ARIA · WCAG 2.0 Level A
ARIA attributes must conform to valid values
Ensure all ARIA attributes have valid values.
What it means
The aria-valid-attr-value rule flags elements that fail this check. It maps to WCAG success criterion 4.1.2.
Who it affects
Screen reader and voice control users, who depend on ARIA roles and attributes being valid.
How to fix it
Correct ARIA attribute values: IDs referenced by aria-labelledby or aria-controls must exist, and tokens must be allowed values.
<button aria-expanded="false" aria-controls="menu">Menu</button>
<ul id="menu" hidden>…</ul>Check it on your site
Run a free scan. If this rule fails, the results list the affected elements. Deque, which maintains axe-core, also documents this rule in detail: Deque University: aria-valid-attr-value.
Quick answers
What does the axe rule "aria-valid-attr-value" check?
Ensure all ARIA attributes have valid values.
How do I fix "ARIA attributes must conform to valid values"?
Correct ARIA attribute values: IDs referenced by aria-labelledby or aria-controls must exist, and tokens must be allowed values.
Who is affected by aria-valid-attr-value failures?
Screen reader and voice control users, who depend on ARIA roles and attributes being valid.
Automated accessibility scan. Results are informational and may not identify every accessibility issue. This service is not legal advice, a compliance certification, or a substitute for comprehensive manual accessibility testing.