- Success Criterion 2.5.3
- Conformance level A
Accessible Name Missing the Units Shown in the Visible Label
2.5.3 — Label in Name
Scenario
Setting
A webinar platform's registration form
What’s wrong
Placeholder or trailing units visible ("Amount (USD)") while accessible name is "input".
Example
<button aria-label="Find">Search</button> Why it matters
Voice-control users and screen-reader users who depend on spoken names matching visible text.
How to test
Read the visible label including any trailing unit or descriptor (e.g., 'Amount (USD)'): check whether the accessible name includes it too, or is just 'input'.
How to fix
The accessible name must contain the exact visible label text.
<button aria-label="Search">Search</button>The accessible name must contain the visible label text so voice-control users can activate it by what they see.
Outcome
On a webinar platform's registration form, this barrier is gone for voice-control users and screen-reader users who depend on spoken names matching visible text — they reach the same outcome without extra effort.
Who is affected
Voice-control users and screen-reader users who depend on spoken names matching visible text.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Accessible Name That Doesn’t Match the Control’s Visible Label
- Visible Label Text With No Accessible Name Behind It
- ARIA Label Naming a Completely Different Action Than Shown
- Accessible Name Built From an Icon Instead of Visible Text
- Translated ARIA Label That Doesn’t Match the Visible Language
- Visible Label Text Reordered or Broken Apart in the Name