Services · Second opinions & benchmarks

A Pre-Launch Audit Buys the Cheapest Fixes You Will Ever Ship

For the team a few weeks out from launch that wants its barriers found on staging, where fixing one is a commit rather than a project. We work behind your login, your VPN, or your staging wall, and hand back a list split into what has to land before launch and what can safely wait.

What We Keep Finding

There is a moment in every build when accessibility fixes cost almost nothing, and it is the one you are in. No user has hit the barrier yet. No campaign is pointing traffic at it. The developer who wrote the template is still inside the code and remembers why. The same fix requested six months after launch competes with a roadmap, waits behind a release cycle, and gets rediscovered by whoever is left on the team.

The useful part is the split, and the standard draws that line better than instinct does. Conformance is defined for a page, and where several pages make up a process, every page in it has to conform before any single one of them counts. A checkout is W3C's own worked example. So anything that breaks one step of a revenue journey breaks the whole journey, including the four steps you got right, and that is your launch blocker. A contrast miss on the careers page is not. Same report, two very different Mondays.

One thing to know before you try the free scan on your staging site, because a lot of teams try it first. The scanner only accepts a public address on a standard web port, so a build on an odd port, an internal hostname, or anything running on localhost gets refused rather than scanned. That is not a limit we can engineer away either. A person can be handed a VPN profile and a password. A crawler pointed at the open internet cannot.

What We Check

Audit the staging build against all 55 WCAG 2.2 Level A and AA rules
Run the launch-critical journeys with a real blind screen-reader user
Work behind logins, VPNs, and staging walls, with the access you grant us
Flag template fixes first, where one change repairs every page that template prints
Split findings by whether they break a whole journey or sit inside one page
Rank what is left into before-launch blockers and after-launch cleanup

What You Get

Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.

The format is not a mystery either. Read the sample report before you spend anything.

The Honest Limit

Two honest limits, and the second one has a clock on it. First, we audit the build we are given, and builds move fast in the last few weeks, so anything landing after our pass arrives untested and the report says which pages that covers. Second, the half-price re-audit runs for 3 months from the date of your report, and a launch that slips can outrun that window. If your date is soft, say so when we confirm scope and we will time the pass to be useful rather than early. And because our testing is desktop-based, clearing a staging build does not clear its phone layout, which the standard treats as a page of its own.

What It Costs

Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.

Order your audit Read the sample report first

Worth Reading Next

Related on this site

Guides, checklists, tools, and terms that go with this service.