21 Best Accessibility Testing Tools in 2026

What Are the 21 Best Accessibility Testing Tools?

The best accessibility testing tools are TestMu AI, axe DevTools, WAVE, Accessibility Insights, Pa11y, Lighthouse, and screen readers such as NVDA, JAWS, and VoiceOver. They scan web pages and mobile apps for WCAG, ADA, and Section 508 violations.

How these tools were chosen and ordered - Each tool was checked against six criteria:

• Standards coverage - Which WCAG version it tests, and whether it also maps to Section 508 or EN 301 549.
• Automated or manual - Whether it scans for rule violations, supports human assistive-technology testing, or both.
• Where it runs - Browser extension, desktop app, command line, CI pipeline, or cloud platform.
• Platform coverage - Web only, or native Android and iOS apps as well.
• Reporting - Whether each issue carries a WCAG reference, severity, element location, and fix guidance.
• Cost and licensing - Free, open source, or commercial.

TestMu AI is our own product and is listed first because it covers the most of these criteria in one place. The rest of the list is grouped by tool type, from browser extensions and command-line scanners to screen readers and enterprise platforms, and the order within it is not a quality ranking. TestMu AI also has limits: it needs an account, so for a quick check of a single page a free extension such as WAVE or axe DevTools gets you an answer faster.

The table below compares 12 widely used tools by type, best use case, standards coverage, and pricing model. Detailed entries for all 21 follow.

1. TestMu AI

TestMu AI's accessibility testing tool provides a wide range of browsers, real devices, and operating systems. It is powered by the axe-core rules engine and covers 39 WCAG-aligned automated checkpoints on web, plus 15 rules on iOS and 18 on Android, validating WCAG 2.0, 2.1, and 2.2 (Levels A, AA, and AAA), ADA, Section 508, AODA, and the European Accessibility Act from one workspace.

It spans six testing surfaces: browser DevTools scanning, framework-driven CI/CD automation, scheduled recurring monitoring, manual real-device mobile testing, Appium-based native app automation, and KaneAI no-code mobile authoring. Every violation carries a WCAG reference, severity, element location, and specific fix guidance.

Features:

• Accessibility DevTools - Chrome extension with axe-core powered full-page, partial-page, workflow, and keyboard scans, and element-level issue reporting.
• Accessibility Automation - Adds accessibility checks to CI/CD pipelines using Selenium, Playwright, and Cypress.
• Accessibility Test Scheduling - Recurring or one-time scans via sitemap, CSV, or crawler discovery to maintain ongoing compliance.
• App Scanner and Appium automation - Scans native Android and iOS apps screen by screen on real devices, or adds accessibility scans to existing Appium suites.
• Screen readers - Manual testing with NVDA, JAWS, VoiceOver, and TalkBack for the checks automation cannot cover.
• Accessibility MCP Server - Exposes accessibility analysis inside AI coding tools, so you can request a report or scan a local build in natural language.

In pipelines, the scans run from GitHub Actions, GitLab CI, Jenkins, or Azure DevOps with the same test command you use locally, and violations can be sent to Jira or GitHub so fixes are tracked where the team already works. The accessibility testing dashboard collects every scan in one view, and hiding and restoring issues lets you park a confirmed false positive without deleting it.

To start with manual accessibility testing, see the Accessibility DevTools documentation. For automated testing, refer to the Accessibility Automation documentation.

Why Choose TestMu AI Over Other Tools?

Most entries in this list cover one surface: an extension, a scanner, or a screen reader. TestMu AI covers six, so the DevTools scan, the CI/CD check, the scheduled crawl, the native Android and iOS app scan and the manual screen reader pass report into one history rather than four disconnected ones. That matters most for the checks automation cannot make, because the manual evidence sits against the same pages as the automated results.

2. WAVE (Web Accessibility Evaluation Tool)

WAVE is WebAIM's accessibility evaluator. Its browser extension marks errors, alerts, and structural elements directly on the rendered page, which makes it the quickest way to see where a violation sits rather than reading a list of selectors. The WAVE accessibility tool guide walks through a full report.

Key facts:

• Runs on - Extensions for Chrome, Firefox, and Edge. WebAIM states that the extension runs entirely in the browser and sends no page data to the WAVE server, so it works on intranet and logged-in pages.
• Beyond the extension - WebAIM also offers a subscription API and a stand-alone testing engine for checking pages at scale, plus the AIM report.
• Stands out for - In-page visual overlays: icons sit next to the element that fails, so non-developers can review results without DevTools.

3. Accessibility Insights (by Microsoft)

Accessibility Insights is Microsoft's open-source accessibility tool family, available as a browser extension for Chrome and Edge and as a desktop tool for Windows applications. It pairs a fast automated pass with a guided manual assessment.

Key facts:

• FastPass - Microsoft describes it as catching the most common accessibility issues in under 5 minutes, combining automated checks with a visual tab-stops test.
• Assessment - A guided, step-by-step manual review that the project positions for WCAG 2.1 AA coverage, with instructions for each check.
• License - Open source on GitHub, free to use.

4. Axe DevTools (Deque Systems)

