Different types of accessibility testing tools

Here is a wide range of tools and approaches that help teams identify and address accessibility issues, from design and content through to development, testing and automation.

Table of contents

Introduction

Tools are only part of the process

Accessibility testing tools can help identify issues and prevent regressions, but no single tool can find every accessibility issue. They don't replace manual testing, assistive technology testing or testing with people with disability.

How to use this page

The sections move from automated tools through to hands-on testing:

Tools are listed alphabetically within each section. All external links open in a new tab.

A note about inclusion

Apart from Intopia's own resources, inclusion in this list does not imply endorsement by Intopia.

Automated accessibility scanning tools and platforms

These tools range from individual page scanners to platforms for checking multiple pages and managing accessibility issues across websites.

Good for: running automated checks, scanning multiple pages, monitoring sites over time, and reporting issues across teams. Capabilities vary between tools.

Limitations: automated checks detect only a portion of accessibility issues. They cannot judge whether content is meaningful, such as whether alt text accurately describes an image. Results still need manual review.

Automated accessibility scanning tools and platforms
Tool Platform Cost Typical users
Deque Axe Web platform Paid Developers, testers, accessibility teams
Level Access Web platform Paid Developers, testers, accessibility teams
Monsido Web platform Paid Content teams, accessibility teams
Tanaguru Web platform, including multi-page user journeys Free and paid options Testers, accessibility teams
UsableNet AQA Web platform Paid Developers, testers, accessibility teams

Developer and CI tools

These tools let developers run automated accessibility checks inside their own code, unit tests and build pipelines.

Good for: catching issues early and preventing regressions before code is deployed.

Limitations: they share the limits of all automated testing, and require developer setup and maintenance.

Developer and CI tools
Tool Platform Cost Typical users
axe-core JavaScript accessibility rules engine, used by many of the tools on this page Free (open source) Developers
Cypress with cypress-axe Browser testing framework, with axe-core added through a plugin Free (open source) Developers, testers
Pa11y Command line tool and CI runner Free (open source) Developers
Playwright with @axe-core/playwright Browser testing framework, with axe-core added through a package. Also includes role-based locators and ARIA snapshot testing Free (open source) Developers, testers

Automated mobile tools

These tools provide automated testing for accessibility on mobile devices.

Good for: checking native apps for issues like missing labels, small touch targets and low contrast.

Limitations: like the automated web tools above, they find only a portion of issues. Apps should also be tested with VoiceOver and TalkBack.

Automated mobile tools
Tool Platform Cost Typical users
Android Accessibility Scanner Android Free Testers, developers
Android Studio Lint Android Studio Free Developers
Axe for Android Android Paid Developers, testers
iOS Accessibility Inspector Xcode on macOS Free Developers, testers

Browser extensions

These tools allow us to check aspects of accessibility directly in the browser.

Good for: quick checks of a single page, highlighting issues visually on the page, and learning about common issues.

Limitations: they test one page or state at a time. Different extensions use different rules, so results may vary between tools.

Browser extensions
Tool Platform Cost Typical users
AccessUX SiteScan Chrome Free Designers, developers, testers, content authors
Accessibility Insights for Web Chrome or Edge Free Developers, testers
ARC Toolkit Chrome, Firefox or Edge Free Developers, testers
axe DevTools Chrome, Firefox or Edge Free, with paid features Developers, testers
Tota11y: Accessibility toolkit Firefox Free Developers, designers
WAVE Evaluation Tool Chrome, Firefox or Edge. Also available as an online service Free Developers, testers, content authors
Web Developer extension Chrome, Firefox or Opera Free Developers, testers
WICK-AG-Lens: Accessibility Inspector Chrome Free Developers, testers

Built-in browser tools

These tools come built into browser developer tools, so nothing needs to be installed.

Good for: inspecting the accessibility tree, and checking the names, roles and states that are passed to assistive technologies.

Limitations: they show what the browser exposes, not how a specific screen reader will announce it. Some technical knowledge is needed to interpret results.

Built-in browser tools
Tool Platform Cost Typical users
Chrome DevTools Accessibility pane Chrome Built in Developers, testers
Firefox Accessibility Inspector Firefox Built in Developers, testers
Lighthouse Chrome and Edge DevTools (also available as an extension and command line tool) Built in Developers
Safari Web Inspector Safari on macOS Built in Developers, testers

Bookmarklets

Simple tests that allow us to test individual accessibility issues.

Good for: highlighting one specific feature on a page, such as headings, focus order or alt text. They work in most browsers and need no installation.

