Accessibility Remediation

An audit tells you where the barriers are. Remediation is the work of removing them — fixing the code, the content and the documents so people using assistive technology can actually get in and get things done.

We remediate from audit reports — ours or another firm's — working issue by issue with WCAG 2.2 AA as the aim, and we re-test the fixes against the same standard when the work is done.

What remediation covers

• Websites and web apps — heading structure, form labels, keyboard navigation and focus order, color contrast, alt text, link purpose, and the other issues an audit typically surfaces.
• Documents — PDFs and office documents made readable in the right order: tags, reading order, headings, table structure and alt text, so screen readers can make sense of them.
• Templates and components — fixing the shared pieces (headers, forms, menus) so one fix repairs every page that uses them.
• Re-testing — after fixes land, the changed areas are reviewed again against WCAG 2.2 AA and the results documented, so you have a record of what was fixed and what remains.

Where to start

Remediation goes fastest with a current audit in hand. If you do not have one, start with our Website Audit — the free mini audit or the full audit — and we will scope the fix work from the findings. If you already have a report, send it over and we will work from it. For the bigger picture, see our Accessibility & UX services.

Frequently asked questions

Do I need an audit before remediation?

It helps — an audit scopes the work and keeps everyone honest about what was fixed. We can start from your existing audit report, a VPAT/ACR gap list, or an audit we run for you.

Do you remediate PDFs and documents, or only websites?

Both. Document remediation covers PDFs and office files — tagging, reading order, headings and alt text — alongside website and web app fixes.

Will my site be guaranteed compliant after remediation?

No — and be wary of anyone who guarantees that. Remediation fixes the issues that were found, and re-testing documents the result. New content and code changes can introduce new issues, which is why accessibility is an ongoing practice, not a one-time certificate.