- Success Criterion 4.1.2
- Conformance level A
Complex Widget Relying on a Title Attribute for Its Name
4.1.2 — Name, Role, Value
Scenario
Setting
A streaming music app's search results
What’s wrong
title-only names on complex widgets where assistive technology support gaps make the name unavailable in practice (risk-level failure logged against name robustness).
Example
A streaming music app's search results is a good example: title-only names on complex widgets where assistive technology support gaps make the name unavailable in practice (risk-level failure logged against name robustness).
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. The practical effect on a streaming music app's search results: they can't complete the task without extra help.
How to test
Inspect a complex widget's name source in DevTools: if it relies only on a title attribute (with known inconsistent AT support), verify the name is still reliably available — if not, it fails.
How to fix
Provide the name via aria-label/labelledby rather than title alone.
Outcome
That one change on a streaming music app's search results means they move past the barrier without workarounds.
Who is affected
Screen-reader and voice-control users who can operate only what the accessibility tree exposes.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Custom Dropdown or Slider With No Accessibility API Support
- Content Changes That Never Update Their Accessible Name
- Scripted Link or Button With No Real Role or Keyboard Support
- Clickable Div Turned Into a Control but Given No ARIA Role
- Form Field With No Programmatic Label at All
- Assistive Technology Never Told Which Element Currently Has Focus