ARIA · WCAG 2.0 Level A
Required ARIA attributes must be provided
Ensure elements with ARIA roles have all required ARIA attributes.
What it means
The aria-required-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
Add the attributes the role requires, for example aria-checked on role="checkbox". Better: use a native element.
<div role="checkbox" aria-checked="false" tabindex="0">Subscribe</div>
<!-- better -->
<input type="checkbox" id="sub"><label for="sub">Subscribe</label>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-required-attr.
Quick answers
What does the axe rule "aria-required-attr" check?
Ensure elements with ARIA roles have all required ARIA attributes.
How do I fix "Required ARIA attributes must be provided"?
Add the attributes the role requires, for example aria-checked on role="checkbox". Better: use a native element.
Who is affected by aria-required-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.