- Success Criterion 2.5.3
- Conformance level A
Translated ARIA Label That Doesn’t Match the Visible Language
2.5.3 — Label in Name
Scenario
Setting
An online clothing store's product listing page
What’s wrong
Translated/localized aria-label while visible label is another language.
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
Check the aria-label's language against the visible label's language: a translated aria-label on an untranslated visible label (or vice versa) fails.
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 an online clothing store's product listing page, this barrier is gone for voice-control users and screen-reader users who depend on spoken names matching visible text — they get the same result as anyone else here.
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
- Visible Label Text Reordered or Broken Apart in the Name
- ARIA Reference Pointing to the Wrong Element for a Name