What does an accessibility audit cost?
The honest short answer: nobody can price your audit responsibly without looking at your site — and anyone who quotes a flat price sight-unseen is either guessing, or selling you a scan. Here is what actually drives the cost, and how to compare quotes fairly.
What drives the cost
- Size — and templates. Fifty pages built on three templates is a much smaller job than fifty individually designed pages. What matters is how many distinct designs and components exist, not the raw page count.
- The journeys that matter. Audits are priced on tasks — buying, booking, applying, submitting — worked end to end. More critical journeys, more work.
- Documents. PDFs, statements and forms are their own discipline. An audit that includes your key documents costs more than one that stops at web pages — and is usually worth it, because documents are where customers get stuck quietly.
- Web, app, or both. Each platform is separate testing, on separate tools.
- The standard — and the paperwork. Findings against WCAG are one thing; a formal Accessibility Conformance Report (VPAT®-based) for procurement is additional, exacting work.
- What happens after. A walkthrough call, advice while your team fixes things, and retesting the fixes are real work — included in some quotes, invisible in others.
The pricing models you will meet
- Defined-scope checks. A small, fixed scope — one journey, a set number of pages — priced as a package once scoped. This is how the AODA Check works, and it is the right shape for a first step.
- Project or day-based audits. Priced on estimated effort. Honest, when the scope is written down in the proposal; vague, when it isn’t.
- Per-page pricing. Easy to compare, easy to game. Barriers don’t live on pages — they live in journeys, components and flows, which is why serious testers rarely price this way.
What a suspiciously cheap audit skips
An automated scan, run once, with the tool’s raw output forwarded to you. Scans catch a minority of barriers — missing labels, some contrast failures — and none of the ones that actually stop a blind customer completing a task: the confusing order, the unlabelled control, the step that silently fails. If no screen reader is named in the quote, no screen reader is involved. Compare a real report: what a findings report looks like.
How this practice prices
Every engagement starts with a free conversation, and you receive a written proposal — the full scope and the full cost — before any work begins. No work starts without it, and no invoice surprises you after it. The defined-scope Check exists so the first step can be small and certain; a full audit is scoped to your site, your journeys and the standard you must meet. See the services.
Questions to ask any auditor
- Who does the testing — and are they a screen-reader user themselves?
- Which tasks will you work through, not just which pages?
- What exactly do I receive, and in what form?
- Is a walkthrough of the findings included?
- After we fix things, is retesting included — or a separate cost?