- Success Criterion 4.1.2
- Conformance level A
ARIA Role Assigned That Doesn’t Match the Control’s Behavior
4.1.2 — Name, Role, Value
Scenario
Setting
A budget airline's flight search results
What’s wrong
Wrong roles: role="button" on real links changing announced behavior falsely — role="menu" on ordinary nav breaking arrow-key expectations.
Example
On a budget airline's flight search results: wrong roles: role="button" on real links changing announced behavior falsely — role="menu" on ordinary nav breaking arrow-key expectations.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a budget airline's flight search results specifically, they have to work around the barrier just to continue.
How to test
Inspect the assigned ARIA role against the control's actual behavior: a role that doesn't match what the control does (e.g., role="menu" on plain navigation) fails.
How to fix
Use the role that matches actual behavior — link stays link, button stays button — drop role='menu' from plain navigation.
Outcome
Fixed, a visitor to a budget airline's flight search results can 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)
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