How to fix “Elements must only use permitted ARIA attributes”
By Justin Zagar · Updated
An element uses an ARIA attribute its role doesn't allow, most often an aria-label on a plain div or span. Use a real button or link for anything people click, and put the label there.
- axe rule
aria-prohibited-attr- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Lighthouse
- Google Lighthouse and PageSpeed Insights report it as “Elements use prohibited ARIA attributes”
What it means
The WAI-ARIA 1.2 spec lists roles that can't be given a name, including generic (what a plain div or span is), paragraph, strong and presentation. An aria-label on one of them is ignored or read inconsistently, so the information is lost.
This usually means something clickable was built from a div. That's a bigger problem than the label, because a div also can't be reached or pressed with a keyboard unless extra code is added.
ARIA is common and often misused. The WebAIM Million found ARIA on 82.7% of home pages in 2026, and those pages averaged 59.1 errors against 42 on pages without it. W3C's own advice is that no ARIA is better than bad ARIA.
Who it affects
People who use a screen reader, and keyboard users when the element is meant to be clicked.
How to find it
- Run the free checker. It lists the element and the attribute, often a div with an aria-label.
How to fix it
- If people click it, make it a button (or a link if it goes to another page) and keep the aria-label there, or better, put visible text in it.
- If it's just text, remove the aria-label. The text speaks for itself.
A chat launcher built from a div
<div class="chat-launcher" aria-label="Open chat">
<i class="icon-chat"></i>
</div><button type="button" class="chat-launcher" aria-label="Open chat">
<i class="icon-chat" aria-hidden="true"></i>
</button>From a real fix
On the law firm site I fixed, a chat launcher on every page was a div with an aria-label. Making it a real button fixed this rule and gave it the keyboard behavior a button gets for free.
What a scanner can and can’t tell you
Fixing this clears one automated check. It doesn’t mean the page is accessible, and it doesn’t settle any legal question. Automated tests catch only part of the problems. W3C puts it plainly: evaluation tools “can not determine accessibility, they can only assist in doing so.” The rest takes a person working through the site with a keyboard and a screen reader.
Source: W3C WAI, Selecting Web Accessibility Evaluation Tools. Not legal advice.
Sources
All checked November 8, 2026. The rule wording is axe-core 4.14.0’s own.
- W3C: Understanding Success Criterion 4.1.2 Name, Role, Value
- W3C: WAI-ARIA 1.2
- W3C ARIA Authoring Practices: Read Me First (No ARIA is better than bad ARIA)
- WebAIM: The WebAIM Million, 2026 report
- Deque University: axe rule aria-prohibited-attr (axe-core 4.14)
- Google Lighthouse source: the aria-prohibited-attr audit
Related fixes
- Required ARIA attributes must be provided
ARIA roles missing required attributes
- ARIA attributes must conform to valid values
ARIA attributes with bad values
- Buttons must have discernible text
Buttons with no text
Check a page for free
Scan any page of your site against WCAG 2.1 AA in about 30 seconds. You get the problems automated testing finds, in plain words, with a link to a fix guide for the common ones.
Rather have someone fix it for you? Tell me about your site.