What this criterion requires
For controls with visible text labels, the accessible name must contain that visible text - ideally starting with it.
Who it helps
Speech-input users, who say the label they see ("click Send"); if the accessible name differs, the command fails.
Example: fails vs passes
<button aria-label="Submit form">Send</button><button>Send</button> <!-- or aria-label="Send message", starting with the visible text -->Voice control users say what they see. If the accessible name lacks "Send", the command "click Send" fails.
How to meet and fix it
- Keep aria-label in sync with the visible text, or better, do not override it at all
Common failures auditors find
- Visible "Send" with aria-label="Submit form" - voice control cannot find "Send"
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
Sources
- W3C, Understanding 2.5.3: Label in Name - w3.org/WAI
- W3C, How to Meet 2.5.3 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 2.5.3?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.