axe Dev Tools
Browser extension to find accessibility issues in web apps.
Open the official app on www.deque.com
This tool is hosted by its maintainers. Click below to open www.deque.com in a new tab — it's their official demo.
Browse developer tools →What's next with axe Dev Tools?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is axe Dev Tools?
Axe DevTools is an open-source accessibility testing tool designed to automate compliance checks for web and mobile applications. It leverages AI and automation to identify barriers that prevent users with disabilities from accessing digital content, aligning with standards like WCAG 2.1. Developers, QA teams, and accessibility specialists use it to integrate accessibility testing into their workflows, reducing manual efforts and ensuring early detection of issues. The tool addresses the challenge of maintaining accessibility in rapidly evolving codebases by providing scalable, reliable results with minimal false positives. Its integration into IDEs, browsers, and CI/CD pipelines enables continuous testing, making it a critical tool for organizations aiming to meet accessibility regulations and improve user inclusivity.
How it works
Axe DevTools is a digital accessibility testing solution that automates the identification of barriers in web and mobile applications. It was developed by Deque, a leader in accessibility tools, and is built on the widely used axe-core library, which has been downloaded over 4 billion times. The tool's primary purpose is to streamline accessibility testing by integrating AI-driven checks into development workflows. It helps developers and QA teams catch issues early, ensuring compliance with standards like WCAG 2.1 and reducing the risk of legal or usability problems. Axe DevTools supports automated testing for both web and mobile platforms. For web, it integrates with IDEs, browsers, and CI/CD pipelines, enabling real-time checks during development. For mobile, it allows testing without source code access via automated UI tests and React Native linting. The tool also includes AI-powered deduplication to prioritize critical issues.
How to use it
- 1Install the axe DevTools extension for browsers or integrate it into your IDE via plugins. 2. Configure CI/CD pipelines to run automated tests using the axe CLI. 3. Execute tests on web applications during development or mobile apps via UI automation. 4. Review results in the integrated interface, prioritizing issues flagged by AI-driven analysis. Practical tips include using the axe CLI for batch testing, leveraging the React Native linter for mobile code, and combining tests with manual audits for comprehensive coverage.
What it can do
- accessibility scanner
Use cases
Assumptions and limitations
Assumptions
- source: https://www.deque.com/axe/devtools/
- license: MPL-2.0 — free to use
- privacy: Opens an external demo
Limitations
- Mobile testing requires access to UI elements, which may not be available in all environments
- AI-driven deduplication may occasionally miss nuanced issues requiring manual review
- Setup complexity may challenge teams unfamiliar with CI/CD integration
- Limited native support for non-React Native mobile frameworks
- Real-time feedback during development is constrained by test execution overhead
Understanding the result
Browser extension to find accessibility issues in web apps.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MPL-2.0).
- Built with
- (https://www.deque.com/axe/devtools/)
- License
- MPL-2.0
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with https://www.deque.com/axe/devtools/. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MPL-2.0
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- MPL-2.0 License
Upstream project
Frequently asked
What is axe DevTools and how does it differ from manual accessibility testing?
Axe DevTools automates accessibility testing using AI and predefined rules, drastically reducing the time and effort required compared to manual checks. While manual testing identifies issues through human observation, axe DevTools scales testing across codebases, catches issues early in development, and prioritizes critical problems with AI-driven deduplication. It also integrates with CI/CD pipelines, ensuring compliance is maintained throughout the development lifecycle.
How does axe DevTools handle mobile testing without source code access?
For mobile testing, axe DevTools uses automated UI tests to interact with apps as a user would, simulating gestures and navigation to identify accessibility barriers. This approach allows testing of apps without requiring source code, though it relies on the app’s UI elements being accessible via standard automation frameworks. React Native projects benefit from built-in linting rules that analyze code for accessibility issues during development.
How do I run axe DevTools in a CI/CD pipeline?
To integrate axe DevTools into a CI/CD pipeline, install the axe CLI tool and configure it to run tests on your codebase. For web projects, use the axe CLI with command-line parameters to scan HTML/CSS/JS files. For mobile, use the axe DevTools mobile plugin with automated test scripts. Results are outputted in JSON or HTML format, which can be parsed by your pipeline to trigger alerts or fix blockers.
How does axe DevTools compare to alternatives like Lighthouse or IBM Accessibility Checker?
Axe DevTools focuses on automated, AI-driven testing with a strong emphasis on zero false positives and integration into development workflows. Lighthouse, part of Chrome DevTools, provides a broader set of performance and accessibility checks but lacks the same level of AI optimization. IBM Accessibility Checker offers detailed reports but is less integrated with CI/CD pipelines. Axe DevTools excels in scalability and real-time feedback for developers, while alternatives may offer more general-purpose testing capabilities.
What should I do if axe DevTools reports a false positive?
If a false positive occurs, first verify the issue by manually testing the element in a browser. Use the axe DevTools debug mode to inspect the element’s attributes and context. If the rule is overly strict, consider customizing the test rules or excluding specific elements. For persistent issues, report them to the axe DevTools community or Deque support to refine the tool’s AI models.