Names, roles and values · WCAG 2.0 Level A
Buttons must have discernible text
Ensure buttons have discernible text.
What it means
The 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
Every button needs a name: visible text, aria-label, or aria-labelledby. Icon buttons are the usual culprit.
<button type="button" aria-label="Close dialog">×</button>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: button-name.
Quick answers
What does the axe rule "button-name" check?
Ensure buttons have discernible text.
How do I fix "Buttons must have discernible text"?
Every button needs a name: visible text, aria-label, or aria-labelledby. Icon buttons are the usual culprit.
Who is affected by 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.