Pa11y

Open-source command line and Node.js tool that runs automated accessibility tests on web pages, using HTML_CodeSniffer or axe.

Updated

This is a profile, built from Pa11y (open-source project)'s documentation and our own use. It is not a scored review. How we profile and review tools.

In short

The simplest way to put an accessibility check in a build script. It is ideal for catching regressions across many pages, alongside manual testing.

Made by
Pa11y (open-source project)
Pricing
Open source. Free and open source under the LGPL 3.0 licence.
Supported platforms
Node.js command line (Pa11y 10 needs Node 22.13 or later), Node.js library, CI via Pa11y CI
Categories
Accessibility tools

Overview

Pa11y is an open-source accessibility testing tool. Install it with npm, run pa11y https://example.com, and it opens the page in a headless browser and reports accessibility issues.

By default it uses the HTML_CodeSniffer rules. You can switch to axe-core, or run both in the same test. Pa11y can also perform actions before testing, such as logging in or opening a menu, so it can reach states a plain page load would miss.

For pipelines, the companion Pa11y CI tool tests a list of URLs and fails the build when new issues appear.

Key features

  • Run accessibility tests from the command line with a single command
  • Choose HTML_CodeSniffer, axe or both as the test runner
  • Node.js API that returns results as a Promise
  • Actions to log in, click or fill forms before testing
  • Pa11y CI for testing lists of URLs in a pipeline

Strengths

  • Very quick to add to scripts and CI
  • Two rule engines can be combined for broader coverage
  • Free and lightweight

Weaknesses

  • No visual interface; results are text or JSON
  • Needs a recent Node.js version
  • Automated only, so manual testing is still needed

Pricing

Free and open source under the LGPL 3.0 licence.

Supported platforms

  • Node.js command line (Pa11y 10 needs Node 22.13 or later)
  • Node.js library
  • CI via Pa11y CI

Ideal users

  • Developers who want a simple accessibility check in CI
  • Teams testing many URLs on a schedule

Accessibility support

Built for automated accessibility testing against WCAG, through HTML_CodeSniffer or axe-core.

Security features

Runs on your own machine or CI server with a headless browser, so pages are not sent to a third-party service.

AI readiness

Not an AI tool. JSON output makes results easy to feed into other systems.

Alternatives

  • axe-core

    Deque Systems

    Open-source accessibility rules engine that checks web pages against WCAG 2.0, 2.1 and 2.2 and plugs into existing automated test suites.

    Accessibility tools. Open source. Last reviewed .

    Profile
  • Lighthouse

    Google

    Google's open-source auditing tool for performance, accessibility, SEO and best practices, built into Chrome DevTools.

    Performance tools, Accessibility tools, SEO audit tools. Open source. Last reviewed .

    Profile

Final verdict

The simplest way to put an accessibility check in a build script. It is ideal for catching regressions across many pages, alongside manual testing.

Visit Pa11y

Frequently asked questions

What is the difference between Pa11y and axe-core?

axe-core is a rules engine you call from your own tests. Pa11y is a ready-made command line tool that runs a headless browser and uses HTML_CodeSniffer, axe or both to test pages.

What Node.js version does Pa11y need?

Pa11y 10 needs an even-numbered Node.js release, 22.13.0 or later. Older Node.js versions can use Pa11y 9 or earlier.

Mentioned in

Sources

  1. Pa11y on GitHub