An audit is a map, not a verdict.
We’re here to help you get to where you’re going without any surprises. Our auditors test your product by hand, with the assistive technology your users actually rely on, and chart the clearest path to conformance with the Web Content Accessibility Guidelines (WCAG), the standard most accessibility laws point to.
- Every page tested by hand
- All 55 WCAG 2.2 AA success criteria
- Fixed-fee, scoped in plain language
How we test
We meet your product the way your users do.
NVDA, VoiceOver, JAWS, and TalkBack are screen readers: software that reads the screen aloud, or sends it to a braille display, for people who are blind or have low vision. Every audit runs NVDA and VoiceOver by default, covering Windows, Mac, and iPhone between them. If your users rely on JAWS or on Android’s TalkBack, we add those on request. Keyboard-only testing comes standard on every engagement.
The heart of every audit is a person, sitting with your product, using it. Our auditors navigate your critical journeys with the same assistive technology your users bring: listening to how a form announces itself, feeling where keyboard focus lands, noticing the exact moment a journey quietly becomes impossible.
- NVDA
- VoiceOver
- JAWS
- TalkBack
- Keyboard-only testing
Where automation fits
Scanners catch about a third of the problems.
We run automated checks on every engagement, led by axe, the engine behind much of the industry’s tooling. It sweeps each page for the mechanical issues a machine can see: missing image descriptions, contrast slips, code that tells assistive technology one thing and does another. It’s fast, it’s tireless, and we’d be silly not to use it.
What a scanner can’t tell you is whether the focus order makes sense, whether the alt text says anything useful, or whether checking out with a screen reader takes four minutes or forty. That judgment is the audit. Automation clears the mechanical layer so our auditors spend their time on the two thirds only a person can find.
How an audit runs
-
Scope
Tell us about your product and the markets you sell into; if it’s live, include the URL. Within 2 business days you’ll have a fixed-fee proposal in plain language: the pages, the flows, the price.
-
Test
Our auditors work through everything in scope by hand, with automated sweeps clearing the mechanical layer as they go. Laws mostly still name WCAG 2.1 at Level AA; we test to 2.2 AA by default because it is more recent and considered to be the stronger of the two, backward compatible (2.2 AA covers 2.1 AA, with one criterion W3C removed as obsolete), and 2.2 is where most regulation is headed.
We test all 55 WCAG 2.2 AA checkpoints, called success criteria, against all “unique” pages from a selected sample, components, and steps using at least two screen readers. If your regulation calls for WCAG 2.1 AA and you have no interest in testing past that, that’s fine – we can stick with that. We will only give you our lecture on 2.1 vs 2.2 once.
-
Report
Findings land in the Labrador platform as they’re discovered, and your report is generated straight from that record: severity, evidence, and suggested fixes, nothing retyped.
-
Walk through
We sit down with your team and put the findings in order together, so you leave with a clear picture and a sensible plan.
-
Re-test
When your fixes have been made, we verify every finding again and update the report. Anything that doesn’t pass gets one more check after your next fix, at no charge. Re-testing stays open for 90 days from your report. That first full round is included in your audit; further full rounds are the flat $300 on our pricing page, whenever you need them. And if you’d like assistance, we can have our developers make the fixes.
What you get
Every audit closes with the same set of deliverables, built to be used rather than filed.
-
Findings you can hand to a developer
Every issue is written against its WCAG success criterion, with severity, evidence (screenshots and video where they help), and a suggested fix.
-
A report people actually read
An interactive HTML report, generated by the Labrador platform, which we built. Filter by page, severity, or criterion; every claim sits next to its evidence.
-
Exports that meet your team where it works
A Jira-ready CSV export, or a direct Jira integration, moves findings straight into your backlog, and a plain CSV opens anywhere a spreadsheet does. When procurement asks for formal proof, your audit becomes the basis for a VPAT (the industry’s Voluntary Product Accessibility Template) or an ACR, an Accessibility Conformance Report, which is simply a filled out VPAT.
-
A walkthrough, included
We present what we found, answer your questions, and help you decide what to fix first, so the report starts moving the day it lands.
The homepage audit
Start with one page for $495.
Not ready to scope a whole audit? We’ll take your homepage through the same hands-on testing described above, on the same assistive technology, and send you the snapshot: every finding with severity, evidence, and a suggested fix.
Nothing is wasted, either: if you go on to a complete audit, the full $495 is credited toward it. You never pay for the same page twice, and you’ll already know exactly how we work.
Start a conversation
Say hi (opens chat)
Tell us what you’re building, and we’ll tell you what an audit of it looks like. Our founding team spans Maine, Wales, and Delhi, so someone’s online through most of your working day. Expect a scoped, fixed-fee proposal within 2 business days. A call is welcome, never required.