- Success Criterion 4.1.2
- Conformance level A
Accessible Name Computed as Meaningless Icon or Code Text
4.1.2 — Name, Role, Value
Scenario
Setting
A telehealth app's video-visit waiting room
What’s wrong
Names computed as junk: icon ligature text (". "), SVG path noise, or "button button".
Example
A tester reviewing a telehealth app's video-visit waiting room finds this: names computed as junk: icon ligature text (". "), SVG path noise, or "button button".
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. The practical effect on a telehealth app's video-visit waiting room: they can't complete the task without extra help.
How to test
Check the computed accessible name in DevTools: if it's junk (icon-font ligature characters, raw SVG path text, or duplicated words like 'button button'), it fails.
How to fix
Give the control a clean accessible name — hide icon-font characters and avoid duplicated words.
Outcome
That one change on a telehealth app's video-visit waiting room 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