Success Criterion 4.1.2
Conformance level A
W3C reference F111

Control With an On-Screen Label but No Accessible Name

4.1.2 — Name, Role, Value

Scenario

Setting

A food-delivery app's order-tracking screen

What’s wrong

A control shows label text on screen but has no accessible name at all — screen readers announce nothing useful and voice control can't target it.

Example

On a food-delivery app's order-tracking screen, a visitor hits this wall: a control shows label text on screen but has no accessible name at all — screen readers announce nothing useful and voice control can't target it.

Why it matters

Screen-reader and voice-control users who can operate only what the accessibility tree exposes. Here, on a food-delivery app's order-tracking screen, the result is they hit a dead end with no way forward.

How to test

Compare visible label text to the computed accessible name in DevTools: if the control shows text but has no accessible name at all, it fails.

How to fix

Give the control an accessible name that includes its visible label text.

Outcome

After the fix, the same visitor to a food-delivery app's order-tracking screen can now 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)
Technique Related technique (opens in a new tab)