Website accessibility remediation
Fixing the barriers that stop people with disabilities from using your site, in the templates where they start, with a written record of what was tested and what changed.
Most accessibility problems on a business website come from a handful of templates: the header and menu, the product or service page, the forms, the checkout. Fix those and every page built from them is fixed at once. I test the way people with disabilities actually use the web, with a keyboard, a screen reader, zoom, and a text-only browser, and I hand your developers fixes they can ship, or make them myself.
What I test
- Keyboard use from the home page to the main conversion: every menu, filter, button, and form field reachable and usable without a mouse, with visible focus.
- Screen reader output for headings, landmarks, links, images, form labels, error messages, and dynamic content.
- Color contrast for text, buttons, and form states against WCAG 2.2 Level AA.
- Zoom and reflow at 200 and 400 percent, where layouts break and content disappears.
- Media: captions on video, transcripts for audio, and controls for anything that moves.
- Pop-ups, cookie banners, and chat widgets, which trap keyboard users more often than anything else on a modern site.
Automated scanners catch only part of the real problems and flag some false ones. I use them to cover ground quickly and then check every template by hand.
What I fix
Every finding is tied to the template or component that causes it, with the WCAG success criterion it fails and the change that fixes it. On WordPress, static sites, and many Shopify themes I make the changes directly. On custom applications I write developer tickets with acceptance criteria and review the pull requests. Then I retest on the live site and record the result.
Overlay widgets stay off the site. They leave the underlying code as it was, and that code is what a court or regulator examines.
Documentation
You get a findings report, a record of every fix with the date it went live, and a draft accessibility statement that names the standard you work to, any known gaps, and how visitors can report a barrier. That record is what a lawyer will ask for if a demand letter arrives, and the statement is what EU rules expect a service provider to publish.
Who needs this
US businesses facing ADA demand letters or wanting to avoid them, which is covered in my guide to ADA website compliance. Companies selling to consumers in the European Union, which has enforced the European Accessibility Act since June 28, 2025, covered in my European Accessibility Act guide. And any organization that wants more of its visitors to complete what they came to do.
The search dividend
Accessible pages are easier for crawlers and AI systems to read. Real headings, labeled links, text alternatives for images, and content that doesn't depend on a mouse all help search engines understand a page the same way they help a screen reader. The work pays for itself twice.
Common questions
How long does remediation take?
The testing is quoted from the number of templates and the main user journeys. Fixes depend on who implements them; template changes I make myself usually ship within the engagement.
Can you certify the site as compliant?
I document what was tested, against which standard, and what was fixed. Compliance is decided by courts and regulators; the documentation is your evidence of good-faith work.
How is it billed?
An audit first, quoted as a fixed fee. The fixes come second: once the findings are known, they are scoped and quoted as a fixed fee before the work begins.
Updated