axe-playwright
axe-playwright connects the axe-core accessibility testing engine to Playwright tests.
What axe-playwright is
axe-playwright connects the axe-core accessibility testing engine to Playwright tests. It supports Playwright’s Chromium, Firefox, and WebKit browsers, with commands to inject and configure axe, check accessibility, retrieve results or violations, and report findings. Checks can cover a page document or a selected DOM context, such as a selector. Options include axe.run settings, impact filtering, detailed reports, and verbose output; an optional setting logs violations without failing the test. Reports can use terminal, v2 terminal, HTML, or JUnit formats. The project shows configurations for WCAG 2.1 AA, WCAG 2.2 AA, best-practice, and EN 301 549 tags, and lists WCAG 2.2 coverage. Installation uses axe-playwright and Playwright as npm development dependencies; axe-core is bundled. The open-source package is distributed under the MIT License. Its README says it is not formally affiliated with Deque Systems, though it uses axe-core with permission. It is free, with a listed price of no cost.
Good
- Supports Chromium, Firefox, and WebKit.
- Can check a page or selected DOM context.
- Offers terminal, HTML, and JUnit reports.
- Bundles axe-core with the package.
Watch out
- No manual review tools.
- No mobile testing.
- No browser extension.
Who it suits
It suits developers who want accessibility checks as part of Playwright tests across Chromium, Firefox, or WebKit. It is intended for automated checks, not manual review or mobile testing.
Verdict
axe-playwright brings configurable axe-core checks and multiple reporting options into Playwright tests. It is a focused fit for automated accessibility checks, with no manual review or mobile testing tools listed.
Plans and prices
From axe-playwright's own pricing page, checked 8 Oct 2026.
| Plan | Price | What it gives you |
|---|---|---|
| axe-playwright | Free | MIT-licensed software · Playwright peer dependency |
The facts
Each one read from axe-playwright's own pages, with the date it was checked.
What it does
- Accessibility standards
- The README shows configuring checks for WCAG 2.1 AA, WCAG 2.2 AA, best-practice, and EN 301 549 tags.checked 8 Oct 2026
- Automated scans
- Yeschecked 23 Sep 2026
- Bundled engine
- The README says axe-core is bundled and does not need to be installed separately.checked 8 Oct 2026
- CI/CD integration
- Yeschecked 23 Sep 2026
- Commands
- The package provides injectAxe, configureAxe, checkA11y, getAxeResults, getViolations, and reportViolations commands.checked 8 Oct 2026
- Configurable checks
- Options support axe.run settings, custom impact filtering, detailed reports, and verbose output.checked 8 Oct 2026
- Failure handling
- The optional skipFailures setting logs violations without failing the test.checked 8 Oct 2026
- Install
- The README instructs users to install axe-playwright and Playwright as npm development dependencies.checked 8 Oct 2026
- License
- The repository is distributed under the MIT License.checked 8 Oct 2026
- Manual review tools
- Nochecked 23 Sep 2026
- Mobile testing
- Nochecked 23 Sep 2026
- Not affiliated with Deque
- The README says the project is not formally affiliated with Deque Systems, though it uses axe-core with permission.checked 8 Oct 2026
- Purpose
- Axe-Playwright provides commands to integrate the axe-core accessibility testing engine with Playwright tests.checked 8 Oct 2026
- Remediation guidance
- Nochecked 23 Sep 2026
- Report formats
- The README describes default terminal, v2 terminal, HTML, and JUnit reporting options.checked 8 Oct 2026
- Scoped analysis
- Checks can target a page document or a selected DOM context such as a selector.checked 8 Oct 2026
- WCAG coverage
- wcag 2.2checked 23 Sep 2026
Where it runs
- Browser extension
- Nochecked 23 Sep 2026
- Browser support
- The integration works across Playwright’s Chromium, Firefox, and WebKit browsers.checked 8 Oct 2026
Money
- Free plan
- Nochecked 23 Sep 2026
The company
- Maker
- The package metadata names Abhinaba Ghosh as author.checked 8 Oct 2026
The full review of axe-playwright
Overview
axe-playwright is an open-source package that brings axe-core accessibility checks into Playwright test suites. It suits developers who already run browser tests with Playwright and want automated accessibility findings in that workflow. Its value is focused: configurable checks and several report formats, not a complete accessibility review process.
Key features
The package supplies commands to inject and configure axe, run checks, retrieve results and violations, and report findings. Checks can cover a full page or a selected DOM context, giving teams a way to examine a component without limiting every scan to the entire document. Options for axe.run, impact filtering, detailed reports, and verbose output offer useful control over what runs and how much detail teams see.
Reports can be printed in default or v2 terminal formats, or generated as HTML or JUnit output. That range suits both local debugging and test pipelines. An optional skipFailures setting logs violations without failing the test; this can preserve a test run, but teams that want accessibility defects to block a build should avoid treating that setting as a default.
Playwright’s Chromium, Firefox, and WebKit browsers are supported. The project’s stated coverage is WCAG 2.2, and its configuration examples also include WCAG 2.1 AA, best-practice, and EN 301 549 tags. The README directs users to install axe-playwright and Playwright as npm development dependencies; axe-core is bundled, so it does not require a separate installation. The MIT license permits use under its terms. The project is not formally affiliated with Deque Systems, despite using axe-core with permission.
Pricing
axe-playwright costs free. The free package is MIT-licensed and has Playwright as a peer dependency, so it is aimed at teams prepared to work within a Playwright development setup. There are no paid tiers to unlock, but it is a testing integration rather than a broader accessibility service with manual review or remediation tools.
Platforms
The package is listed for Linux and the web. Its browser coverage is through Playwright’s Chromium, Firefox, and WebKit support. It is not a mobile testing tool, so teams needing mobile accessibility checks will need another approach.
Who it's for
This is a sensible choice for development teams already using Playwright who want automated axe-core checks, scoped scans, and reports that can fit into CI/CD. It is not the right standalone choice for teams that need manual accessibility review, remediation guidance, browser-extension testing, or mobile coverage.
Pros and cons
- Pro: Scans can target either a whole document or a selected DOM context, which makes the same integration useful for page-level and component-focused checks.
- Pro: HTML and JUnit reporting join two terminal formats, giving teams options for both detailed output and test-oriented reporting.
- Pro: Chromium, Firefox, and WebKit support lets teams run checks across Playwright’s three browser engines.
- Con: There are no manual review tools or remediation guidance, so automated findings do not complete the review-and-fix workflow.
- Con: Mobile testing is absent, limiting its fit for teams responsible for accessibility across device types.
- Con: skipFailures can leave violations non-blocking, so teams must choose their own enforcement policy.
Alternatives
For other software in this area, browse Accessibility Testing Software. The related Runtime Version Managers category covers a different need. GHCup is a free Haskell toolchain installer and manager, while rustup is another free option. Jabba is a free Java version manager, and fnm is a free alternative. nvm manages Node.js versions, while elan focuses on Lean version management and GVM on Go. mise is another free option. These tools address runtime or toolchain management rather than Playwright accessibility testing, so choose them when that is the task at hand.
Verdict
Choose axe-playwright if your team already uses Playwright and wants configurable, multi-browser axe-core checks inside its test workflow at no cost. Look elsewhere if you need manual review, remediation guidance, or mobile testing; those gaps keep this focused package from serving as a complete accessibility program.
Getting started
- Open the axe-playwright GitHub website
- Install axe-playwright and Playwright as npm development dependencies
- Use the bundled axe-core engine in Playwright tests
- Configure axe and select a page or DOM selector to analyze
- Choose reporting and failure-handling options for your test workflow
Limits worth knowing
The package provides automated checks but no manual review tools, mobile testing, browser extension, or remediation guidance. It is listed as free MIT-licensed software with Playwright as a peer dependency.
Questions
Is axe-playwright free?
Yes. The listed plan is free, and the package is open source under the MIT License.
Which browsers does it support?
The integration works with Playwright’s Chromium, Firefox, and WebKit browsers.
Does it include axe-core?
Yes. axe-core is bundled, so it does not need a separate installation.
Can it run in CI/CD?
Yes. CI/CD integration is listed as supported.
What reports are available?
The README describes standard terminal, v2 terminal, HTML, and JUnit reporting options.
