Error: No matching rule for
axe/html/3.5/assets
List of Axe HTML 3.5 rules
Start building more accessible experiences
Axe DevTools Pro helps dev teams find and fix up to 80% of accessibility issues while coding. No experience required. Get started with your free trial today.
These are automated accessibility checks. Manual checks are also required. Learn how through our accessibility curriculum.
See the list of axe html versions
- <audio> elements must have a captions <track>
- accesskey attribute value must be unique
- Active <area> elements must have alternate text
- ARIA attributes must conform to valid names
- ARIA attributes must conform to valid values
- ARIA button, link, and menuitem must have an accessible name
- ARIA dialog and alertdialog must have an accessible name
- ARIA input fields must have an accessible name
- ARIA meter must have an accessible name
- ARIA progressbar must have an accessible name
- ARIA role must be appropriate for the element
- ARIA roles used must conform to valid values
- ARIA toggle fields have an accessible name
- ARIA tooltip must have an accessible name
- ARIA treeitem must have an accessible name
- aria-hidden elements do not contain focusable elements
- aria-hidden="true" must not be present on the document <body>
- Autocomplete attribute must be used correctly
- Certain ARIA roles must be contained by particular parent elements
- Certain ARIA roles must contain particular children
- Elements must only use allowed ARIA attributes
- Ensures role="text" is used on elements with no focusable descendants
- Required ARIA attributes must be provided
- Unsupported DPUB ARIA roles should be used on elements with implicit fallback roles
- Use aria-roledescription on elements with a semantic role
Axe browser extensions
The axe features are integrated into the developer tools.
Contribute to axe on
- You can find the axe-core source code on GitHub.
- See also the axe-core changelog on GitHub.
Deque's Enterprise Suite of Accessibility Tools
- axe DevTools: Empower development teams to find, prevent, and fix accessibility issues while they code.
- axe Auditor: Bring efficient, full-coverage auditing capabilities to your testing teams with this step-by-step manual accessibility testing tool.
- axe Monitor: Dynamically scan, monitor and report on the accessibility status of your site across business and development teams.