- Success Criterion 4.1.2
- Conformance level A
Combobox Missing the ARIA Wiring for Its Open and Active State
4.1.2 — Name, Role, Value
Scenario
Setting
A podcast app's episode list
What’s wrong
Comboboxes missing aria-expanded (the open/closed state in code)/aria-activedescendant (code tracking the highlighted option) wiring so value/state never reported.
Example
During an audit of a podcast app's episode list: comboboxes missing aria-expanded (the open/closed state in code)/aria-activedescendant (code tracking the highlighted option) wiring so value/state never reported.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a podcast app's episode list, that means they have to work around the barrier just to continue.
How to test
Operate a combobox and inspect DevTools: check for aria-expanded, aria-controls, and aria-activedescendant updating as you navigate — missing wiring fails.
How to fix
Wire the combobox pattern fully: aria-expanded (the open/closed state in code), aria-controls, and aria-activedescendant (code tracking the highlighted option)/selection state.
Outcome
With the fix in place on a podcast app's episode list, they get the same outcome as everyone else.
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