axe DevTools®: Digital accessibility testing tools dev teams love

Automate with the most comprehensive web and mobile accessibility testing tools built for developers–saving you money, time, and effort.

Why use axe DevTools?

Human-centric AI

Computer vision designed by and for people finds more accessibility defects faster than any other tool.

Test web and mobile

Globally-accepted standards validated by 20+ years of accessibility leadership. Get consistent tests across all devices.

Integrate immediately

From the first scan, axe DevTools becomes part of your dev process – with a single call from your build.

Get started with web accessibility testing

Join our growing community of dev team users: 875,000+ extensions installed and 1 Billion+ axe-core downloads. View full feature comparison table.

Browser extension

Easily test web applications right from your browser.

  • Includes: Start testing immediately
  • Includes: Find issues & save time with AI
  • Includes: Export, save, share results

Free 7-day trial.
No credit card required!

Complete HTML toolkit

Integrate directly into your current testing process.

  • Includes: Extended browser extension capabilities
  • Includes: No-code automated testing
  • Includes: Coordinate and scale testing across CI/CD

Get the widest mobile coverage available

Scan for mobile accessibility in minutes. No code access required–test apps built with native Android or iOS, React Native, or other cross-platform technologies. Get started with a free trial of axe DevTools Mobile.

The axe DevTools Mobile dashboard and a mobile phone that says

Testing only specific parts of a page makes auditing design systems 10x easier!

Photo of Anna Cook

Anna Cook Senior Inclusive Designer, Microsoft

There’s instant credibility in having axe DevTools behind us, not just a free tool you can get off the internet.

Photo of Bob Andreasen

Bob Andreasen Executive Director of Software Quality Assurance, Harland Clarke

Zero maintenance test integrations

Just add a few lines to configure and embed accessibility testing directly into your current testing cycle. Run scalable accessibility tests with each automated test. Get started with a free trial of axe Developer Hub.

// pull in @axe-core/watcher module so it gets injected into all our tests

const { cypressConfig } = require('axe-core/watcher')

module.exports = defineConfig(
 cypressConfig({
  axe: {
   apiKey: 'abcdef-1234' ,
  },
 })
);

Block bad code with GitHub actions

There’s no need to update automated accessibility tests every time with axe DevTools. One line of code works across all dev environments, coding languages, CI/CD tools and automated testing networks. Get started with a free trial of axe DevTools Linter.

Find and fix more accessibility bugs

  • The axe DevTools Extension tests from your browser, while you code, and in pull requests (PRs).
  • Our computer vision data pipeline uncovers the most real issues.
  • Intelligent Guided Tests (IGTs) provide expert-level testing with no accessibility expertise required.

Human-centric AI: Learn as you test

Axe DevTools quickly discovers accessibility issues, shows you how to fix them, and measures progress over time.

What you can do with axe DevTools

  • Find 80% or more of your issues with no accessibility expertise needed.

  • Stop issues in custom components before they’re live.

  • Report on accessible code quality in SonarQube / Jenkins.

Who is axe DevTools for?

Web development teams

Understand and pinpoint accessibility issues in the context of a fully rendered page.

Test engineers

Seamlessly run accessibility testing as part of your regular build tests.

Development leaders

Incorporate consistent standards, rules, and testing across the SDLC.

Mobile product owners

Enable proven user initiated or automated mobile testing as a part of the release cycle.

Developers / QA–Get the documentation you need now!

If you’re looking for the facts on our products, look no further. We have all the details about how to use axe DevTools – and more.

Screenshot of the Deque Docs website homepage.

Accessibility solutions for the most popular environments

  • Cypress logo
  • Puppeteer logo
  • Selenium_ logo
  • C Sharp (C#) logo
  • Webdriver logo
  • Android logo
  • RSpec (Ruby) logo
  • Jest logo
  • Nightwatch logo
  • Protractor logo
  • Test Cafe logo

Helpful resources

Blog post

Why you need to monitor and report on accessibility–all the time

Read More

Axe-con dev track

Access dozens of free, recorded educational sessions anytime.

View Now

Webinar

Developers’ Guide to Getting Started with Accessibility Testing.

Watch Now

Blog post

I’ve received the results of my accessibility audit–now what?

Read More

Frequently asked questions

Digital accessibility testing tools help designers, members of dev teams, product owners, and others check web pages, mobile applications, and other digital content against accessibility standards– to learn they are accessible for everyone, including people with disabilities.

No. Automated accessibility testing tools enable testers to reduce the volume of manual tests they have to do without machine assistance. Using Intelligent Guided Tests (IGTs) and other semi-automated tools, testers can focus manual testing efforts on more complex issues that can’t yet be detected automatically.

The goal of accessibility testing for web applications is to make sure that websites deliver highly functional, bug-free, and accessible experiences across browsers and devices–for everyone–including people with disabilities. The goal of testing mobile native apps is to ensure that there are no accessibility issues within the native or hybrid mobile app across a wide range of Android and/or iOS devices, so that the applications are also accessible for everyone who uses them.

No, JAWS, NVDA, and VoiceOver are three very popular screen readers that are used by many people with low or no vision. While automated and semi-automated tests can eliminate a large percentage of issues that may affect screen readers, manual testing with screen readers is sometimes still required to be completely certain that all potential issues have been addressed.

Google Lighthouse has actually run on Deque’s open-source accessibility library, axe-core, since 2017. Deque owns and maintains the axe-core project and also uses it to power axe DevTools. However, Lighthouse does not run the full set of more than 70 tests that axe DevTools does.

Some vendors want you to believe that always flagging “more issues” is better. So much so, that many tools produce inaccurate results – or false positives. This is evident in comparative reviews with accessibility experts who participate in setting the WCAG standards. False positives lead to dev team testing abandonment and wasted time. Further, they undermine the credibility of accessibility team leaders who recommend these tools and practices.