Operable · Level A · Introduced in WCAG 2.1
WCAG 2.5.3: Label in Name
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
When a control has a visible text label, its accessible name must contain that text. People using speech input often speak the words they see, so a conflicting hidden name can make the control difficult to target.
A practical example
A button visibly says “Send message” but aria-label changes its name to “Submit inquiry.” Remove the conflicting override or use a name that contains “Send message,” preferably at the beginning.
How to check it
- List controls with visible text or images of text.
- Inspect each computed accessible name rather than only its HTML attributes.
- Check that the visible words are included in the name and try the visible phrase with supported speech input where available.
What can be missed
A more descriptive hidden label can still introduce a mismatch. Check localization and changing button labels because the accessible name may be left behind after the visible wording changes.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.