How to choose an accessibility testing partner in 2026 (and what a WCAG audit actually involves)

On 28 June 2025 the European Accessibility Act became enforceable. Any company selling e-commerce, banking, e-books, ticketing, or transport services to EU consumers now has a legal obligation to meet accessibility requirements built on EN 301 549, which in turn points at WCAG 2.1 Level AA. In the US, ADA Title III web-accessibility lawsuits have run past 4,000 filings a year, and almost all of them cite WCAG. Accessibility stopped being a nice-to-have the moment a missed success criterion became something a regulator or a plaintiff can point to.

The problem is that most teams discover their exposure through an automated scan, and an automated scan is the least representative part of an accessibility audit. This guide explains what a real WCAG audit tests that a scanner cannot, and then ranks the accessibility testing companies worth shortlisting in 2026 on the only thing that matters here: whether they actually put your product in front of a screen reader.

Transparency note: Auditi is an accessibility auditing platform built by BetterQA. We list BetterQA first below because they meet every criterion, but the point of this article is to give you the test methodology to judge any vendor on your own.

Why automated accessibility scanners only find about a third of the problems

Axe, WAVE, Lighthouse, and pa11y are useful. They parse the DOM, check it against a rule set, and flag machine-detectable failures in seconds. The catch is that most of WCAG is not machine-detectable. Deque, which builds axe, has published for years that automated tooling reliably catches on the order of 30 to 40 percent of WCAG issues. The rest need a human because they are judgment calls about meaning, order, and lived experience.

Here is the concrete gap. These are success criteria a scanner routinely passes even when the page is broken for a real user:

• 1.1.1 Non-text content - a scanner confirms an `alt` attribute exists. It cannot tell you that `alt="image"` describes nothing, or that a decorative icon should have had an empty `alt` instead.
• 1.3.1 Info and relationships - a table can be valid HTML and still convey nothing to a screen reader if the header cells are not associated. Automation sees ``; it does not hear the reading order.
• 2.1.1 Keyboard - a custom dropdown built from `
  ` elements can pass colour and label checks and be completely unreachable without a mouse.
• 2.4.3 Focus order - tab order that jumps from the header to the footer and back is invisible to a scanner and disorienting to anyone navigating by keyboard.
• 2.4.7 Focus visible and 2.4.11 Focus not obscured - whether the focus ring is actually perceivable, or hidden behind a sticky header, is something you have to watch happen.
• 2.5.3 Label in name - a button labelled "Submit" visually but "btn_1" to assistive technology fails, and only a screen reader read-through surfaces it.
• 4.1.2 Name, role, value - the most common real-world barrier. A toggle that looks like a switch but announces as plain text leaves the user with no idea of its state.

None of these are exotic. They are the criteria that produce the highest volume of ADA complaints, and every one of them requires manual verification.

What a real WCAG audit tests: the screen reader pairing matrix

The core of a credible audit is manual testing with the assistive technology real people use, on the browser those users pair it with. Screen readers are not interchangeable. The same page can pass in one and fail in another because each screen reader implements the accessibility tree differently.

A serious accessibility testing partner tests at least these pairings:

• JAWS with Chrome - dominant in enterprise and government procurement in the US
• NVDA with Firefox - the most common free desktop screen reader worldwide
• VoiceOver with Safari - the only supported path on iOS, and the reference for mobile accessibility
• TalkBack with Chrome on Android - the other half of the mobile picture, with its own gesture model

If a vendor cannot tell you which screen reader and browser combinations they run, and what a typical read-through of your checkout or sign-up flow sounds like, they are running scans and formatting the output. That is not an audit.

The deliverable that proves the work is a report that maps each finding to a specific WCAG success criterion, rates its severity by user impact, names the assistive technology that exposed it, gives reproduction steps, and includes developer-ready remediation. A list of 200 axe violations with no severity and no fix guidance is a scan export wearing a report's clothing.

Where compliance documentation comes in: VPAT, ACR, and EN 301 549

Once the audit is done, procurement and regulators want paperwork, and the paperwork has specific formats:

