Lighthouse vs Pa11y: open-source accessibility testing tools compared
Metrics as of , from the GitHub or GitLab API of each repository. Refreshed monthly.
Summary
Lighthouse: Web page auditing tool for performance, accessibility and SEO, run from Chrome DevTools, a Node CLI or module.
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
| Fact | Lighthouse | Pa11y |
|---|---|---|
| Stars | 30,7991 | 4,5361 |
| Forks | 9,7601 | 3011 |
| Contributors | 3901 | 631 |
| Last release | 2026-09-181 | 2026-08-281 |
| Last commit | 2026-09-181 | 2026-08-281 |
| Commits in 90 days | 571 | 101 |
| License | Apache-2.01 | LGPL-3.01 |
| Primary language | JavaScript1 | JavaScript1 |
| Status | active1 | active1 |
| Rules or standards | Accessibility audits, weighted by axe user impact assessments source: Docs: Lighthouse accessibility score | WCAG2A, WCAG2AA (default), WCAG2AAA (HTML_CodeSniffer runner only) source: README |
| Browsers | Chrome or Chromium 66.0 or later; detects Chrome Canary or Chrome stable by default source: README | Headless Chrome, configured through Puppeteer launch options source: README |
| Framework integrations | Puppeteer (launch Chrome with Puppeteer, then hand off to Lighthouse) source: Docs: Using Puppeteer with Lighthouse | Test runners HTML_CodeSniffer (default) and axe-core; custom runners as CommonJS modules source: README |
| CI integration | Lighthouse CI, listed as the official project for running Lighthouse on every commit source: README | Error thresholds that set the exit code, for CI builds source: README |
| Report formats | JSON, HTML, CSV (HTML by default) source: README | cli, csv, html, json, tsv; custom reporters source: README |
| Install method | npm (npm install -g lighthouse) or yarn; also a Chrome DevTools panel source: README | npm (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
Fits projects that analyze web apps and web pages; its README describes audit categories for accessibility, performance and SEO, among others. 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
- GitHub REST API: repository, read
- GitHub REST API: repository, read
- GitHub REST API: contributors, read
- GitHub REST API: contributors, read
- GitHub REST API: latest release, read
- GitHub REST API: latest release, read
- GitHub REST API: commits, read
- GitHub REST API: commits, read
- Docs: Lighthouse accessibility score, read
- README, read
- README, read
- Docs: Using Puppeteer with Lighthouse, read
Documented facts collected 2026-09-22. See the methodology for how metrics and facts are gathered.