Custom buttons, links or menu items have no accessible name
Automated check aria-command-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 activate controls by saying their name.
Why it matters
Elements with role="button", role="link" or role="menuitem" but no text are announced as just "button" or "link". The user cannot tell what they do, and voice control cannot reach them.
How to fix it
Put visible text inside the element, or add aria-label or aria-labelledby. Better still, use a native <button> or <a> element.
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
- 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
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name
- Image buttons have no text alternative