ARIA labels placed on elements that cannot carry them
Automated check aria-prohibited-attr, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Serious: completable, but painful
- Typical effort
- Quick win, under 1 hour
- Category
- Code quality
Who this affects
Screen reader users.
Why it matters
An aria-label on a plain <div> or <span> is ignored by most screen readers, so the information it was meant to convey never arrives.
How to fix it
Move the label onto an interactive element or one with a suitable role, or make the text visible instead.
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 roles are missing their required attributes
- Menus, lists or tabs are missing their required child elements