Someone has asked whether your site is accessible - a client, a procurement form, a regulator, or a user who could not complete a task. A full WCAG 2.2 AA audit gives you a dated, defensible answer instead of a guess.
Not sure which? Book the scoping call and we will tell you - including if the answer is the cheaper one.
Why people commission one
Nobody buys an accessibility audit for fun.
There is almost always a trigger. Whichever one brought you here changes what the report needs to prove - so we ask before we start.
A legal or contractual obligation
The Equality Act 2010 requires reasonable adjustments for disabled users. Public sector bodies carry specific duties under the 2018 regulations. Increasingly, private-sector procurement asks for a conformance position before it will sign.
A tender or supplier questionnaire
A buyer has asked you to state your WCAG conformance level and you cannot answer honestly without testing. A dated audit and a published statement turn a blocking question into a box you can tick.
A user who could not complete a task
A complaint, a support ticket, or a drop-off you cannot explain. Roughly one in five UK adults is disabled - if your checkout fails a screen reader, you are not losing an edge case, you are losing a segment.
What you get
A report your developers can act on and your lawyers can rely on.
Every finding carries the WCAG success criterion it fails, the severity, who it affects, where it occurs, and what to do about it. No screenshot dumps, no unranked lists of 400 automated warnings.
Conformance statement
Your position against every WCAG 2.2 AA criterion: pass, fail, or not applicable - with the evidence for each.
Prioritised issue register
Every failure, scored by severity and user impact, with the affected templates listed.
Developer remediation notes
Per issue: the failing pattern, the corrected pattern, and the code-level change required.
Assistive technology findings
What actually happened under keyboard, NVDA, VoiceOver, 200% zoom and 400% reflow - recorded, not assumed.
Drafted accessibility statement
Written to the standard UK model, ready to publish, with known issues and target fix dates.
Debrief and Q&A
A 60-minute call to walk your team through the findings and agree what gets fixed first.
How it works
Scoped in a call. Delivered in ten working days.
1
Scoping call
We agree the trigger, the templates in scope, and the journeys that matter. You get a fixed price before anything starts.
2
Automated sweep
A full-site machine scan to catch repeated, machine-detectable failures fast - and to tell us where to look harder.
3
Manual testing
The real work. Every distinct template driven by keyboard and screen reader, at zoom and reflow, against all 2.2 AA criteria.
4
Report and debrief
The full report, the drafted statement, and a 60-minute call with whoever will be doing the fixing.
Pricing
Fixed price, agreed before we start.
Scope is driven by the number of distinct templates, not the number of pages - fifty blog posts built from one template count once.
Audit
£1,500+ VAT
Up to 15 distinct templates
Full WCAG 2.2 AA conformance assessment
Manual keyboard and screen reader testing on every template
Prioritised issue register with severity and user impact
Prices are for a single site or application. Multi-site estates, native mobile apps, and documents (PDF, Word) are quoted separately. Every price is confirmed in writing after the scoping call, before any invoice.
After the audit
Accessibility decays. Keep an eye on it.
Every content update, plugin change and new template is a chance to reintroduce something you have already paid to fix. Accessibility Watch is available to anyone we have audited.
Accessibility Watch - £95 + VAT / month
A monthly automated scan across your site, a quarterly manual spot-check of your highest-value journey, and a re-issued accessibility statement whenever your position changes. You get told when something regresses, not when a user complains. 30-day rolling, cancel any time, available after any audit with us.
Remediation, if you want us to do it
We can fix what we find. Scale varies far too much to publish a price honestly, so it is quoted once the audit tells us the real size of the job. On WordPress sites we host, fixes usually fold into a VIP Day or your existing care plan.
Questions
What people ask about the accessibility audit.
How is this different from the £749 UX & Accessibility Audit?
The £749 audit is a conversion-first review that includes an accessibility assessment across up to 10 pages. This is the reverse: accessibility is the whole job, done to evidential standard across every distinct template on your site, with per-issue WCAG success criteria, severity, affected user groups, and developer-ready remediation notes. If someone has asked you to prove your compliance position, you need this one. If you want to know why visitors are not converting, the £749 audit is the better buy.
Do you test with real assistive technology, or just automated tools?
Both, and the manual testing is the bulk of it. Automated scanning catches somewhere around a third of WCAG failures - it is a starting point, not an audit. Every template is driven by keyboard only, then through screen readers (NVDA and VoiceOver as standard; JAWS on request, charged at cost and quoted in the scoping call), at 200% zoom and 400% reflow, and checked for contrast, focus visibility, motion and target size. Automated results are used to sweep for repeated machine-detectable issues, then discarded from the headline findings.
Which version of WCAG do you audit against?
WCAG 2.2 Level AA by default, which is a superset of 2.1 AA - so you get a 2.1 AA position as part of it. If your obligation is written against 2.1 AA specifically, we report against that and flag the 2.2 additions separately so you can see them coming.
Will this make us legally compliant?
An audit tells you where you stand and what to fix - it is evidence, not a certificate, and nobody can honestly sell you one. In the UK, the Equality Act 2010 requires reasonable adjustments for disabled users, and public sector bodies have specific obligations under the 2018 accessibility regulations. What we give you is a defensible, dated record of what was tested, what failed, and what the remediation plan is. That record is what a regulator, a procurement team or a complainant actually asks to see.
What exactly is the retest report, and does it prove we are compliant?
It is a dated factual record: what was retested, on what date, against which WCAG 2.2 AA criteria, and which of the original failures now pass. It is signed by the person who did the testing. That is a document you can attach to a tender response or hand to a complainant to show what you did and when. What it is not - and what nobody can legitimately sell you - is a certificate of legal compliance. No private firm can certify you against the Equality Act, and any supplier offering to is overselling. Buyers and regulators ask for evidence of testing and a remediation record, and that is precisely what this is.
Can you fix the issues as well as find them?
Yes, and it is quoted separately once we know the scale - remediation on a 12-page brochure site and a 300-page platform are not the same job. For WordPress sites we build ourselves, fixes are usually folded into a VIP Day or your care plan. We will never bundle an unpriced fix promise into the audit fee to make the number look better.
What do you need from us to start?
A URL, a list of the journeys that matter most to your business, and login credentials for anything behind a form or paywall you want covered. If you have had a previous audit, a complaint, or a procurement question that triggered this, send that too - it tells us what the report has to answer.
Get a straight answer about where you stand.
A 15-minute scoping call. We will tell you how many templates you actually have, what the audit would cost, and whether you need one at all.