Axe rule guides
aria-required-attrcritical

Fix aria-required-attr axe errors

An ARIA role is missing attributes required for that role, so the component may be exposed incorrectly.

Affected users

Screen reader users and users of assistive technology that depends on role metadata.

WCAG mapping

4.1.2 Name, Role, Value (A)

Detection

wcagc checks ARIA role requirements through axe-core and reports missing required attributes.

Failing markup

<div role="slider" aria-label="Volume"></div>

Fixed code

<div role="slider" aria-label="Volume" aria-valuemin="0" aria-valuemax="100" aria-valuenow="50"></div>

Sources and standards

FAQ

Should I add ARIA to every custom component?

No. Prefer native HTML controls first. Use ARIA only when native elements cannot express the needed widget.

Why can one missing ARIA attribute be critical?

Without required state or value attributes, assistive technology may expose the component with the wrong behavior.

Scan the rest of the page

One rule rarely travels alone

Run a page through wcagc to find this rule, related WCAG issues, affected selectors, and manual checks that automation cannot judge.

Scan a page