What WCAG 2.5.3 Requires
When a control has a visible text label, its accessible name (what a screen reader announces) must contain that visible text, so voice control users referring to the visible label can activate it.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Compare the visible label on a button or link to its accessible name (from the browser's accessibility inspector); the visible words should be part of the accessible name.
Common Failures
- A button visibly reads "Submit" but has aria-label="Send form now" with no matching text, so voice control commands using the visible word fail.
Related Criteria in Input Modalities
WCAG 2.5.3 Questions
What does WCAG 2.5.3 require?
When a control has a visible text label, its accessible name (what a screen reader announces) must contain that visible text, so voice control users referring to the visible label can activate it.
Can AccessBell test WCAG 2.5.3 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 2.5.3?
Level A, added in WCAG 2.1.
Sources
- W3C: Understanding 2.5.3 Label in Name (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.