axe-playwright

axe-playwright is a free, open-source bridge between the axe-core accessibility engine and Playwright test suites. It suits development teams that want WCAG-oriented checks embedded in browser tests across multiple engines. Choose it for configurable automation and report output; look elsewhere if you need manual assessment, mobile coverage, or help fixing findings.

Overview

This npm development dependency adds accessibility commands to Playwright workflows, with axe-core bundled so a separate axe-core installation is unnecessary. It is designed for teams already maintaining Playwright tests rather than for organizations seeking a standalone accessibility review product. The MIT license and zero price remove procurement barriers, while the package's stated coverage reaches WCAG 2.2.

Key features

The command set covers injection, configuration, scanning, result retrieval, violation retrieval, and reporting: injectAxe, configureAxe, checkA11y, getAxeResults, getViolations, and reportViolations. That gives developers control over whether a test simply checks a page, collects data for later handling, or emits a formatted report.

Analysis can run against an entire page document or a selected DOM context such as a selector. Page-wide scans provide broad regression coverage; selector-based checks are more practical for component-level tests and can keep a failure tied to the part of the interface under development.

Configuration accepts axe.run settings, custom impact filtering, detailed reports, and verbose output. The README demonstrates tags for WCAG 2.1 AA, WCAG 2.2 AA, best-practice, and EN 301 549 checks. An optional skipFailures mode records violations without failing the test. That is useful for inventory or gradual adoption, but it also lets known issues pass through a pipeline unless the team treats the resulting reports as release criteria.

Output can use default terminal or v2 terminal formatting, HTML, or JUnit. Terminal output supports local debugging, while HTML and JUnit fit broader reporting and CI systems. The integration runs with Playwright's Chromium, Firefox, and WebKit browsers, making engine-specific regression checks possible. It does not provide manual review tools, remediation guidance, mobile testing, or a browser extension, so automated results still require separate interpretation and follow-up work.

Pricing

The axe-playwright plan costs free. It is MIT-licensed software with Playwright as a peer dependency, so there are no paid tiers, seat charges, quotas, or trial terms to weigh. This is the right fit for individual developers and teams that can operate an open-source package inside their own JavaScript toolchain. The trade-off is product scope rather than price: support for manual assessment, mobile testing, and remediation is not part of this package.

Platforms

Platform support is listed for Linux and the web. Browser execution follows the Playwright engines Chromium, Firefox, and WebKit, so the package is most relevant to web projects whose automated tests already run in that ecosystem.

Who it's for

Use axe-playwright when accessibility checks belong in an existing Playwright suite, especially when the team needs selector-scoped scans, impact filters, configurable standards, and CI/CD integration. It is also a sensible option for projects that need several report formats without licensing expense.

It is a poor sole choice for accessibility programs requiring expert manual review, mobile application testing, or actionable remediation instruction. Teams without Playwright experience should also expect to adopt its npm-based test dependency and workflow rather than use it as a standalone interface.

Pros and cons

Pros

Free MIT license: removes purchase and seat-cost barriers for teams able to maintain their own test setup.

Three Playwright browser engines: supports checks in Chromium, Firefox, and WebKit workflows.

Scoped and configurable scans: page or selector targets, impact filtering, axe.run options, and verbosity suit both broad regression tests and component checks.

Flexible reporting: terminal, v2 terminal, HTML, and JUnit formats serve local and CI reporting needs.

Cons

No manual review tools: automated findings cannot replace keyboard, interaction, or expert assessment work.

No remediation guidance: teams must determine how to correct reported violations.

No mobile testing or browser extension: coverage remains centered on Playwright web tests.

Failure suppression can weaken enforcement: skipFailures may log issues without blocking a test, so governance is required.

Alternatives

For a broader directory of accessibility-focused products, see Accessibility Testing Software. The other linked tools are runtime version managers rather than accessibility-testing substitutes: choose GHCup for Haskell toolchain management, Jabba for Java versions, rustup for Rust, fnm or nvm for Node.js, and GVM for Go. ClearerVoice-Studio and RVM are also listed as free tools, but no accessibility-testing role is established for either.

Verdict

axe-playwright is a strong choice for Playwright-based web teams that want free, configurable WCAG automation integrated with CI and multiple browser engines. Its main reason to choose it is the combination of selector-level control and practical report formats at no cost. Look elsewhere—or pair it with separate assessment and remediation practices—if automated scans alone cannot meet your accessibility obligations.