Buttons have no discernible text
Automated check button-name, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Blocker: a task cannot be completed
- Typical effort
- Quick win, under 1 hour
- Category
- Forms and controls
Who this affects
Screen reader users, and voice-control users who must speak a control name to activate it.
Why it matters
An unlabelled button is announced as "button" with no indication of what it does. When this hits a checkout, close or submit control, the user cannot complete the transaction at all — exactly the scenario the EAA targets.
How to fix it
Put text inside the <button>, or add aria-label="Close dialog". For icon buttons, keep a visually-hidden text label so voice control still works.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Forms and controls
- Custom buttons, links or menu items have no accessible name
- Dialogs have no accessible name
- Custom input widgets have no accessible name
- Custom checkboxes, switches or radio buttons have no accessible name
- Form fields use invalid autocomplete values
- Form field has more than one label
- Form buttons have no accessible name
- Image buttons have no text alternative