Names, roles and values · WCAG 2.0 Level A
Input buttons must have discernible text
Ensure input buttons have discernible text.
What it means
The input-button-name rule flags elements that fail this check. It maps to WCAG success criterion 4.1.2.
Who it affects
Screen reader and voice control users, who need every control to announce a name and role.
How to fix it
Make sure every interactive element exposes an accessible name (visible text, aria-label or aria-labelledby) and the correct role.
Check it on your site
Run a free scan. If this rule fails, the results list the affected elements. Deque, which maintains axe-core, also documents this rule in detail: Deque University: input-button-name.
Quick answers
What does the axe rule "input-button-name" check?
Ensure input buttons have discernible text.
How do I fix "Input buttons must have discernible text"?
Make sure every interactive element exposes an accessible name (visible text, aria-label or aria-labelledby) and the correct role.
Who is affected by input-button-name failures?
Screen reader and voice control users, who need every control to announce a name and role.
Automated accessibility scan. Results are informational and may not identify every accessibility issue. This service is not legal advice, a compliance certification, or a substitute for comprehensive manual accessibility testing.