Axe DevTools is Deque's browser extension built on the open-source axe-core engine. It runs the same rules developers can later automate in CI, so findings from a manual check and a pipeline run line up.

Key facts:

• Intelligent Guided Tests - Deque describes its IGTs as AI-driven guided tests inside the extension that find more issues than automation alone.
• False positives - Deque states a commitment to zero false positives, so reported issues are meant to be acted on, not triaged.
• Free and paid tiers - A free extension plus paid tiers that add guided tests, a linter for static code, and CI/CD integrations for Cypress, Selenium, and Jest.

5. Lighthouse

Lighthouse is Google's open-source auditing tool, built into Chrome DevTools and also available as a command-line tool, a Node module, and through PageSpeed Insights. Its accessibility category runs axe-core rules, and the Lighthouse accessibility scoring documentation explains that the score is a weighted average of audits that each pass or fail, weighted by axe user-impact ratings.

Key facts:

• Built-in DevTools Audit - Runs from the Lighthouse panel in Chrome DevTools with nothing extra to install.
• Pass-or-Fail Audits - A page gets no partial credit on an audit, so one unlabeled button fails that audit outright.
• axe-core Rules - Uses the same rules engine as axe DevTools, so findings line up with axe-based checks in CI.
• Command Line and Node Module - Scriptable runs for pipelines, with Lighthouse CI adding pull-request checks on top.
• Manual Checks Listed Separately - Items that need a human to verify are listed but do not count toward the score.

6. Pa11y

Pa11y is an open-source command-line tool and Node.js library that loads pages in a headless browser and reports accessibility issues. It suits scripted audits and regression checks, and Pa11y CI wraps it for pipelines.

Key facts:

• Engines - Per the Pa11y README, HTML_CodeSniffer is the default runner and axe is also supported; both can run in one pass.
• Actions before testing - Scripted actions such as clicking an element, setting a field, or waiting for a selector let it test states that only exist after interaction.
• License and runtime - LGPL-3.0; runs on Node.js and drives Chromium through Puppeteer, with cli, csv, json, html, and tsv reporters.

7. AChecker (Accessibility Checker)

AChecker is a long-running free web accessibility checker that tests a page against a selected guideline. The original achecker.ca site no longer hosts it; per a 2021 notice on the W3C evaluation-tools list, its maintainers moved it, and it is now offered as AChecker Legacy on ACHECKS (achecks.org), run by Cantan Group.

Key facts:

• Guidelines - The ACHECKS guideline selector still offers older and regional sets, including WCAG 2.0, Section 508, BITV, and the Italian Stanca Act.
• Newer option - ACHECKS also runs AChecker+, which adds Lighthouse-based web checks and the Tingtun checker for PDFs.
• Cost - Free tools, with paid services for scheduled compliance reporting.

8. IBM Equal Access Accessibility Checker

IBM's Equal Access toolkit is open source and runs the same rules in the browser and in automated tests, so a developer can reproduce a CI failure locally with the extension.

Key facts:

• Runs on - Extensions for Chrome, Firefox, and Edge, plus the accessibility-checker npm package and Cypress and Karma wrappers for Selenium, Puppeteer, and Playwright suites.
• Standards - Its ACE rules engine checks WCAG 2.0, 2.1, and 2.2.
• Stands out for - Baselines: known issues are recorded in a baseline file so a pipeline fails only on new violations. Licensed Apache 2.0.

9. SortSite

SortSite, from PowerMapper, crawls an entire site and checks accessibility alongside other quality problems in one report, which suits teams that want a single desktop audit of a large site.

Key facts:

• Runs on - Desktop app for Windows 10+ and macOS 12+, plus a web-based OnDemand edition.
• Checks - WCAG and Section 508 accessibility, plus broken links, browser compatibility, SEO, HTML and CSS standards, and usability guidelines.
• License - Commercial, in Standard, Professional, and Developer editions, with a free trial and a 10-page online demo.

10. Accessibility Scanner (Android)

Accessibility Scanner is Google's free Android app for checking native apps on a real phone or tablet. It replaces aDesigner in this list: aDesigner's Eclipse download page no longer resolves, and its Eclipse ACTF framework last shipped a release in December 2018.

Key facts:

• Checks - According to Google's help page, it suggests fixes for content labels, touch target size, clickable items, and text and image contrast.
• How it runs - A floating button captures a single screen snapshot or records a workflow as you move through the app.
• Requirements and limits - Android 9.0 or later (an older version supports Android 6.0 to 8.0). Google notes it is not a replacement for manual testing.

11. Firefox Accessibility Inspector

The Accessibility Inspector is built into Firefox Developer Tools and shows the accessibility tree that assistive technology reads, with roles, names, and states for each node.

Key facts:

• Check for issues - Mozilla's documentation lists checks for contrast, keyboard navigation, and missing text labels.
• Simulation - A simulator shows the page as users with color vision deficiencies or contrast sensitivity loss would see it.
• Tab order - Show Tabbing Order overlays the tab sequence on the page; it is a snapshot taken when the checkbox is selected, not a live view.

12. Chrome DevTools Accessibility Panel

