ARIA · WCAG 2.0 Level A
ARIA attributes must be used as specified for the element's role
Ensure ARIA attributes are used as described in the specification of the element's role.
What it means
The aria-conditional-attr 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
Use native HTML elements where possible. If you use ARIA, use only valid roles and attributes, with allowed values, on elements that support them.
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-conditional-attr.
Quick answers
What does the axe rule "aria-conditional-attr" check?
Ensure ARIA attributes are used as described in the specification of the element's role.
How do I fix "ARIA attributes must be used as specified for the element's role"?
Use native HTML elements where possible. If you use ARIA, use only valid roles and attributes, with allowed values, on elements that support them.
Who is affected by aria-conditional-attr 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.