Accessibility audit · WCAG 2.2 AA · Fixed price

An accessibility audit done by hand, not by a scanner.

Automated tools catch roughly a third of WCAG failures. The rest — keyboard traps, focus order, screen-reader output, broken ARIA — only show up when a person drives the interface the way your users with disabilities actually do. That's the audit we run, and at the end of it you hold a VPAT your buyer's procurement team can accept.

Fixed price $3,000 – $5,000, scoped on one short call.
Done in 2–3 weeks, including the retest.
Senior engineers in Poland, with a guaranteed daily overlap with Pacific time.
3,117

Federal website-accessibility lawsuits filed in the U.S. in 2025 — up 27% year over year. E-commerce is roughly 70% of them.

Seyfarth Shaw, ADA Title III report
$25–75k

Typical cost of settling a single accessibility claim — before you pay anyone to actually fix the site.

Reported settlement ranges, 2025
Jun 2025

The European Accessibility Act now applies to non-EU sellers too — so even if the ADA never reaches you, Europe already has.

Directive (EU) 2019/882, in force

The process

How a manual WCAG 2.2 AA audit runs

Fixed scope, fixed price, and a written deliverable at the end of every step. You always know what happens next and what it costs.

01 — Scope

One call, one number

We pick up to 15 representative screens or flows — the ones a plaintiff's expert or an enterprise buyer would look at first. You get a fixed price before we start, and we sign an NDA and MSA so legal is not the bottleneck.

02 — Test

Hands, keyboards, screen readers

Every screen is exercised with keyboard-only navigation and real assistive technology — NVDA, JAWS and VoiceOver — on top of automated passes. We test against WCAG 2.2 Level AA, the standard U.S. courts and the EAA both point to.

03 — Report

Findings your devs can ticket

Each finding is mapped to its WCAG success criterion, rated by severity, and written with reproduction steps and a concrete fix — so it can go straight into your tracker without a translation layer.

04 — VPAT & retest

Proof you can hand over

We complete a VPAT (Voluntary Product Accessibility Template) written to survive procurement review, then retest after your fixes and sign off a statement of conformance.

What you receive

The deliverables, in order

Written so a founder can read page one and an engineer can work from page four.

  1. Executive summary — one page, written for the person who signs
  2. Scope and method, including what we deliberately didn't test
  3. Findings by severity, each mapped to its WCAG 2.2 criterion
  4. Reproduction steps, evidence and a concrete fix per finding
  5. A completed VPAT / Accessibility Conformance Report
  6. A remediation plan your team can execute, with or without us
  7. Retest after fixes, with a signed-off conformance statement

Who does the work

Senior engineers, not a scanning subscription

The person on your first call is the person reviewing your report. No junior hand-offs, no platform to keep paying for.

Deep senior bench

We recruit from one of the deepest pools of senior QA and SDET talent outside the U.S. Everyone on your account is senior enough to argue with your engineers about whether a finding is really a failure.

English-first, async by default

No lock-in

Everything we produce — findings, fixes, the VPAT itself — is yours. There's no platform of ours to keep paying for and nothing to migrate off if you stop working with us.

Your repo, your documents

Time zone as a feature

Warsaw is nine hours ahead of Pacific time. Findings land in your tracker overnight, with a guaranteed 08:00–12:00 PT overlap window for anything that needs a conversation.

Results before your first meeting

Before you ask

Common questions about the audit

Why not just run an automated scanner?

Automated tools reliably detect only a minority of WCAG failures — the ones expressible as markup rules. They can't tell you whether your focus order makes sense, whether a modal traps the keyboard, or what a screen reader actually announces on your checkout. Those are exactly the issues that show up in demand letters, and they only surface in manual testing with assistive technology. We run automated passes too — as a baseline, not as the audit.

What is a VPAT and when do I need one?

A VPAT (Voluntary Product Accessibility Template) is the standard document enterprise buyers, government agencies and procurement teams ask for to evaluate your product's accessibility. The completed document is called an ACR. If an RFP or security review has ever asked about your accessibility posture, a properly written VPAT is what answers it. We complete it as part of the audit.

Does the European Accessibility Act apply to us?

If you sell products or services into the EU, very likely yes — the EAA has applied since June 2025 and covers many non-EU companies selling to EU customers. It points to the same WCAG 2.x Level AA baseline as U.S. case law, so one audit covers both directions.

Can you fix the issues for us?

The remediation plan is written so your own developers can execute it directly — most teams do. If you'd rather have us verify or implement fixes alongside your team, that's a separate scope we can quote after the audit.

How do contracts and payment work?

We're an EU company and invoice in USD — payment by wire or Wise, typically settled in one to three business days. Contracts are an MSA plus a per-project SOW, with a mutual NDA and a GDPR data processing addendum, and we'll sign under Delaware law if your legal team prefers it. You'll get a completed W-8BEN-E for your records.

Next step

Fifteen minutes, and you'll know where you stand

Tell us what's coming — a demand letter, an RFP asking for a VPAT, an enterprise deal — and we'll tell you what we'd test first and what it would cost. If a scanner is all you need, we'll say so on the call.

Book a 15-min gap call

Replies within one business day, always from an engineer.
Free with the call: a five-issue accessibility scan of your homepage.