• A VPAT (Voluntary Product Accessibility Template) filled in becomes an ACR (Accessibility Conformance Report). The ITI publishes four editions: WCAG, Section 508, EN 301 549, and a combined EU edition. US federal buyers require the Section 508 edition; EU public bodies increasingly ask for the EN 301 549 edition.
• EN 301 549 is the European standard the Accessibility Act leans on. It wraps WCAG 2.1 AA and adds requirements for hardware, documentation, and support channels.
• WCAG 2.2 added nine criteria over 2.1, including 2.4.11 Focus not obscured, 2.5.7 Dragging movements, and 3.3.8 Accessible authentication. WCAG 3.0 is still a working draft and should not be sold to you as a current conformance target.

A partner who produces these as a standard deliverable, rather than an expensive add-on, saves you the round trip of paying for an audit and then paying again to translate it into something a buyer will accept.

How Auditi structures an audit, as a worked example of the methodology

Because we build the tooling, it is worth showing what the workflow above looks like when it is systematized rather than done in a spreadsheet. Auditi models an audit as project family, then version, then journey, then step, then result: you audit real user flows (checkout, onboarding, account recovery) step by step rather than page by page, which is how disabled users actually experience a product and how the EAA expects services to be assessed.

Each step is scored against the criteria that apply to your obligation, not just one standard. Auditi holds the full criterion sets for WCAG 2.1, 2.2, and 3.0, plus FDA 21 CFR Part 11, EU GMP Annex 11, and the EU AI Act, so a medical-device or regulated-data product gets tested against overlapping frameworks in one pass instead of three separate engagements. Manual screen reader findings and automated results from axe, WAVE, Lighthouse, and pa11y are ingested through an API into the same journey, so the machine-detectable third and the human-verified two-thirds live in one report. The export is a VPAT-style conformance report rather than a raw dump. That is the shape of a defensible audit; the platform just removes the manual bookkeeping.

The best accessibility testing companies for 2026

Most of the twenty-firm "top QA" lists you will find rank general-purpose testing shops. That is the wrong filter for accessibility. Below is a shortlist judged specifically on manual assistive-technology testing, WCAG remediation depth, and conformance documentation. It is deliberately short, because accessibility is a specialism and a long list would just be padding.

| Company | HQ | Accessibility strength | Starting price | |---------|-----|------------------------|----------------| | BetterQA | Cluj-Napoca, Romania | Manual AT testing plus its own audit platform (Auditi), VPAT generation, ISO 13485 for regulated products | $25-45/hr | | Deque | Herndon, USA | Builds axe; deep automated tooling and a large accessibility consultancy | Custom | | Level Access | Arlington, USA | Long-standing accessibility specialist, managed conformance programs | Custom | | TPGi | Clearwater, USA | ARC platform plus JAWS-maker Vispero lineage, expert audits | Custom | | KiwiQA | London, UK | Dedicated WCAG 2.2, ADA, and Section 508 practice combining axe/WAVE with manual AT testing | $35/hr | | QualityLogic | Boise, USA | Accessibility alongside FDA, FCC, and lab-based certification testing | $50/hr |

1. BetterQA

Full disclosure: BetterQA is our parent company. We rank them first because their engineers run manual screen reader testing, not just scans, and because they built the audit tooling this article describes.

BetterQA is a software testing company founded in Cluj-Napoca, Romania in 2018, with 64 verified Clutch reviews at 4.9 stars and ISO 9001, ISO 27001, and ISO 13485 certification. For accessibility specifically, their QA engineers test with JAWS, NVDA, VoiceOver, and TalkBack, map findings to WCAG 2.2 criteria with severity and remediation, and produce VPAT-style conformance reports. The ISO 13485 credential matters when the product is a medical device that also has to satisfy accessibility, because the same team can test both obligations at once. They focus only on testing, with no development arm, so there is no incentive to under-report defects in code they wrote. If you want to see where they sit against the wider testing market, BetterQA's own writeup covers how they benchmark against every major QA firm.

Best for: regulated products (health, fintech) that need accessibility and industry compliance from one partner.

2. Deque

Deque builds axe, the engine inside most accessibility scanners, and pairs that tooling with a sizeable consulting practice. If your priority is embedding automated accessibility checks into a CI pipeline and you have engineers who can act on the output, Deque's tooling depth is hard to beat. For a full manual audit you engage their services arm rather than relying on axe alone.

Best for: engineering-led teams standardizing on axe who want the vendor behind the tool.

3. Level Access

