axle · honest comparison

axle vs Pa11y vs Lighthouse vs WAVE vs axe DevTools vs accessiBe

Built by axle, but written for teams choosing tools. The page below is honest about what each tool is for — including where alternatives are better. The big idea: most accessibility tools are built on the same engine (axe-core 4.11); the real differentiation is delivery surface, CI integration, AI-assisted remediation, and regulator- ready artifacts.

Side-by-side — pick the right tool for the job

ToolEngineCIAI fixesReportsRegulator artifactsPrice
axle
site →
axe-core 4.11 (same as below)GitHub Action + npm CLI + Netlify / Cloudflare / Vercel / WordPress pluginsClaude Sonnet code-fix diffs in PR commentsSticky PR comment + JSON + Markdown + public /r/<id> shareable URLPer-PR scan history, statement generator (EAA / ADA / 35), VPAT-grade evidenceFree 1 repo · $49/mo Team · $299/mo Business
Pa11y
site →
axe-core or HTML CodeSnifferPa11y CI (npm) + Pa11y Dashboard (self-host)NoneJSON / CSV; Dashboard for trend tracking (self-hosted)Self-hosted history; nothing pre-built for regulatorsFree / open source; self-host costs
Lighthouse CI
site →
axe-core (subset) + custom rules; performance-focusedLighthouse CI Action; chromium-basedNoneLighthouse score, JSON outputPerformance + best practice + a11y blended score; not WCAG-mappable line-by-lineFree / open source
WAVE (WebAIM)
site →
Proprietary; widely used by plaintiff firmsBrowser extension; WAVE API (paid) for programmaticNoneVisual annotated overlay on the pageManual screenshots; no native CI integrationFree browser tool · paid API for automation
axe DevTools (Deque)
site →
axe-core (Deque is the maintainer)axe-core CLI (open source) + paid Pro / Watcher tiersIntelligent Guided Tests, no fix-diff generationJSON, browser DevTools panel, dashboard (Pro+)Audit history (Pro+); enterprise ARM compliance reportsaxe-core CLI free; axe DevTools Pro $40/mo per dev; Watcher enterprise (call for quote)
accessiBe / UserWay / AudioEye
site →
Runtime overlay widget — not a scannerDoesn't applyAuto-injected ARIA at runtimeVendor-published 'compliance score' (questioned by regulators)Vendor-issued statement; FTC fined accessiBe $1M for accuracy in Jan 2025$5K-$20K/year typical

When to pick which

Pick Pa11y when

You want full control, self-hosted, OSS-only, no SaaS, no AI

Pa11y Dashboard is genuinely good for teams with the operations capacity to host it. No AI fix generation, no PR-comment integration out of the box (you'd build that yourself), but the engine is the same axe-core under the hood.

Pick Lighthouse CI when

You already use Lighthouse for performance and a11y is one of several quality bars

Lighthouse blends performance + a11y + best-practices into one score. Great for general quality regression but not WCAG-mappable line-by-line — it lumps issues. If you need to report 'we passed WCAG 4.1.2 specifically', Lighthouse won't tell you that.

Pick WAVE (WebAIM) when

Single-page manual audits with visual feedback; lawyer / auditor reference

WAVE's annotated overlay is excellent for understanding violations visually. Plaintiff firms cite WAVE alongside axe-core. Use it for one-off audits, not CI — the WAVE API is paid + their CI story is rough.

Pick axe DevTools (Deque) when

You're a Fortune 500 with a budget and want the canonical Deque stack

Deque maintains axe-core. The Pro / Watcher tiers add intelligent guided tests, dashboards, Issue tracking. Per-seat pricing means it scales with engineer headcount, not site count. Best fit if you have deep pockets and lots of engineers.

Pick accessiBe / UserWay / AudioEye when

You want an overlay widget

Don't. The FTC fined accessiBe $1M in January 2025 for deceptive compliance claims. EAA 2025 / EN 301 549 evaluate served HTML, not runtime ARIA. See the full breakdown at /why-not-overlay.

Pick axle when

You want CI scans on every PR + AI fix diffs + the regulator-graded artifacts (statement, audit trail) for under $300/mo

The use case axle was designed for. Free for one repo, $49/mo for hosted AI fixes + multi-repo, $299/mo for unlimited repos + EAA language pack. Same axe-core engine as Pa11y / Lighthouse / Deque axe DevTools, just packaged for the compliance workflow rather than as a developer-experience tool.

FAQ

Aren't most of these the same engine?

Yes — axle, Pa11y (in axe-core mode), Lighthouse, axe DevTools, and Microsoft Accessibility Insights all use axe-core. The differentiation is the delivery surface: how the violations are surfaced to engineers, how they integrate with CI, what artifacts they produce, and what AI-assisted remediation they offer. Same engine in different boxes.

Can I use multiple tools together?

Yes — common stacks: Lighthouse CI for performance + a11y blended score, axle for the deep WCAG view + statement / audit-trail. Or Pa11y self-hosted for the dashboard + axle Action for the AI fix suggestions on PR. The engines are compatible because they're the same engine under the hood.

Is axle just “Pa11y with AI”?

Roughly accurate but missing the regulator-artifacts piece. axle ships the things a compliance officer asks for after the scan — accessibility statement generator (EAA, ADA, Israeli תקנה 35), VPAT-grade evidence chain, public shareable scan results. Pa11y is positioned as a developer tool; axle is positioned as a compliance workflow that happens to also be a developer tool.

Why don't you compare against accessiBe properly?

Because it's not in the same category. Overlay widgets are a different product class — they don't produce CI reports, don't scan source HTML, and the FTC just fined the largest vendor $1M for deceptive marketing in January 2025. The honest comparison is “accessibility scanner + CI” vs “runtime overlay widget”, not “axle vs accessiBe”. See /why-not-overlay.

Try axle before deciding

The fastest way to evaluate axle is the same way you'd evaluate Pa11y or Lighthouse: run it once. The free scan returns the full WCAG 2.2 AA report by email; no signup, no credit card.