RatedWithAI

RatedWithAI

Accessibility scanner

Free ToolsJune 17, 2026

Best Open Source Accessibility Testing Tools 2026

You don't need to spend $500/month to test for WCAG issues. The best accessibility testing stack in 2026 is largely open source — axe-core, Pa11y, jest-axe, and Playwright cover most of the automated testing layer for free. Here's what each tool does, where it fits, and what you still need to do manually.

ℹ️

Automated tools catch ~30–40% of WCAG issues

No tool — free or paid — catches everything. Automated testing must be paired with manual keyboard testing and screen reader testing to achieve meaningful WCAG coverage. This guide covers what automation catches and what it doesn't.

Quick Comparison: Open Source Accessibility Tools 2026

ToolCategoryWCAG CoverageBest ForLicense
axe-coreCore Library~57% automatedAny project — CI/CD, unit tests, browser automationMPL-2.0
WAVEManual Scanner~40% automatedVisual accessibility reviews, non-developer auditorsFree (WebAIM)
Pa11yCLI / CI Tool~40% (via axe or htmlcs)CI/CD pipelines, batch URL scanning, scheduled auditsLGPL-3.0
jest-axeUnit Test Integration~57% (inherits axe-core)Frontend teams with Jest, component-level accessibility testingMIT
Playwright + axe-playwrightE2E Testing~57% (inherits axe-core)E2E accessibility testing in CI/CD, full-page authenticated scanApache-2.0 / MIT
LighthouseAuditing Suite~30% automatedPerformance + accessibility combined audits, quick site assessmentsApache-2.0
IBM Equal Access CheckerBrowser Extension / CI~50% automatedIBM products, enterprise teams wanting a second opinionApache-2.0

Tool-by-Tool Breakdown

axe-core

github.com/dequelabs/axe-core

Core LibraryMPL-2.0

The gold standard open source accessibility rule engine. Powers Deque axe DevTools, Pope Tech, and dozens of other tools. Has the most comprehensive WCAG 2.2 rule set and is actively maintained by Deque. The axe-core library itself is MIT-licensed.

WCAG Coverage
~57% automated
False Positive Rate
Very Low
Integrations
jest-axe, playwright, puppeteer +3 more
Example usage
import axe from 'axe-core';
const results = await axe.run(document);
console.log(results.violations);

WAVE

wave.webaim.org

Manual ScannerFree (WebAIM)

Web Accessibility Evaluation Tool from WebAIM. The best free browser-based scanner for visual accessibility review. Overlays accessibility information directly on the page, making it easy for non-technical reviewers to understand issues. Not suitable for CI/CD — browser extension only.

WCAG Coverage
~40% automated
False Positive Rate
Low
Integrations
Chrome Extension, Firefox Extension, API (paid)

Pa11y

github.com/pa11y/pa11y

CLI / CI ToolLGPL-3.0

Pa11y is a Node.js command-line tool for automated accessibility testing. It runs Headless Chrome and can test URLs in batch. Uses either axe-core or HTML_CodeSniffer as its rule engine. Pa11y Dashboard provides a web interface for monitoring multiple sites over time.

WCAG Coverage
~40% (via axe or htmlcs)
False Positive Rate
Low-Medium
Integrations
GitHub Actions, Jenkins, CircleCI +2 more
Example usage
# Install and run
npm install -g pa11y
pa11y https://example.com --reporter cli

# Batch testing
pa11y-ci --sitemap https://example.com/sitemap.xml

jest-axe

github.com/nickcolley/jest-axe

Unit Test IntegrationMIT

jest-axe adds axe-core accessibility assertions to Jest. Run axe checks on rendered React, Vue, or Angular components as part of your unit test suite. Ideal for component libraries or design systems where accessibility regressions should fail tests.

WCAG Coverage
~57% (inherits axe-core)
False Positive Rate
Very Low
Integrations
Jest, React Testing Library, Vue Test Utils
Example usage
import { axe, toHaveNoViolations } from 'jest-axe';
expect.extend(toHaveNoViolations);

it('Button has no accessibility violations', async () => {
  const { container } = render(<Button>Click me</Button>);
  const results = await axe(container);
  expect(results).toHaveNoViolations();
});

Playwright + axe-playwright

github.com/abhinaba-ghosh/axe-playwright

E2E TestingApache-2.0 / MIT

axe-playwright integrates axe-core into Playwright test suites. This is the most powerful open source approach for testing authenticated SaaS applications — Playwright can log in, navigate complex flows, and run axe on each page state. Playwright's built-in accessibility tree snapshot (page.accessibility.snapshot()) provides additional structural testing.

WCAG Coverage
~57% (inherits axe-core)
False Positive Rate
Very Low
Integrations
Playwright, GitHub Actions, CircleCI +1 more
Example usage
import { checkA11y } from 'axe-playwright';

test('Dashboard has no accessibility violations', async ({ page }) => {
  await page.goto('/dashboard');
  await page.waitForLoadState('networkidle');
  await checkA11y(page, undefined, {
    runOnly: { type: 'tag', values: ['wcag2aa', 'wcag21aa', 'wcag22aa'] },
  });
});

Lighthouse

github.com/GoogleChrome/lighthouse

Auditing SuiteApache-2.0

Google's Lighthouse includes an accessibility audit using axe-core under the hood, combined with additional checks. Scores 0–100 on accessibility. Note: the Lighthouse accessibility score does NOT equate to WCAG conformance — a 100 score does not mean WCAG AA conformant. Use it as a quick signal, not a compliance benchmark.

