Known barriers fixed and a record of what remains
Sounds familiar? We're not sure people with disabilities can use our site, and we've heard about accessibility laws.
Someone using a keyboard or a screen reader (software that reads the page aloud) can hit barriers that a visual check never shows, such as a menu they can't reach or a form field with no label. An accessibility specialist uses a keyboard, a screen reader and automated tools to test your key pages and flows against WCAG (the Web Content Accessibility Guidelines) at level AA, the middle of its three levels. Issues are ranked by severity, fixed by a developer and retested, and you get a record of what was tested, what was fixed and what remains. We scope first because the testing grows with your page types and flows, the third-party tools involved and the WCAG version that fits where you operate. This is not legal advice or a certification of compliance.

What you get
- Written testing scope: pages, flows, devices and the WCAG version and level
- Manual keyboard and screen reader testing, plus automated checks
- Issue list ranked by severity, with the page, the barrier and who it affects
- Fixes made in your site's code, templates and content
- Retest of fixed issues and a summary of what was tested, fixed and still open
- Notes on barriers inside third-party tools, ready to raise with their vendors
- Accessible content guidance for your editors on headings, links, image descriptions and documents
Is this right for you?
- You sell to consumers online and want checkout, booking and contact flows that everyone can use
- You run an organization with public services and need to know where your site stands
- You received an accessibility complaint and want the barriers fixed alongside your lawyer's advice
- You were told an overlay widget would make your site accessible and want a second opinion
- You have a web app or customer portal and want its core tasks tested the same way
What it changes
Known barriers found and fixed
Issues in your site's code, templates and content are fixed and retested across the agreed pages and flows, starting with those that stop people finishing a task.
A record of where you stand
The written record lists what was tested and how, what was fixed and what remains open.
Editors who can keep it up
Your team knows how to add headings, links, image descriptions and documents without creating new barriers.
Scope and delivery
How we deliver it, what we need from you, what is not included. Timeline: Set after a short call, when we know which pages and flows to test
How we deliver it
-
Agree on the scope
A short call settles the pages, flows and devices to test, and the WCAG version and level to test against.
-
Test by hand and with tools
An accessibility specialist works through each flow with a keyboard and a screen reader and runs automated checks. Every issue is ranked by severity.
-
Fix the barriers
A developer fixes the issues in your site's code, templates and content, most severe first. Problems inside third-party tools are written up for their vendors.
-
Retest and hand over
Fixed issues are retested. You then get the written record and the guidance for your editors.
What we need from you
- A list of your key pages and tasks, such as booking, checkout or contact
- Admin or developer access to your site, and a staging copy (a private test version) if you have one
- Details of third-party tools on your site, such as booking, chat or payment widgets
- Any complaint or feedback you have received about accessibility
- The countries you operate in, so the scope names the right WCAG version
What's not included
A specialist looks at your situation first, so the scope is agreed after a short call.
Not included
- Legal advice or a compliance certificate
- Accessibility overlay widgets
- Fixes inside third-party tools you don't control
Limits to know
- This is not legal advice or a certification of compliance. For questions about which laws apply to you, speak to a lawyer.
- Testing covers the pages and flows agreed in the scope. New content and features can add new barriers.
- Manual testing uses the screen readers, browsers and devices named in the scope. Other combinations can behave differently.
- We don't install overlay widgets, because they don't make a site accessible on their own.
- Third-party tools such as booking or chat widgets may have barriers only their vendor can fix.
Where it fits
What usually follows, what may already be in place, and what is planned alongside, with the reason for each.
This service: Accessibility review & fixes
3 connected services
Keeps it running
Keeps it working after launch.
-
Website care plans
Keeps the site updated and monitored. Ask for accessibility rechecks in the plan's written scope.
Part of these packages
-
E-commerce launch
Optional add-on: For stores selling to EU consumers, where accessibility rules can apply. Your lawyer can confirm whether they cover your business.
-
Repair, improve & modernize
Optional add-on: When accessibility barriers need fixing.
Common questions
Will this make my site legally compliant?
That is a legal question, and this work is not legal advice or a certification. You get barriers found and fixed against WCAG level AA within the agreed scope, plus a written record of the testing. If a law or a complaint is involved, your lawyer can review that record as part of their advice. They can also tell you whether a rule applies to a business your size.
Can't we install an accessibility widget instead?
An overlay widget adds a toolbar on top of the site, and the barriers in the code and content stay where they are. We fix those directly and don't install overlays.
Can you quote this without a call?
Not reliably, because two sites that look alike can need very different amounts of testing. On a short call we count the page types and flows, list the third-party tools and pick the WCAG version that fits where you operate. The quote for testing and fixes follows from that.
How do we keep the site accessible after the fixes?
New pages, images and documents can add barriers, so your editors get guidance on accessible content. A Website care plan can include rechecks of key pages if you ask for them in its scope, and UI/UX design can build accessible patterns into new features from the start.