Visible button text differs from its accessible name
Automated check label-content-name-mismatch, run with axe-core
- WCAG
- 2.5.3 Label in Name (Level A)
- Severity
- Serious: completable, but painful
- Typical effort
- Quick win, under 1 hour
- Category
- Forms and controls
Who this affects
Voice-control users, who activate a control by saying the text they see.
Why it matters
If a button shows "Buy now" but its aria-label says "Add product to basket", saying "click Buy now" does nothing.
How to fix it
Make the accessible name start with, or at least contain, the visible text, or remove the aria-label so the visible text is used.
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
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name