axe vs WAVE vs Lighthouse vs Pa11y: Accessibility Testing Tools Compared (2026)

axe is built around axe-core, an open-source JavaScript accessibility testing engine maintained by Deque Systems. axe-core is designed for zero false positives by default, meaning every issue it reports is a genuine WCAG violation. This philosophy makes it the most trusted engine for automated pipelines where false positives waste developer time and erode trust in the tool.

axe-core can be integrated into Cypress, Playwright, Selenium, Jest, and virtually any JavaScript-based test framework via packages like @axe-core/playwright and cypress-axe. This means accessibility checks run alongside your functional tests in CI, catching regressions before they reach production. The free axe DevTools browser extension provides a developer-friendly way to audit pages manually during development.

Deque's paid products build on axe-core. axe DevTools Pro adds guided manual testing workflows that cover the WCAG criteria automated tools cannot catch (like focus order, reading order, and alternative text quality). axe Monitor provides ongoing site-wide scanning and dashboards. The commercial products are expensive but comprehensive; the open-source core is what most teams start with and it is genuinely excellent on its own.

WAVE, maintained by WebAIM at Utah State University, takes a fundamentally visual approach. Instead of outputting a list of violations in a console or report, WAVE overlays icons directly on the page next to the elements that have issues. Red icons for errors, yellow for warnings, green for features (like alt text present), and purple for structural elements (headings, landmarks, ARIA). This visual overlay makes WAVE the most intuitive tool for non-developers to understand.

The free browser extension (available for Chrome and Firefox) is the most common way to use WAVE. It provides a sidebar with a summary of errors, contrast issues, alerts, and structural information. The contrast checker is particularly useful, showing the exact contrast ratio and WCAG compliance level for every text element. WAVE also flags document structure issues like skipped heading levels and missing landmarks that other tools sometimes overlook.

For teams that need programmatic access, the WAVE API allows page scanning via HTTP requests with JSON responses. Pricing is credit-based and affordable for moderate usage. WAVE does not integrate into test frameworks the way axe-core does, so it is better suited for manual audits and content workflows than CI/CD pipelines.

Lighthouse is Google's open-source auditing tool, built into Chrome DevTools and available as a Node CLI and CI package. It audits pages across four categories: Performance, Accessibility, Best Practices, and SEO. The accessibility audit uses axe-core under the hood, which means its violation detection accuracy is the same as axe, but it presents results as a 0-100 score alongside the other audit categories.

The convenience of Lighthouse is its main selling point. Every Chrome user already has it in DevTools (right-click, Inspect, Lighthouse tab, run). The score provides a quick pulse check, and the detailed results link directly to web.dev documentation explaining each issue and how to fix it. For CI, the Lighthouse CI package supports assertions (fail the build if the accessibility score drops below 90) and result storage for trend tracking.

The limitation is depth. Because Lighthouse runs a broad audit across multiple categories, its accessibility coverage is necessarily a subset of what a focused tool like axe DevTools Pro or WAVE provides. It runs the axe-core rules but does not include the additional heuristic checks that WAVE performs. It is a starting point, not a comprehensive accessibility testing strategy.

Pa11y is an open-source accessibility testing tool designed specifically for automation and CI/CD. It runs from the command line or as a Node.js library, takes a URL, and outputs accessibility violations as JSON, CSV, or CLI-formatted text. It supports two runners: axe (using axe-core) and htmlcs (using HTML_CodeSniffer), and you can configure which WCAG level to test against (A, AA, or AAA).

Pa11y CI is the companion tool for continuous integration, designed to test multiple URLs defined in a configuration file and fail the build if violations are found. Pa11y Dashboard provides a simple web interface for tracking results over time, though it is less polished than commercial alternatives. The Pa11y ecosystem is small but focused: it does one thing (automated accessibility scanning) and does it well.

The key advantage of Pa11y is control. You can configure exactly which runner to use, which WCAG level to enforce, which rules to ignore, and how results are formatted. It runs headless Chromium via Puppeteer, supports authentication via actions (click, set field value, wait), and can test pages behind login flows. The disadvantage is that it requires command-line comfort and has no visual output.