How to fix “Required ARIA attributes must be provided”
By Justin Zagar · Updated
An element has an ARIA role but is missing an attribute that role needs, such as a slider with no aria-valuenow. Add the missing attribute and keep it up to date, or use the native HTML element instead.
- axe rule
aria-required-attr- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Lighthouse
- Google Lighthouse and PageSpeed Insights report it as “[role]s do not have all required [aria-*] attributes”
What it means
Some ARIA roles promise a screen reader certain facts. A slider promises a current value. A checkbox promises checked or not. Deque explains that when the required attribute is missing, the widget's state never reaches screen reader users.
It usually comes from a custom widget in a theme or plugin: a price range slider, a custom dropdown, an accordion.
Who it affects
People who use a screen reader.
How to find it
- Run the free checker. It names the role and the attribute that's missing.
How to fix it
- Prefer the native element. input type="range" is already a slider, input type="checkbox" is already a checkbox, and both report their state on their own.
- If you keep the custom widget, add the required attribute and update it with script whenever the value changes.
- If the widget comes from a plugin, report it to the plugin's maker and check for an update first.
A custom slider
<div role="slider" tabindex="0"></div><div role="slider" tabindex="0" aria-label="Maximum price"
aria-valuemin="0" aria-valuemax="500" aria-valuenow="250"></div>Simpler still: <input type="range" min="0" max="500" value="250"> with a label.
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
- ARIA attributes must conform to valid values
ARIA attributes with bad values
- Elements must only use permitted ARIA attributes
ARIA attributes where they aren't allowed
- <ul> and <ol> must only directly contain <li>, <script> or <template> elements
Broken list markup
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.