Chrome DevTools exposes accessibility data next to the DOM, which makes it the fastest place to debug why a screen reader announces an element the way it does.

Key facts:

• Accessibility tab - Shows the accessibility tree, ARIA attributes, and computed accessibility properties for the selected node, and can replace the DOM tree with a full-page accessibility tree.
• Vision and contrast - The Rendering tab emulates several vision deficiencies, and DevTools can find low-contrast text and suggest better colors.
• Source order - The Source Order Viewer numbers elements in source order, which helps catch reading-order and focus problems.

13. Dyno Mapper

Dyno Mapper is a cloud platform that tests and monitors whole sites, including pages behind a login, and tracks an accessibility score over time.

Key facts:

• Standards - WCAG 1.0 through 2.2 at Levels A, AA, and AAA, plus Section 508, BITV 1.0, and the Stanca Act.
• Issue types - Findings are split into known problems, likely problems that need human review, and potential problems that need human verification.
• Monitoring - Scheduled testing with email alerts on new issues, CSV and PDF exports, and integrations such as Jira, Asana, Figma, and WordPress.

14. NVDA (NonVisual Desktop Access)

NVDA is a free, open-source screen reader for Windows from NV Access, used by blind and low-vision people and by testers checking how pages are actually announced.

Key facts:

• Runs on - Per NV Access, 64-bit Windows 10, Windows 11, and Windows Server from 2016, including ARM64 on Windows 11.
• Speech and braille - A built-in synthesizer supports over 55 languages, and it drives many refreshable braille displays, including braille keyboard input.
• License - Free and open source, extended through community add-ons written in Python.

15. JAWS (Job Access With Speech)

JAWS is Freedom Scientific's commercial screen reader for Windows, common in enterprise and government settings, and worth including in a test matrix alongside NVDA because the two announce some patterns differently.

Key facts:

• Speech and braille - Speech output plus braille input and output across a wide range of braille displays.
• AI assistance - Freedom Scientific describes AI-assisted exploration of complex pages and task guidance through Vispero Companion.
• License - Commercial: professional, home, and annual home subscriptions, with legacy perpetual options and a free trial.

16. VoiceOver (macOS/iOS)

VoiceOver is the screen reader built into every Mac, iPhone, and iPad, so it is the default way to test how Safari and native Apple apps are announced, at no extra cost.

Key facts:

• Rotor - The VoiceOver rotor lets users jump between headings, links, landmarks, and form controls, which is how many users scan a page.
• Braille - Supports Bluetooth braille displays, router keys, and braille keyboard input.
• Configuration - VoiceOver Utility changes the voice, verbosity, and navigation options, so testers can match common user settings.

17. ChromeVox (Chrome OS)

ChromeVox is the screen reader built into ChromeOS, relevant when a product targets schools and organizations that standardize on Chromebooks.

Key facts:

• Turning it on - Ctrl + Alt + Z toggles it on standard keyboards; on tablets, hold Volume down and Volume up for 5 seconds.
• Navigation - Keyboard shortcuts jump by headings, links, form fields, and tables, and the ChromeVox menu (Search + Period) lists navigation options.
• Braille and learning - Supports braille displays over USB or Bluetooth, and includes a built-in tutorial and Learn Mode.

18. Functional Accessibility Evaluator (FAE)

FAE is an open-source web application from the University of Illinois that spiders a website and reports rule results per page and across the site.

Key facts:

• Rules - It uses the OpenA11y Evaluation Library of over 120 rules, each referencing a WCAG 2.0 Level A or AA success criterion.
• Companion tool - AInspector, a Firefox extension, runs the same library on a single page, including logged-in pages and dynamic content.
• Stands out for - Site-wide rule summaries, which show whether a failure is one page or a template-level pattern.

19. Silktide

Silktide is a website quality platform that monitors accessibility across a site and tracks progress with scores over time.

Key facts:

• Standards - Positions its checks for WCAG 2.2 and ADA obligations.
• Monitoring - Continuous monitoring with an Inspector view that visualizes each issue on the page, plus scoring that tracks improvement.
• Free option - A free accessibility checker browser tool alongside the paid platform.

20. UserWay Accessibility Scanner

UserWay's accessibility checker is a free URL scan for WCAG and ADA issues, and the entry point to the company's accessibility widget, monitoring, and audit services.

Key facts:

• Free scan - Enter a URL to get an instant report of WCAG and ADA issues on desktop and mobile layouts.
• Prioritization - Issues are classified by urgency and importance.
• Keep in mind - The scan is automated, so it shares the limits covered in the next section; pair it with manual screen reader and keyboard testing.

21. Siteimprove Accessibility Checker

Siteimprove is an enterprise platform that monitors accessibility across an organization's whole web estate, and its free Accessibility Checker browser extension brings the same checks to a single page.

Key facts:

• Coverage - Monitoring across public and authenticated pages, documents, and PDFs, positioned for WCAG 2.2 AA, ADA Title II, Section 508, and the EAA.
• Developer workflow - Siteimprove describes accessibility agents and an MCP server that work inside VS Code, Claude Code, Figma, and CI/CD.
• Free tools - The Accessibility Checker extension and an accessibility statement generator.