WCAG Coverage
~30% automated
False Positive Rate
Low
Integrations
Chrome DevTools, CLI, Node.js API +1 more
Example usage
# CLI usage
npx lighthouse https://example.com --only-categories=accessibility

# CI with budget
npx lhci autorun --budget-path=budget.json

IBM Equal Access Checker

github.com/IBMa/equal-access

Browser Extension / CIApache-2.0

IBM's open source accessibility checker. Includes browser extensions and a Node.js API for CI integration. Uses IBM's own rule set (ACT-rules based) which often catches different issues than axe-core. Running both axe-core and IBM's checker in CI provides broader coverage than either alone.

WCAG Coverage
~50% automated
False Positive Rate
Low-Medium
Integrations
Chrome Extension, Firefox Extension, Node.js API +2 more
Example usage
const { getCompliance } = require('accessibility-checker');
const results = await getCompliance(document, 'testLabel');
console.log(results.report.results);

Recommended Open Source Stack by Team Type

⚛️

Frontend Dev Team (React/Vue/Angular)

  • jest-axe for component-level unit tests
  • Playwright + axe-playwright for E2E flows
  • axe browser extension for manual review during development
  • Pa11y-ci for scheduled full-site scans
👤

Solo Developer / Freelancer

  • WAVE browser extension for quick visual reviews
  • axe DevTools browser extension (free tier) for detailed audit
  • Lighthouse in Chrome DevTools for quick score
  • Pa11y CLI for batch scanning before launch
🏢

Enterprise / Compliance Team

  • axe-core via Playwright in CI/CD pipeline
  • IBM Equal Access Checker for second-opinion coverage
  • Pa11y Dashboard for monitoring production across multiple URLs
  • Manual screen reader testing protocol (NVDA, JAWS, VoiceOver)
  • RatedWithAI or Pope Tech for continuous monitoring + reporting
🔍

QA / Non-Developer Auditors

  • WAVE browser extension as primary visual scanner
  • axe DevTools browser extension for detailed rule information
  • Keyboard-only navigation testing protocol
  • Screen reader testing: NVDA+Firefox, VoiceOver+Safari

What Open Source Tools Can't Do

Even the best open source accessibility testing stack has gaps you need to close manually:

  • Alt text quality — Tools detect missing alt text, but not whether existing alt text is actually descriptive and useful.
  • Reading order logic — Automated tools can check DOM order, but not whether the reading sequence makes sense for the content.
  • Link purpose — "Click here" and "Read more" fail WCAG 2.4.4, but automated tools often miss these in context.
  • Cognitive complexity — WCAG 2.2 added criteria around cognitive load (focus appearance, accessible authentication) that require human judgment.
  • Authenticated flows — Pa11y and Lighthouse can be configured for authenticated testing, but it requires setup. Playwright handles this best.
  • Real screen reader behavior — axe-core tests the DOM model, not actual screen reader output. VoiceOver and NVDA may behave differently than the DOM model predicts.

When to Add Paid Monitoring

Open source tools cover the development-time testing layer well. What they don't cover is production monitoring — catching accessibility regressions after code ships.

If your site or app is updated regularly (content management, deployments, plugin updates), adding continuous monitoring with a tool like RatedWithAI or Pope Tech is worth it. The automated monitoring runs on a schedule, alerts you when new issues appear, and maintains a compliance history that's useful for VPAT documentation and legal defense.

Monitor your site for accessibility regressions

Open source tools are great for development-time testing. RatedWithAI adds continuous production monitoring so regressions are caught when they ship, not months later when a plaintiff finds them first.

Start Monitoring Free →

Frequently Asked Questions

Is axe-core the same as Deque's paid axe DevTools?

axe-core is the open source rule engine (MPL-2.0 license) that powers Deque's paid axe DevTools. The core rules are the same. axe DevTools Pro adds intelligent guided testing, WCAG 2.2 expanded rules, issue management, and team reporting on top of the open source engine. For most development use cases, axe-core (free) and the free tier of axe DevTools browser extension are sufficient.

Can I use Pa11y for continuous monitoring instead of a paid tool?

Pa11y CI and Pa11y Dashboard can be self-hosted for continuous monitoring. This requires infrastructure setup and maintenance. Pa11y Dashboard stores historical data and provides a web interface. The trade-off is engineering time to configure and maintain versus the simplicity of a paid SaaS monitoring tool. For teams with DevOps capacity, Pa11y Dashboard is a viable free alternative.

Does Lighthouse give an accurate accessibility score?

Lighthouse's accessibility score (0–100) reflects how many of its audits a page passes, not actual WCAG conformance. A 100 Lighthouse accessibility score does not mean WCAG 2.2 AA conformant — Lighthouse covers about 30% of automated-testable WCAG criteria. Use Lighthouse as a quick health signal, not a compliance benchmark.

What's the best open source screen reader for testing?

NVDA (NonVisual Desktop Access) for Windows is free and open source, and it's the most widely used screen reader globally. Pair it with Firefox for the most common real-world AT combination. VoiceOver is built into macOS and iOS (free but not open source). JAWS is the dominant enterprise screen reader but is paid ($90–$1,100/year). For most testing, NVDA + Firefox and VoiceOver + Safari together cover the majority of real-world AT usage patterns.

Can I use open source tools to produce a VPAT?

Open source tools can provide the testing data that informs a VPAT, but the VPAT document itself is a structured report that requires human judgment about conformance levels for each WCAG criterion. You can use axe-core, Pa11y, and manual testing to gather findings, then document them in the VPAT/ACR format. Enterprise buyers often prefer VPATs produced or validated by recognized third-party accessibility firms.

Related Guides