Suggest a tool

Lighthouse CI vs Pa11y: open-source accessibility testing tools compared

Metrics as of , from the GitHub or GitLab API of each repository. Refreshed monthly.

Summary

Lighthouse CI: Tool suite that runs, stores and asserts against Lighthouse results in CI, with a server and dashboard.

Pa11y: Accessibility testing CLI and Node.js library that checks web pages with HTML_CodeSniffer or axe runners.

Both are listed under Accessibility testing. The table gives repository metrics from the GitHub API with their fetch date, then the documented facts used for every comparison in this category, each linked to the README or docs page it comes from. A cell reads "not documented" when the fact was not found in the project's documentation; that does not mean the feature is absent.

Side by side

Lighthouse CI and Pa11y: metrics and documented facts, in the fixed row order used for accessibility testing comparisons.
FactLighthouse CIPa11y
Stars7,09414,5361
Forks71713011
Contributors1271631
Last release2025-06-2612026-08-281
Last commit2025-06-2612026-08-281
Commits in 90 days01101
LicenseApache-2.01LGPL-3.01
Primary languageJavaScript1JavaScript1
Statusinactive1active1
Rules or standardsLighthouse regression checks for accessibility, SEO, offline support and performance source: READMEWCAG2A, WCAG2AA (default), WCAG2AAA (HTML_CodeSniffer runner only) source: README
BrowsersChrome or Chromium (chromePath option) source: Docs: ConfigurationHeadless Chrome, configured through Puppeteer launch options source: README
Framework integrationsPuppeteer scripts that prepare the browser before Lighthouse runs (puppeteerScript) source: Docs: ConfigurationTest runners HTML_CodeSniffer (default) and axe-core; custom runners as CommonJS modules source: README
CI integrationGuide with configs for GitHub Actions, Travis CI, CircleCI, GitLab CI, Jenkins, Google Cloud Build source: Docs: Getting StartedError thresholds that set the exit code, for CI builds source: README
Report formatsLighthouse JSON and HTML reports with a manifest.json (filesystem target); LHCI server or temporary public storage source: Docs: Configurationcli, csv, html, json, tsv; custom reporters source: README
Install methodnpm (npm install -g @lhci/cli) source: READMEnpm (npm install -g pa11y) source: README

1 Fetched from the GitHub or GitLab API on . Hover a value for its own date.

When each fits

Written from each project's documented scope, not from preference. Neither tool is ranked.

Lighthouse CI

Fits projects that run Lighthouse on every commit in continuous integration; its README describes tools for running, saving, retrieving and asserting against Lighthouse results. source: README

Pa11y

Fits projects that automate accessibility tests on web pages; its README describes running accessibility tests via the command line or Node.js. source: README

More on these tools

Sources

  1. GitHub REST API: repository, read
  2. GitHub REST API: repository, read
  3. GitHub REST API: contributors, read
  4. GitHub REST API: contributors, read
  5. GitHub REST API: latest release, read
  6. GitHub REST API: latest release, read
  7. GitHub REST API: commits, read
  8. GitHub REST API: commits, read
  9. README, read
  10. README, read
  11. Docs: Configuration, read
  12. Docs: Getting Started, read

Documented facts collected 2026-09-22. See the methodology for how metrics and facts are gathered.