95.9% of the top one million home pages had detectable WCAG 2 failures in February 2026, with an average of 56.1 errors per page (WebAIM Million, 2026). The tools exist. The APIs exist. So why does almost every website still ship with accessibility bugs?
Because most teams pick the wrong scanning API for their workflow, or worse, bolt one on as an afterthought after the code ships. Catching accessibility issues during development costs far less than fixing them after launch (Deque, 2023), yet most comparison guides ignore what developers actually need: API response formats, rate limits, per-scan costs, and CI/CD integration complexity.
This post compares six third-party accessibility testing APIs on WCAG coverage, price, published rate limits and CI/CD fit. No overall "winner", the right choice depends on your team size, scan volume, and budget. We also include a11yFlow, our own API, clearly marked, so you can weigh it on the same axes as everything else.
For the full picture on accessibility testing approaches beyond APIs, see our accessibility testing tools comparison guide.
TL;DR: The top accessibility testing APIs in 2026 are WAVE API, Pa11y, Deque axe DevTools, Pope Tech, Siteimprove and BrowserStack. WAVE API is the cheapest pay-as-you-go option (100 free credits, then $0.025 to $0.04 per credit). Pa11y is free and CI/CD-native but self-hosted, and it runs no WCAG 2.2 rules by default. Deque's axe DevTools aims for zero false positives, but its CI/CD and API bundle is sold through sales. For a managed API with no infrastructure to host, a11yFlow (our own, disclosure noted) is the option we built for that gap.
Which APIs Are Worth Comparing?
Over 1.3 billion people worldwide live with some form of disability (WHO, 2024). Six third-party accessibility testing APIs cover the realistic options for developers building for that audience in 2026. Each takes a different approach, from pay-per-scan credits to self-hosted open source to enterprise platform bundles.
API | Pricing | WCAG checks | Published rate limit | Best For |
|---|---|---|---|---|
WAVE API | Pay per credit: 100 free, then $0.025 to $0.04 per credit | WCAG 2.2 and Section 508 checks | 2 simultaneous requests | Budget-conscious teams |
Pa11y | Free (LGPL-3.0 open source), you host it | WCAG 2.0 and 2.1 (no 2.2 rules by default) | None (self-hosted) | CI/CD-native pipelines |
Deque axe DevTools | Not published (CI/CD and API bundle: contact sales) | WCAG 2.0, 2.1 and 2.2 A/AA (2.2 opt-in, default 2.1 AA) | Not published | Zero false positive requirements |
Pope Tech | Free for 25 pages, Team from $25/mo, API plans from $225/mo (billed annually) | WAVE engine | Not published | Dashboard + monitoring |
Siteimprove | Not published (contact sales; Vendr average about $15.6K/yr) | WCAG 2.2 since April 2024 | 5 requests/s per API key, bursts of 50 | Combined accessibility + SEO + QA |
BrowserStack | Free plan; paid prices not published (price on request) | WCAG 2.0 to 2.2, A to AAA (default 2.1 AA) | Reports API: 1,600 requests per 5 min per user | Teams already on BrowserStack |
a11yFlow (our product) | Free 25 scans/mo (no card), then £19 to £149/mo | WCAG 2.2 A & AA (axe-core) | 5 to 120 requests/min by plan | Managed API + scoring, no self-hosting |
Prices and limits checked October 2026. Sources: WAVE API pricing and request limit; Pa11y license; Deque pricing; Pope Tech pricing; Siteimprove contract data from Vendr and API rate limit; BrowserStack pricing and API rate limit; a11yFlow pricing.
Disclosure: a11yFlow is the API we build, so treat the row above as ours, not a neutral verdict. The figures are honest and on the same axes as the others; the rest of this comparison stays vendor-neutral.
Looking for Tenon.io? It has been retired. Level Access took the Tenon.io service offline on August 7, 2023, and its API stopped responding to new requests (Level Access). The tenon.io domain now redirects to that notice.
Worth noting: several of these products share an engine. WebAIM's WAVE engine powers both the WAVE API and Pope Tech (Pope Tech). Deque's open-source axe-core powers axe DevTools, is an optional runner in Pa11y, whose default runner is HTML_CodeSniffer (Pa11y), and is the engine inside a11yFlow. BrowserStack uses its own Spectra rule engine (BrowserStack). When you compare these APIs, you're often comparing different interfaces to the same rules, and the real differences are pricing, hosting and workflow.
When we built a11yFlow's scanner, we chose axe-core as the detection engine for exactly this reason, it's the de facto standard, and its zero false positive policy means every violation we surface is actionable. We've processed thousands of scans, and the engine's consistency across different page structures is what sold us.
Which API Has the Best WCAG Coverage?
On paper, almost every option here now tests against WCAG 2.2, the current standard released in October 2023. WebAIM says WAVE includes many checks for WCAG 2.2 issues (WebAIM). axe DevTools added a WCAG 2.2 ruleset in version 4.5, though its standard configuration is still WCAG 2.1 AA (Deque). BrowserStack lets you choose WCAG 2.0, 2.1 or 2.2, with 2.1 AA as the default (BrowserStack). Siteimprove added WCAG 2.2 to its automated checks in April 2024 (Siteimprove).
Pa11y is the exception. Its default runner, HTML_CodeSniffer, works from WCAG 2.1 rules, and its axe runner only asks axe-core for rules tagged WCAG 2.0 and 2.1 (Pa11y source). Out of the box, Pa11y runs no WCAG 2.2 rules.
The WCAG 2.2 label matters less than it sounds, because most of the new criteria can't be tested reliably by a machine. axe-core has a single WCAG 2.2 rule, target size, and leaves it off by default (axe-core). Siteimprove automated the same criterion and says the remaining eight new criteria couldn't be automated in a reliable way.
Automated tools catch roughly 57% of all accessibility issues by volume (Deque, 2021). That ceiling applies regardless of which API you choose. The difference lies in how each handles the gap between what's automatable and what isn't.
Deque's axe-core engine runs its full WCAG rule set with a zero false positive policy, every flagged violation is a genuine WCAG failure. Uncertain findings go into a separate "incomplete" bucket for manual review. That distinction matters in CI/CD, where a false positive blocks your deployment.
Pa11y lets you swap engines. Run axe-core for Deque's rule set, HTML_CodeSniffer for different detection patterns, or both in the same run. Craig Abbott's study found axe-core catches 27% and Pa11y catches 20% of known issues independently, but combined, they find 35% (Craig Abbott, 2021). Running both covers blind spots neither catches alone.
Verdict: no clear winner on WCAG 2.2, because the new criteria barely automate. Deque for zero false positives. Pa11y for dual-engine flexibility, if WCAG 2.1 checks are enough.
For a detailed breakdown of how axe-core, Lighthouse, WAVE, and Pa11y compare on detection rates, see our axe vs Lighthouse vs WAVE vs Pa11y comparison. If you're new to accessibility testing altogether, start with our developer's guide to web accessibility testing.
How Does Pricing Compare at Scale?
WAVE API has the most transparent pay-as-you-go pricing here. Every new account gets 100 free credits. After that, credits cost $0.04 each for 250 to 999 ($10 minimum), $0.03 for 1,000 to 9,999, and $0.025 for 10,000 or more (WAVE API, 2026). A basic scan of one page uses 1 credit; the more detailed report types use 2 or 3 (WAVE API details). No subscriptions, no sales calls.
Pa11y costs nothing for the software itself. But self-hosting isn't free: you need a machine that can run headless Chromium, whether that's a server you rent or CI runners you already pay for.
Deque and Siteimprove both sit in the enterprise bracket. Deque sells the axe DevTools Extension (Pro) online per user, while the axe DevTools for Web bundle, which adds CI/CD and API integrations, is sold through its sales team; the pricing page publishes no prices for either (Deque, 2026). Siteimprove doesn't publish prices either. Vendr's buyer data puts its average contract value at about $15,572 a year, ranging from $15,000 to $150,000+ depending on scope (Vendr, 2026).
Pope Tech prices by page tier, with unlimited rescans inside the tier. Built on the WAVE engine, it has a free plan for 25 pages and a Team plan from $25/month (50-page tier, billed annually). Its Developer API and GitHub and Bitbucket CI/CD integration start on Business Plus, from $225/month billed annually or $270 billed monthly for a 500-page tier (Pope Tech, 2026).
BrowserStack has a free accessibility plan, but its paid accessibility plans have no published price; the pricing page asks you to request one (BrowserStack, 2026).
Prices checked October 2026. Sources: WAVE API, Pope Tech, BrowserStack, Deque, Siteimprove via Vendr, Pa11y license.
Verdict: Pa11y for high-volume pipelines (free software, you pay only for hosting). WAVE API for pay-as-you-go simplicity. Pope Tech for teams wanting WAVE's engine with a dashboard.
What Rate Limits Should You Plan For?
Rate limits decide how fast a pipeline can work through a large site. This is what each vendor publishes:
- WAVE API: no more than 2 simultaneous requests, otherwise WebAIM may rate-limit your account (WAVE API details).
- Pa11y: none, because it runs on your own machines. Throughput depends on how many headless browsers you can run.
- Deque axe DevTools: not published.
- Pope Tech: not published.
- Siteimprove: 5 requests per second per API key on average, with bursts of up to 50. Above that, the API returns HTTP 429 (Siteimprove).
- BrowserStack: its accessibility reports API allows 1,600 requests per 5 minutes per user and 160 requests per second per IP address (BrowserStack). We found no separate published cap on scans.
- a11yFlow (our product): 5 requests a minute on the free plan, 20 on Starter, 60 on Pro and 120 on Team, with monthly quotas of 25, 1,000, 5,000 and 25,000 scans (a11yFlow pricing).
Limits checked October 2026.
Which API Integrates Best with CI/CD?
Pa11y wins on CI/CD integration, it was built for pipelines from day one. Pa11y CI accepts a JSON config file, runs against a list of URLs, and returns structured exit codes your pipeline understands. No API keys, no authentication, no external dependencies.
Here's what a GitHub Actions step looks like with Pa11y:
- name: Accessibility scan
run: npx pa11y-ci --config .pa11yci.jsonThat's it. Three lines. Compare that with WAVE, where you're making HTTP requests, parsing JSON responses, and keeping to WebAIM's limit of 2 simultaneous requests. It works, but you're writing custom integration code.
Deque's CI/CD integration comes with the axe DevTools for Web bundle, which is sold through sales. BrowserStack offers a CLI tool that's straightforward but couples your accessibility testing to their broader platform subscription. Pope Tech's GitHub and Bitbucket CI/CD integration starts on its Business Plus plan.
Verdict: Pa11y for the simplest CI/CD setup. Deque for teams with enterprise budgets needing the most accurate engine. WAVE for teams that want API flexibility without a platform lock-in.
What About Legal Compliance?
More than 5,000 ADA web accessibility lawsuits were filed in 2025 (UsableNet, 2026). E-commerce takes the worst hit, accounting for roughly 70% of all ADA web lawsuits. And since June 2025, the European Accessibility Act has applied across EU member states, requiring covered digital products and services to meet accessibility standards, with penalties set nationally (AccessibleEU, 2025).
No scanning API makes you legally compliant on its own. Automated tools catch 57% of issues, the remaining 43% requires manual testing for things like reading order, cognitive clarity, and keyboard traps.
But an API in your CI/CD pipeline catches regressions before they ship. That's the difference between fixing a missing form label in a pull request and fixing it after a demand letter arrives. The six most common failures, low contrast (83.9%), missing alt text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%), and missing language attributes (13.5%), are all caught reliably by every API on this list (WebAIM, 2026).
The legal case for API scanning isn't about achieving compliance. It's about demonstrating due diligence and catching the automatable 57% before your users find it. For more on what WCAG compliance actually requires, see our complete accessibility testing tools comparison.

