What this service is
We review your website against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard most UK organisations work to and the one referred to in public sector accessibility regulations. Automated tools catch only part of the picture, so most of our testing is manual. We navigate with a keyboard alone, listen with screen readers, zoom pages to 400 per cent, check colour contrast, use voice control and examine forms, error messages and dynamic content.
You receive a report that groups issues by the journeys they affect, such as making an enquiry, donating or booking. Each issue explains who it affects, why it matters, which WCAG success criterion applies and exactly how to fix it, with code examples where useful.
When you might need it
- You want to understand your position before publishing or updating an accessibility statement.
- A visitor has told you they couldn't use part of your website.
- A funder, client or tender asks how your website meets accessibility standards.
- You're about to redesign and want to avoid repeating existing problems.
- You'd like to check your site against the newer WCAG 2.2 criteria, such as focus visibility, target size and accessible authentication.
How the work runs
First we agree a sample. For most sites that means representative templates plus the key journeys from start to finish, rather than every page. We then test that sample across desktop and mobile using a range of assistive technology and browser combinations. Findings are written up in a prioritised report, and we hold a walkthrough call with your team or developers to talk through the issues and answer questions.
Once fixes are made, whether by your developers or by us, we retest the affected items and update the report. If you need one, we can help draft an accessibility statement that honestly describes the current state of the site and what you're doing about any remaining gaps.
Accessibility isn't a badge you earn once. It's a habit, and an audit is the best way to start it.
What's included
- Agreed scope covering templates and key user journeys
- Manual testing with keyboard, screen readers, zoom and voice control
- Automated scanning to support, not replace, manual checks
- Prioritised report mapped to WCAG 2.2 success criteria
- Walkthrough session with your team or developers
- Retest of fixed issues
- Help drafting or updating your accessibility statement
Questions we're often asked
Will the audit make our website legally compliant?
An audit tells you where you stand and what to fix. It's an important step, but we don't provide legal advice. If you have specific obligations, for example as a public body, check them with your advisers.
Can you fix the issues as well?
Yes. We can make the fixes ourselves, work alongside your existing developer, or simply hand over the report and let your team carry on.
Do you test PDFs and documents?
We can include a sample of key documents in the scope. We often recommend turning important PDFs into accessible web pages instead.
How is this different from an online accessibility checker?
Automated checkers find a useful subset of issues, but they can't tell whether a screen reader user can complete a form or whether keyboard focus gets lost. Manual testing covers those.