Audits and remediation
Most clients start with an audit and then have us fix what it finds. You can also take the audit to your own developer, or bring us in to fix and re-test issues someone else already found.
Accessibility remediation
Remediation means fixing the site you have. We change the templates, theme files, components and content that cause each barrier, then test again with a keyboard and screen readers to confirm it’s gone.
Typical fixes
- Menus, buttons and pop-ups that work with a keyboard and announce their state
- Form labels, error messages and instructions that screen readers read out
- Text alternatives for images, icons and logos
- Color and contrast changes that stay true to your brand
- Visible keyboard focus, logical heading structure, skip links
- Layouts that hold together when people zoom in
What we need from you
Access to the site’s code or CMS (or to a staging copy), and someone who can approve changes. If your site is built on a hosted platform, we’ll confirm what can be changed before work starts.
What you get
Fixed pages, a change log, and a dated re-test report for everything in scope, including anything we couldn’t fix and why.
Full accessibility audit
We agree on the pages and tasks that matter most: usually your home page, main service or product pages, and anything people fill in, such as booking, contact or checkout. Then we test them two ways.
- Automated checks on every page in scope, to catch common patterns quickly.
- Manual testing with a keyboard, with screen readers (NVDA on Windows, VoiceOver on Mac and iPhone), at high zoom and on a phone.
The report lists each confirmed issue with where it is, what we observed, who it affects, the WCAG 2.2 criterion and a recommended fix, ordered by how much it gets in people’s way. See a sample report.
Remediation plan for your developer
If you already have a developer or agency, we can turn the audit into a work plan they can follow: what to change, where, with before-and-after code and how to check the result. We’re available for their questions, and we re-test when they’re done.
Re-test
After fixes, ours or anyone else’s, we test the same pages and issues again and record the outcome with a date. A re-test is useful before a site relaunch, after a big content update, or when someone asks what you’ve done about accessibility.
Pricing
We quote each project after looking at your site, because two sites with the same number of pages can be very different amounts of work. The quote depends on:
- how many distinct page templates and components the site has
- the platform, and whether we can edit code directly
- forms, checkout, booking and other multi-step tasks
- third-party tools embedded in the site
- how many issues the audit finds and how complex they are
You’ll get a fixed scope and price in writing before any paid work begins.
How a project runs
- Conversation. You tell us about the site and what prompted the question. We look at it before we talk price.
- Scope and quote. We agree on pages, tasks, testing methods and what’s excluded.
- Audit. Automated and manual testing, then the report.
- Fixes. By us, or by your developer using our plan.
- Re-test and handoff. We confirm the fixes and give you the dated report. Future changes to the site are yours to manage, and we’ll tell you what to watch for.
Web Accessibility Fix provides technical accessibility testing and remediation. It isn’t legal advice, and no audit or fix guarantees a business won’t receive a complaint or lawsuit.