Success Criterion 4.1.2
Conformance level A
W3C reference F15

Custom Dropdown or Slider With No Accessibility API Support

4.1.2 — Name, Role, Value

Scenario

Setting

A food delivery app's restaurant menu

What’s wrong

A custom-built control (dropdown, slider, dialog) doesn't tell assistive technology what it is or what state it's in, because it skips the standard accessibility hooks.

Example

Picture a food delivery app's restaurant menu: a custom-built control (dropdown, slider, dialog) doesn't tell assistive technology what it is or what state it's in, because it skips the standard accessibility hooks.

Why it matters

Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a food delivery app's restaurant menu, this barrier means they hit a dead end with no way forward.

How to test

Inspect the custom control in DevTools' Accessibility panel: if it doesn't expose a name, role, or state through the accessibility API, it fails.

How to fix

Build the control on native elements or full ARIA (role + name + state) wired to the accessibility API.

Outcome

Corrected, a food delivery app's restaurant menu now lets a visitor complete the task without extra help.

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)