How to fix “ARIA attributes must conform to valid values”
By Justin Zagar · Updated
An ARIA attribute has a value it can't take, such as aria-expanded="yes" instead of "true", or an aria-labelledby that points to an id that isn't on the page. Use an allowed value, and make sure every id it points to exists.
- axe rule
aria-valid-attr-value- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Lighthouse
- Google Lighthouse and PageSpeed Insights report it as “[aria-*] attributes do not have valid values”
What it means
Many ARIA attributes accept only certain values. Deque notes the values must be spelled correctly and make sense for the attribute, or the information doesn't reach assistive technology.
Common causes: true and false written as yes and no, a typo in a role or value, and aria-controls, aria-describedby or aria-labelledby pointing to an id that was renamed or removed.
Who it affects
People who use a screen reader.
How to find it
- Run the free checker. It shows the attribute and its value.
- For id references, search the page source for the id it names. If it's not there, that's the problem.
How to fix it
- Use the allowed value. For true or false attributes, write exactly true or false.
- Fix the id reference, or remove the attribute if the thing it pointed at is gone.
- If script sets the value, fix the script, since the page may start valid and break after a click.
A menu toggle
<button aria-expanded="yes" aria-controls="main-nav">Menu</button>
<nav id="primary-nav">...</nav><button aria-expanded="false" aria-controls="primary-nav">Menu</button>
<nav id="primary-nav">...</nav>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.
Related fixes
- Required ARIA attributes must be provided
ARIA roles missing required attributes
- Elements must only use permitted ARIA attributes
ARIA attributes where they aren't allowed
- ARIA hidden element must not be focusable or contain focusable elements
Hidden content you can still tab to
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.