Accessibility and WCAG. Meet the standard properly, and prove it.
Someone’s asked whether the site is accessible, and nobody can say for sure. We test it properly, fix what’s wrong in the code, and never use an overlay.
Accessibility is a customer problem before it’s a legal one.
Fix the site properly and you deal with both.
Why it matters
Accessibility gets treated as a compliance job. It’s really about whether people can read what you’ve published and use what you’ve built. Everyone has a right to do that. The law expects it, but it’s not why you do it.
-
One in four people in the UK has a disability.
16.8 million people, and one in six worldwide. -
Most of it you can’t see.
Sight, hearing, dexterity, reading and memory, and everyone whose eyes or hands aren’t what they were. -
Nearly every site fails.
96% of the top million home pages have WCAG failures, with 56 errors each on average. -
People don’t complain. They leave.
They go to a site that works, and they don’t tell you why.
When accessibility work helps most
-
You’ve had a complaint.
Or a letter. -
You sell into the EU.
The European Accessibility Act has applied since June 2025. -
You’re public sector, or supply it.
The regulations and procurement both ask. -
A scanner gave you a score.
And you don’t know what it means. -
You’re about to redesign.
It’s cheaper to build it in than bolt it on. -
Someone has suggested an overlay.
Don’t.
What we do
-
Audit against WCAG 2.2.
By hand as well as by tool, on the pages that matter. -
Keyboard and screen reader testing.
Real use, not a checklist. -
Prioritised fixes.
What blocks people, what hinders them, what’s cosmetic. -
Remediation.
We fix the code, the templates and the content.
-
Accessible builds.
New sites built to the standard from the first template. -
Content guidance.
Headings, links, alt text and PDFs your team can keep right. -
Accessibility statement.
Written accurately for your site, not copied from a template. -
Retesting.
After fixes, and on a schedule if you want one.
How it works
What you get
- A report that says what’s wrong, who it affects and what to do, in plain English.
- Fixes made, not just listed.
- An accessibility statement you can publish with a straight face.
- A team that knows how to keep it right.
- No overlay. Ever.
Common questions
In the UK, the Equality Act 2010 requires reasonable adjustments for disabled people, and that covers websites. Public sector bodies have their own regulations. If you sell to consumers in the EU, the European Accessibility Act applies. We’ll explain which of these apply to you.
The current version of the international standard for web accessibility. Level AA is what regulations and most contracts ask for.
Two to three weeks for most sites, depending on the number of templates.
It depends on the size of the site and the number of templates. We confirm the cost before any work starts.
Overlays don’t fix the underlying code, they’ve been the subject of legal action in the US and Europe, and disabled users largely dislike them. Fixing the site is cheaper in the long run.
Both. We’d rather fix.
Rarely, and never much. Most fixes are in code and content, not design.
Included if you want them. Often the biggest problem on public sector sites.
Yes. Most of the sites we audit were built by someone else.
Let’s find out where the site stands
Send us the site address. We’ll come back with scope, cost and timing for an audit, or for fixes if you already have one.
We’ll only use this to reply to you. See our Privacy Policy.