Who Should Choose What?
Automated testing is now standard practice in modern CI/CD pipelines. But which accessibility API fits which team? Here's what we've seen work.
Solo developers and startups: Use Pa11y. It's free, CLI-native, and you control the infrastructure. Add WAVE API credits for a second opinion on critical pages, and for WCAG 2.2 checks Pa11y doesn't run by default.
Small teams (5-20 developers): Start with WAVE API or Pope Tech. WAVE's per-credit pricing means you pay for what you use. Pope Tech adds a dashboard for non-technical stakeholders who want to track progress, though its API needs the Business Plus plan.
Enterprise teams with compliance requirements: Deque axe DevTools is the industry standard for a reason, zero false positives matter when you're reporting to legal. Siteimprove if you also need SEO and content quality monitoring in the same platform.
Teams already using BrowserStack: Their accessibility product is the path of least resistance, and it avoids managing another vendor. Paid accessibility prices aren't published, so ask for a quote before you commit.
Teams that want a managed API without self-hosting: This is the gap a11yFlow (our product) fills. You get the axe-core engine like Pa11y, but without running headless Chromium yourself, plus scoring and WCAG 2.2 remediation guidance in the response. The free tier (25 scans/month, no card) is enough to test it against your own pages before deciding.
Frequently Asked Questions
Which accessibility scanning API has the most accurate results?
Deque's axe-core engine leads on accuracy with a zero false positive commitment, every violation it flags is a genuine WCAG failure (Deque, 2025). The trade-off is it may flag fewer total issues than WAVE, which includes alerts and warnings alongside errors. For CI/CD pipelines where false positives block deployments, axe-core's precision matters most.
Can I use multiple accessibility APIs together?
Yes, and the data supports it. Testing both axe-core and Pa11y against 142 known accessibility issues, axe-core found 39 (27%) and Pa11y found 29 (20%), but combined they found 49 unique issues (35%) because each caught problems the other missed (Craig Abbott, 2021). Run your primary API in CI/CD and a secondary one on scheduled scans.
Is WAVE API good enough for WCAG 2.2 compliance?
WAVE includes checks for WCAG 2.2, but WebAIM says WAVE cannot check all of the issues in these guidelines, and that no automated tool can (WebAIM). The same is true of every API here: automated testing catches about 57% of issues by volume (Deque, 2021). You'll still need manual testing for keyboard navigation, reading order, and cognitive accessibility requirements.
How much does accessibility API scanning cost per month?
Costs range from $0 (Pa11y, self-hosted, plus your own hosting) to enterprise contracts sold through sales (Deque and Siteimprove). For about 1,000 basic scans a month, WAVE API costs $30 in credits, and Pope Tech's cheapest plan with API access is $225 a month billed annually. BrowserStack doesn't publish its paid accessibility prices. Our own a11yFlow Starter plan is £19 a month for 1,000 scans. Prices checked October 2026 on each vendor's pricing page (WAVE API, Pope Tech, BrowserStack, a11yFlow).
Do accessibility APIs replace manual testing?
No. Automated scanning catches the top WCAG failures, low contrast text (83.9% of home pages), missing alt text (53.1%), and missing form labels (51%), but can't evaluate subjective criteria like whether alt text is actually meaningful, whether content order makes sense to screen reader users, or whether focus management in SPAs works correctly (WebAIM, 2026). APIs automate the automatable 57%. Human testers handle the rest.
The Bottom Line
Category | Winner |
|---|---|
WCAG 2.2 coverage | No clear winner (the new criteria barely automate) |
Accuracy (zero false positives) | Deque axe DevTools |
CI/CD integration | Pa11y |
Budget scanning | WAVE API |
Open source / self-hosted | Pa11y |
Enterprise platform | Siteimprove |
Dashboard + monitoring | Pope Tech |
Managed API, no infra to host | a11yFlow (our product) |
Best value overall | Pa11y + WAVE API combo |
There's no single best accessibility scanning API. Pa11y gives you free, pipeline-native scanning with a choice of engines. WAVE gives you transparent per-scan prices and an engine that includes WCAG 2.2 checks. Deque gives you enterprise-grade accuracy with zero false positives.
The accessibility testing market is projected to reach $907.6 million by 2034 (Straits Research, 2025). These APIs will get better. But the 95.9% failure rate won't drop until more teams put scanning in their CI/CD pipeline, not after launch, not after a lawsuit, but before every merge.
Start with one API. Run it on every pull request. Fix what it finds. That's the entire strategy.
For detailed tool-by-tool comparisons, see our accessibility testing tools guide. For a deep dive into the engines behind these APIs, read axe vs Lighthouse vs WAVE vs Pa11y. And if you want to skip the setup entirely, a11yFlow's API handles scanning, scoring, and WCAG remediation guidance in a single call.