- Success Criterion 2.5.3
- Conformance level A
Title Attribute Overriding a Control’s Intended Accessible Name
2.5.3 — Label in Name
Scenario
Setting
A customer-support live-chat widget
What’s wrong
Buttons with visible text plus title overriding computed name to something else in some assistive technology combos.
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 for a title attribute on a control that also has visible text: in some AT combinations title overrides the computed name — verify the announced name still matches what's visible.
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 customer-support live-chat widget, this barrier is gone for voice-control users and screen-reader users who depend on spoken names matching visible text — they can complete the task without hitting this wall.
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