axe-playwright

Overview

axe-playwright is a free, MIT-licensed package for adding axe-core accessibility checks to Playwright tests. It suits development teams already using Playwright who want automated checks in their browser test workflow; it is a narrower choice for anyone seeking manual review or advice on fixing findings.

Key features

Its commands cover injecting and configuring axe, running checks, retrieving results and violations, and reporting findings. Scans can target a full page or a selected DOM context, useful for checking either an end-to-end view or a particular component. Configurable axe.run settings, impact filters, detailed reports, and verbose output let teams tune what gets checked and how much detail they see.

The integration works with Playwright’s Chromium, Firefox, and WebKit browsers. The README demonstrates checks tagged for WCAG 2.1 AA, WCAG 2.2 AA, best practices, and EN 301 549; stated coverage is WCAG 2.2. These automated scans can bring accessibility checks into routine tests, but they do not replace manual review, and the package offers no remediation guidance. Teams need a separate process to assess issues that automation does not address and decide how to fix findings.

Reporting options include default and v2 terminal output, HTML, and JUnit. That range can serve both local inspection and test-reporting workflows. The optional skipFailures setting logs violations without failing a test, which may be useful when teams want to collect findings without interrupting a run. It also means teams should decide whether accessibility violations need to block tests rather than letting that choice happen by default.

The package is installed alongside Playwright as an npm development dependency, and axe-core is bundled, so it does not need separate installation. Its README says it is not formally affiliated with Deque Systems, though it uses axe-core with permission.

Pricing

axe-playwright is free: its plan costs nothing. The package is MIT-licensed, with Playwright as a peer dependency. There are no paid tiers to weigh against the free option; teams do need Playwright in their development setup to use the integration.

Platforms

axe-playwright is available for Linux and the web. Browser checks run through Playwright’s Chromium, Firefox, and WebKit support. It has CI/CD integration, but no mobile testing, browser extension, manual review tools, or remediation guidance.

Who it's for

This is a good fit for developers and teams with existing Playwright tests who want configurable automated accessibility checks and reports in those workflows. It is not a complete accessibility testing solution for teams that need mobile coverage, guided remediation, or manual review capabilities in the same product.

Pros and cons

• Pros: Free and MIT-licensed, with axe-core bundled, so there is no separate engine installation.
• Pros: Supports page-wide and selector-scoped checks across Chromium, Firefox, and WebKit, with multiple reporting formats.
• Cons: Requires Playwright as a peer dependency, so it is not a standalone option for teams using another test workflow.
• Cons: Automated scans do not provide manual review or remediation guidance, leaving assessment and fixes to the team.
• Cons: No mobile testing or browser extension is provided.

Alternatives

If your need is accessibility testing software beyond a Playwright integration, compare Accessibility Testing Software. The Runtime Version Managers directory is a better starting point when the problem is managing language or runtime versions instead.

For version management rather than accessibility checks, GHCup handles Haskell toolchain installation and management, while Jabba is a Java version manager. rustup manages Rust toolchains, elan manages Lean versions, and fnm and nvm are options for Node.js version management. mise and asdf are open-source tool version managers. These tools address version management, not axe-playwright’s accessibility-testing role.

Verdict

Choose axe-playwright if your team already runs Playwright tests and wants free, configurable axe-core checks with reporting across its supported browsers. Its strongest case is fitting automated accessibility checks into an existing test workflow. Look elsewhere if you need mobile testing, manual review, or guidance for resolving findings.