Accessibility audit
Website accessibility audit against WCAG 2.2 AA
We test your website or digital service against WCAG 2.2 AA by hand, with a keyboard, screen readers and automated checks, then give you a prioritised list of issues, the people each one affects and how to fix it. Audits are scoped and quoted for each site.
The problem
What this work is usually brought in to solve
- You need an accessibility statement but do not know which parts of the site fail WCAG 2.2 AA.
- A public-sector body or a buyer has asked for evidence that the service is accessible.
- An automated checker returned a score, but nobody can say what it means for real users.
- Forms, menus or booking steps cannot be completed with a keyboard or a screen reader.
- A redesign is planned and you want to know what to fix before building again.
- Complaints or feedback suggest some people cannot use the site, but the cause is unclear.
Outcomes
What changes for your organisation
- A clear picture
- Every issue we find is mapped to the WCAG 2.2 success criterion it fails and the pages where it occurs.
- Fixes in priority order
- Issues ranked by how badly they block people and how much effort they take to fix, so the team knows where to start.
- Evidence you can use
- A written report that supports your accessibility statement and answers questions from buyers or regulators.
- Confidence after fixes
- An optional retest confirms which issues are resolved before you update your statement.
Deliverables
What you receive
- Agreed scope
- A representative sample of pages, templates and key journeys, such as contact, booking, payment or application forms.
- Manual testing
- Keyboard-only operation, focus order, visible focus, zoom and reflow at 320 pixels, colour contrast and motion.
- Assistive technology checks
- Key journeys tested with screen readers such as NVDA and VoiceOver.
- Automated scan
- Automated checks across the sample to catch repeated code-level issues quickly.
- Written report
- Each issue with the success criterion, severity, affected users, location, screenshots and a recommended fix.
- Walkthrough call
- A call to go through the findings with your team and agree the order of work.
Our approach
How we deliver it
01Scope
Agree the pages, journeys, devices and browsers to test, and the standard: WCAG 2.2 AA unless you need otherwise.
02Test
Manual, assistive technology and automated testing against the agreed sample.
03Report
Findings grouped by severity, with plain-English explanations and code-level recommendations.
04Review
A walkthrough call with the people who will make the fixes.
05Fix
Your team fixes the issues, or we do the work as a separate piece of development.
06Retest
Optional retest of the reported issues so your accessibility statement reflects the current site.
Where it applies
Sector and use-case examples
- Councils and public bodies
- Evidence for the accessibility statement required under the Public Sector Bodies Accessibility Regulations 2018.
- Healthcare providers and clinics
- Making sure patients can find information and complete booking or contact forms with assistive technology.
- Suppliers to the public sector and NHS
- Accessibility evidence requested during procurement or assurance reviews.
- Businesses before a redesign
- Knowing which problems to design out before the new site is built.
Standards
Standards and considerations we work to
- Web Content Accessibility Guidelines (WCAG) 2.2, level AA.
- Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, for public-sector clients.
- Equality Act 2010 duty to make reasonable adjustments, as context for private-sector organisations.
- Where you need an independent third-party assessment, we arrange it through an appropriate specialist and quote it separately.
- An audit reports what we found in the tested sample. It is not a legal opinion or a certificate.
Suitability
Who this is for
- Organisations that need to publish or update an accessibility statement.
- Teams asked for accessibility evidence by a buyer, a framework or a regulator.
- Anyone planning a redesign who wants to fix the right problems first.
Questions
Frequently asked questions
How is an audit different from your website review?
Our website review includes an accessibility spot-check against common issues. An audit tests an agreed sample against every WCAG 2.2 AA success criterion and reports each failure in detail.
How much does an accessibility audit cost?
It depends on the number of page templates, the journeys to test and whether a retest is needed. We quote a fixed price once the scope is agreed.
Do you test every page?
No. We test a representative sample of templates and key journeys. Most issues repeat across pages built from the same template, so fixing them in the template fixes them everywhere.
Will we receive a certificate?
No. WCAG has no official certificate. You receive a written report of what we tested and found, which supports your accessibility statement.
Can you fix the issues as well?
Yes. We can fix the issues as a separate piece of work, or your developers can work from the report.
Is an automated scan enough?
No. Automated tools find only part of the problems. Keyboard, screen reader and manual checks are needed to judge whether people can actually complete tasks.
Related
Related services and insights
Website Review
A free snapshot or a paid review with an accessibility spot-check.
Website Redesign
Rebuild the site with accessibility designed in from the start.
Public Sector Digital Solutions
Accessible digital services for councils and public bodies.
Healthcare Digital Solutions
Websites and services for clinics, practices and health-tech teams.
Next step
Request a website review
A written assessment of your current site covering proposition clarity, usability, accessibility, search visibility and conversion, reviewed by a person rather than generated automatically.
Contact
Or send us a short note
Tell us what you are trying to achieve and we will reply with next steps.