- Success Criterion 4.1.2
- Conformance level A
Control Announcing a State That Contradicts Its Real Behavior
4.1.2 — Name, Role, Value
Scenario
Setting
A coworking-space booking app
What’s wrong
A control announces a false state that contradicts its actual behavior. 'read-only' on an interactive combobox, 'collapsed' while visibly expanded, 'disabled' while fully active, so assistive technology users skip or mistrust working controls.
Example
Picture a coworking-space booking app: a control announces a false state that contradicts its actual behavior. 'read-only' on an interactive combobox, 'collapsed' while visibly expanded, 'disabled' while fully active, so assistive technology users skip or mistrust working controls.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. Here, on a coworking-space booking app, the result is they hit a dead end with no way forward.
How to test
Compare the control's announced state to its actual behavior with a screen reader: 'read-only' announced on a working combobox, or 'collapsed' while visibly expanded, is a false state and fails.
How to fix
Correct the state wiring so announced state always matches actual behavior (interactive ≠ read-only, expanded ≠ collapsed).
Outcome
After the fix, the same visitor to a coworking-space booking app 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)
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