ARIA attributes used on the wrong elements
Automated check aria-allowed-attr, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Moderate: a degraded experience
- Typical effort
- Moderate, 1 to 4 hours
- Category
- Code quality
Who this affects
Screen reader users.
Why it matters
Invalid combinations are ignored or misreported, so the accessibility information you intended to provide never arrives.
How to fix it
Only use ARIA attributes permitted for the element role. Remember the first rule of ARIA: prefer native HTML elements over ARIA wherever possible.
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 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
- ARIA roles are missing their required attributes
- Menus, lists or tabs are missing their required child elements