ARIA roles are missing their required attributes
Automated check aria-required-attr, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Serious: completable, but painful
- Typical effort
- Moderate, 1 to 4 hours
- Category
- Code quality
Who this affects
Screen reader users encountering custom widgets.
Why it matters
A role such as checkbox or slider without its required state attributes is announced with no value, so the user cannot tell what is selected.
How to fix it
Supply the required attributes for the role (for example aria-checked on role="checkbox"), and keep them updated in JavaScript as state changes.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Code quality
- ARIA attributes used on the wrong elements
- ARIA roles that do not suit the element
- Braille-only ARIA attributes have no spoken equivalent
- ARIA attributes used in ways the role does not allow
- Deprecated ARIA roles are used
- The page body is hidden from assistive technology
- ARIA labels placed on elements that cannot carry them
- Menus, lists or tabs are missing their required child elements