• Success Criterion 4.1.2
  • Conformance level A
  • W3C reference F79

Assistive Technology Never Told Which Element Currently Has Focus

4.1.2 — Name, Role, Value

Scenario

Setting

A music streaming app's playlist screen

What’s wrong

Assistive technology is never told which element currently has focus, or that focus changed — screen readers lose track of the user's position.

Example

Try this on a music streaming app's playlist screen: assistive technology is never told which element currently has focus, or that focus changed — screen readers lose track of the user's position.

Why it matters

Screen-reader and voice-control users who can operate only what the accessibility tree exposes. The practical effect on a music streaming app's playlist screen: they can't complete the task without extra help.

How to test

Tab to a control and check DevTools' Accessibility panel: if the focused/unfocused state isn't exposed or announced, it fails.

How to fix

Use focusable native elements (or manage tabindex (keyboard-focus setting) + ARIA) so focus position and changes are exposed to assistive technology.

Outcome

That one change on a music streaming app's playlist screen 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

Related scenarios