Rule
ARIA state the element really has cannot be reached
A state the element has must be exposed through a role that supports it.
- Rule
aria-state-unreachable- WCAG 2.2
- 4.1.2 Name, Role, Value (opens in a new tab) (Level A)
- Severity
- Moderate
What it checks
The rule fails an element that really has a state, shown by a native readonly, required, disabled or checked attribute, when the role it has been given does not support the matching ARIA attribute, such as aria-readonly. Browsers drop an attribute the role does not support, so assistive technology cannot learn the state, though the control behaves that way.
The usual cause is a form field given a role it should not have: a read-only text field with role="region" reaches a screen reader as a landmark, with no sign that it cannot be typed in. Unsupported attributes with no native state behind them are left to allowed ARIA attributes.
Example
Fails
<label for="total">Total to pay</label>
<input id="total" type="text" role="region" readonly aria-readonly="true" value="£1,240">
Passes
<label for="total">Total to pay</label>
<input id="total" type="text" readonly aria-readonly="true" value="£1,240">
The engine is tested against both examples.
How to fix it
Remove the role, so the field keeps its native role and the state with it, or give the element a role that supports the state.
Check your own pages
This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.