Limitations: they show what is on the page but do not decide whether it is correct. Some websites block bookmarklets from running.

Bookmarklets
Tool Platform Cost Typical users
A11y audit bookmarklets Any browser Free Testers, developers
ANDI Accessibility Testing Tool Any browser Free Testers, developers
Intopia's accessibility testing bookmarklets Any browser. Over 40 bookmarklets covering page structure, tables, focus, names, forms, ARIA states and properties, and colour contrast, each with its own test page Free Testers, developers
JavaScript Bookmarklets for Accessibility Testing Any browser Free Testers, developers

Colour contrast tools

These tools are focused on testing colour contrast.

Good for: precise contrast ratio checks, including on design files before anything is built.

Limitations: most test one colour pair at a time. Text over images, gradients and transparent colours can be difficult to measure accurately.

Colour contrast tools
Tool Platform Cost Typical users
Colour Contrast Analyser (CCA) Mac, Windows Free Designers, testers
Stark Figma and Sketch plugins Free, with paid features Designers
WebAIM Color Contrast Checker Web Free Designers, developers, testers

Content testing tools

These tools test the readability and clarity of written content.

Good for: spotting long sentences, complex words and passive voice, and estimating reading level.

Limitations: readability formulas measure word and sentence length, not real understanding. Most are designed for English. They do not replace testing content with real users.

Content testing tools
Tool Platform Cost Typical users
Grammarly Web, desktop, browser extension Free, with paid features Content authors
Hemingway Web, desktop Free, with paid features Content authors
Readability Bookmarklet Any browser Free Content authors, testers
Readability Test Web Free Content authors

Keyboard testing

Testing with only a keyboard requires no tools and can be done in any browser.

Good for: checking that everything can be reached and used without a mouse, that focus order is logical, that focus is always visible, and that there are no keyboard traps.

Limitations: it does not tell you what a screen reader announces.

Keyboard testing
Tool Platform Cost Typical users
Keyboard-only navigation (Tab, Shift+Tab, Enter, Space, arrow keys, Escape) Any browser Built in Everyone

Screen readers

These are the most commonly used screen readers across desktop and mobile devices.

Good for: confirming that headings, labels, roles and states actually work for screen reader users, especially for complex components such as menus, dialogs and forms.

Limitations: there is a learning curve, and testing takes longer. Behaviour can differ between screen reader and browser combinations, so testing with one screen reader does not cover them all.

Screen readers
Tool Platform Cost Typical users
JAWS - Job Access With Speech Windows Paid Testers, developers
NVDA - NonVisual Desktop Access Windows Free Testers, developers
TalkBack Android Built in Testers, developers
VoiceOver macOS and iOS Built in Testers, developers

Screen magnification and low vision tools

These tools enlarge content or change how it is displayed.

Good for: checking that content reflows, text resizes without loss of content, and nothing is cut off or overlaps when zoomed.

Limitations: they show the experience of zooming, but low vision needs vary widely. Results should be combined with other testing.

Screen magnification and low vision tools
Tool Platform Cost Typical users
Browser zoom Any browser Built in Everyone
macOS Zoom macOS Built in Testers, designers
Windows Magnifier Windows Built in Testers, designers
ZoomText Windows Paid Testers

Languages and formats for describing accessibility

These are not testing tools. They are structured ways of writing down accessibility requirements, test cases, test rules or results, so that everyone on a team can read and agree on them. Many can be connected to the tools above to run as automated tests.

Good for: turning accessibility requirements into clear, shared acceptance criteria. They help designers, product owners, testers and developers describe the same behaviour in the same way.

Limitations: a test is only as good as what it describes. Writing good scenarios still needs accessibility knowledge, and automated runs still need to be checked with assistive technology.

Languages and formats for describing accessibility
Language What it describes Maintained by Typical users
ACT Rules Format (Accessibility Conformance Testing) Test rules: a standard format for writing accessibility test rules, so different tools and testers get consistent results W3C Tool makers, accessibility specialists
EARL (Evaluation and Report Language) Test results: a machine-readable format for recording and sharing accessibility test results W3C Tool makers, developers
Gherkin Behaviour scenarios: plain-language "Given, When, Then" steps that can describe accessible behaviour and be run by frameworks such as Cucumber Cucumber open source project Product owners, testers, developers
UCDL (Use Case Definition Language) Accessibility use cases: user tasks written as readable steps, with elements identified by role and accessible name, that can be run as automated browser tests AFixt Testers, product owners, developers