This is a comprehensive report, not a fix: a full audit of your site against WCAG 2.2 AA, the standard most accessibility legislation and lawsuits actually reference, identifying exactly where you fall short, how severe each issue is, and what it would take to address it, so you can prioritise with real information rather than a vague sense of risk.
Accessibility audit report - WCAG 2.2 AA
A full WCAG 2.2 AA audit — a report, not a fix, and an overlay doesn't count toward passing it.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to crawl and test the site comprehensively
- Confirmation of any specific pages or user flows you’re most concerned about, if any
- Your preferred report format, if you have one
This or something else?
| You want a full WCAG 2.2 AA audit identifying every accessibility issue and its severity | This fix covers it |
| You already know your specific issues and want them fixed directly | The relevant targeted fixes instead, likely faster if you’re confident in the diagnosis |
| You want a lighter, automated scan rather than a full manual and automated audit | WAVE accessibility scan & findings report, or axe DevTools audit & remediation list, in the External Validation & Compliance Testing category |
| An overlay tool is currently installed and you want it assessed as part of this audit | We’ll flag it directly — an overlay doesn’t count toward genuine WCAG compliance regardless of what it claims |
What we do
- Test the site against WCAG 2.2 AA success criteria using both automated tools and manual review
- Identify every issue found, with its specific success criterion and severity
- Prioritise findings by genuine impact on real users and legal exposure
- Flag any existing overlay tool and note that it doesn’t substitute for genuine compliance
- Compile findings into a clear, organised written report
- Provide a quote for remediation if you want the issues fixed
What is included
- A comprehensive WCAG 2.2 AA audit combining automated and manual testing
- Prioritised findings with severity and specific success criteria cited
- Flags for any overlay tool that doesn’t represent genuine compliance
- A quote for remediation, if you want one
Not included
- Fixing the issues found — quoted separately based on findings
- Legal advice on your specific compliance obligations or risk exposure
- Ongoing monitoring after the report is delivered
- Certifying legal compliance, since no report can guarantee protection from a claim
Questions about this fix
Does installing an accessibility overlay make this report unnecessary?
No — an overlay doesn't achieve genuine WCAG compliance regardless of its marketing claims, and several jurisdictions' courts and disability advocacy groups have specifically criticised overlays as an inadequate response; we'd audit the underlying site regardless of whether one is installed.
What's the difference between this and an automated scan?
An automated scan catches a meaningful subset of issues quickly and affordably; this audit combines automated tools with manual testing (keyboard navigation, screen reader use) to catch issues automated tools structurally can't detect, like whether focus order is actually logical.
Will this report guarantee I won't face a legal complaint?
No report can guarantee that — what it does is give you an honest, thorough picture of where you stand against the standard most complaints and lawsuits reference, which is a meaningfully better position than not knowing.
How is severity actually determined?
We weigh how significantly an issue blocks real users (a screen reader user unable to complete checkout is more severe than a minor colour contrast issue on a rarely visited page) alongside how directly it maps to a specific, citable WCAG criterion.
Do I need to fix everything found, or can I prioritise?
Prioritising is exactly the point of ranking findings by severity — a phased approach addressing the most significant issues first is a reasonable, common way to proceed rather than requiring everything fixed at once.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.