axe-playwright

axe-playwright adds axe-core accessibility checks to Playwright tests. Its commands can inject and configure axe, check a page, retrieve results or violations, and report findings. Checks can cover a whole page or a selected DOM context, such as a selector. The package works with Playwright’s Chromium, Firefox, and WebKit browsers, and includes axe-core so it does not need to be installed separately. Options cover axe.run settings, impact filtering, detailed reports, and verbose output; an optional skipFailures setting logs violations without failing the test. Report choices include terminal output, a v2 terminal format, HTML, and JUnit. The README shows configurations for WCAG 2.1 AA, WCAG 2.2 AA, best-practice, and EN 301 549 tags, while the listed WCAG coverage is WCAG 2.2. Installation uses axe-playwright and Playwright as npm development dependencies. The project is MIT-licensed, names Abhinaba Ghosh as package author, and states that it is not formally affiliated with Deque Systems, though it uses axe-core with permission.

axe-playwright offers configurable automated accessibility checks and reporting within Playwright tests. Teams needing manual review tools, mobile testing, or remediation guidance will need capabilities beyond those listed here.

axe-playwright is for developers who want accessibility checks inside Playwright test workflows. It fits teams using Chromium, Firefox, or WebKit and configuring checks through code.

axe-playwright is an open-source bridge between the axe-core accessibility engine and Playwright test suites. It suits development teams already running browser tests who want WCAG-oriented checks in their CI workflow. The package is a strong automated testing component, but it is not a complete accessibility review or remediation system.

Overview

Installing axe-playwright and Playwright as npm development dependencies adds accessibility scanning to existing test code, while axe-core is bundled rather than requiring a separate installation. The integration runs in Playwright’s Chromium, Firefox, and WebKit browsers, making it practical for teams covering more than one browser engine. Its MIT license and zero-dollar price remove procurement barriers, although teams remain responsible for interpreting findings and correcting defects.

Key features

The command set covers injection and configuration through injectAxe and configureAxe, execution with checkA11y, result retrieval through getAxeResults and getViolations, and reporting with reportViolations. Scans can address an entire page document or a selected DOM context such as a selector. That scope control is useful for component-level checks as well as end-to-end page coverage.

Configuration supports axe.run settings, impact filtering, detailed reports, and verbose output. Reports can use default or v2 terminal formats, HTML, or JUnit, so developers can inspect findings locally while CI systems consume test-oriented output. The optional skipFailures setting records violations without failing the test; this is helpful for exploratory runs, but using it in release checks can allow known accessibility problems to pass unnoticed.

The README demonstrates WCAG 2.1 AA, WCAG 2.2 AA, best-practice, and EN 301 549 tags, with WCAG 2.2 stated as the product coverage. Automated rules can expose many detectable issues inside browser flows, but there are no manual review tools or remediation guidance. Teams therefore need separate expertise and processes for keyboard, assistive-technology, usability, and repair decisions.

Pricing

The axe-playwright plan costs free. It is MIT-licensed software with Playwright as a peer dependency, and there are no paid tiers or stated quotas, seats, trial period, or renewal terms. This makes it a straightforward fit for individual developers and teams that can operate an npm dependency inside their own test infrastructure. The trade-off is that the free package does not add hosted management, manual assessment, or guided remediation capabilities.

Platforms

axe-playwright supports Linux and the web through Playwright-based browser testing. Browser coverage includes Chromium, Firefox, and WebKit. Mobile testing and a browser extension are not provided, so mobile-focused validation requires another approach.

Who it's for

Choose axe-playwright when your team already uses Playwright and wants configurable accessibility assertions in local or CI/CD runs. It is particularly well matched to engineers who need selector-scoped checks, impact filtering, and HTML or JUnit output without licensing cost. Look elsewhere if you need manual review workflows, remediation coaching, mobile testing, or a standalone interface for non-developers.

Pros and cons

• Pros: Free, MIT-licensed distribution keeps adoption and scaling costs low.
• Pros: Chromium, Firefox, and WebKit support fits multi-browser Playwright suites.
• Pros: Page or selector scope, impact filters, and multiple report formats allow teams to tune both coverage and noise.
• Pros: CI/CD integration places accessibility checks in the same workflow as automated tests.
• Cons: No manual review tools means automated results cannot cover every accessibility concern.
• Cons: No remediation guidance leaves diagnosis and fixes to the team.
• Cons: No mobile testing or browser extension limits use beyond Playwright’s browser scenarios.
• Cons: skipFailures can weaken enforcement if violations are logged instead of made release-blocking.

Alternatives

For dedicated accessibility tooling, browse Accessibility Testing Software. If your need is runtime-version management rather than accessibility testing, the Runtime Version Managers directory is the better starting point. GHCup manages Haskell toolchains; Jabba manages Java versions; rustup manages Rust toolchains; PHPBrew builds and manages PHP versions; asdf is an open-source multi-tool version manager; chruby switches Ruby versions; elan manages Lean versions; and fnm manages Node.js versions. Pick those when version selection is the actual problem, not browser accessibility validation.

Verdict

axe-playwright is a sensible first choice for Playwright-based engineering teams that want free, configurable WCAG automation embedded in CI. Its multi-browser coverage and flexible reporting are the main reasons to choose it. Look elsewhere when accessibility work requires manual assessment, mobile coverage, or concrete remediation support.