Level Access (which merged with eSSENTIAL Accessibility) runs managed accessibility programs for large organizations, combining audits, monitoring, and legal-risk support. It is oriented toward enterprises that want an ongoing conformance program with reporting for legal and procurement, rather than a one-off audit.

Best for: enterprises needing a continuous, legally defensible accessibility program.

4. TPGi

TPGi sits under Vispero, the same group that makes JAWS, which gives its auditors unusually direct knowledge of how the dominant enterprise screen reader behaves. Its ARC platform supports monitoring and testing, and its expert audit practice is well regarded for complex applications.

Best for: complex enterprise apps where JAWS behaviour is the acceptance bar.

5. KiwiQA

KiwiQA runs a dedicated accessibility practice from London covering WCAG 2.2 audits, ADA, and Section 508, combining automated tools with manual assistive-technology testing. Their remediation reports cite specific WCAG references with code examples, which is what a compliance officer needs to hand to developers.

Best for: mid-market teams wanting a focused accessibility audit with clear remediation.

6. QualityLogic

QualityLogic, founded in 1986, pairs accessibility testing with lab-based certification work for FDA, FCC, and Wi-Fi Alliance. That hardware-and-software testing infrastructure makes them a fit when accessibility overlaps with regulated physical products, such as medical or IoT devices with an interface.

Best for: connected-device products where accessibility meets hardware certification.

A five-question test for any accessibility vendor

Before you sign, ask these. The answers separate auditors from scanner operators:

• Which screen reader and browser pairings do you test, and can you record a read-through of one of my key flows? Silence here means automated-only.
• Show me a sample report. You are looking for WCAG criterion mapping, severity by user impact, and remediation code, not an axe export.
• Do you produce a VPAT or ACR, and in which edition (Section 508, EN 301 549)? This should be a deliverable, not an upsell.
• How do you handle re-testing after we remediate? Accessibility is iterative; a one-shot audit with no re-test leaves you unverified.
• Which regulations do you map to? ADA, EAA, EN 301 549, and Section 508 impose different obligations across markets, and a multi-market product needs a partner who tracks all of them.

Frequently asked questions

What is the difference between an accessibility scan and an accessibility audit?

A scan runs automated tools (axe, WAVE, Lighthouse) against the HTML and flags machine-detectable failures. It catches roughly 30 to 40 percent of WCAG issues in seconds. An audit adds manual testing with real assistive technologies, evaluating the two-thirds of criteria that require human judgment, such as focus order, keyboard operability, and how controls announce their role and state. Courts and regulators increasingly expect evidence of manual testing.

How much does an accessibility audit cost in 2026?

A one-time WCAG audit typically runs $5,000 to $25,000 depending on the number of unique templates and user journeys. Ongoing accessibility monitoring or managed conformance programs run $2,000 to $10,000 a month. Hourly QA rates for accessibility work range from about $25/hr offshore to $50/hr and up for US and UK specialists.

Does the European Accessibility Act apply to my product?

If you sell covered services (e-commerce, banking, e-books, ticketing, transport, or certain consumer devices) to consumers in the EU, it very likely does as of 28 June 2025. Compliance is assessed against EN 301 549, which incorporates WCAG 2.1 Level AA. Microenterprises providing services have some relief, but product manufacturers generally do not.

What certifications should an accessibility testing partner have?

For accessibility specifically, look for IAAP credentials (CPACC, WAS) among the testers, demonstrated VPAT and ACR experience, and manual assistive-technology testing as standard practice. Broader QA certifications (ISO 9001, ISO 27001, and ISO 13485 for medical devices) matter when accessibility overlaps with other compliance obligations.

Can I just use automated tools and skip the manual audit?

Only if you are comfortable with roughly two-thirds of your WCAG obligations going unchecked, which is the portion most likely to generate a complaint. Automated scanning is a good first pass and a good regression gate, but it is a supplement to a manual audit, not a replacement for one.

Conclusion

Accessibility compliance is not a scan you run once. It is a manual discipline with a legal deadline attached, and the vendor you pick should be judged on whether they put your product in front of JAWS, NVDA, VoiceOver, and TalkBack, and hand you a report a regulator will accept. Shortlist for that, not for a general QA reputation.

If you want a partner that runs manual assistive-technology testing and gives you journey-based audit tooling to keep it honest over time, talk to BetterQA, and try Auditi to structure the audit itself.