- Success Criterion 4.1.2
- Conformance level A
State Attribute Present on an Element That Never Actually Changes
4.1.2 — Name, Role, Value
Scenario
Setting
A real-estate marketplace's listing page
What’s wrong
State attributes on elements that never change state (aria-expanded (the open/closed state in code) on a plain link) announcing false expandability.
Example
On a real-estate marketplace's listing page: state attributes on elements that never change state (aria-expanded (the open/closed state in code) on a plain link) announcing false expandability.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a real-estate marketplace's listing page, that means they have to work around the barrier just to continue.
How to test
Inspect a control's aria state attributes: if a state attribute exists on an element that has no actual state to report (e.g., aria-expanded on a plain link), it fails.
How to fix
Remove state attributes from elements that have no state to report.
Outcome
With the fix in place on a real-estate marketplace's listing page, 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