- 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
<label for="fee">Registration Fee (USD)</label>
<input id="fee" aria-label="Registration Fee"> Why it matters
A voice-control user reading 'Registration Fee (USD)' on screen says exactly that, but the shorter stored name doesn't contain it.
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
Drop the redundant aria-label and let the visible label, units included, become the accessible name.
<label for="fee">Registration Fee (USD)</label>
<input id="fee"> Outcome
A registrant reads the field's full visible label aloud and lands in the fee input on the first try.
Who is affected
Voice-control users filling out the fee field, and screen reader users who lose the currency context entirely.
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