Website accessibility audit
Manual and automated WCAG 2.2 AA testing with NVDA, JAWS and VoiceOver. Every issue mapped to the fix.
Service · Remediation
Website accessibility remediation
We fix accessibility barriers at the source — in your templates, components, styles and content — and prove the fixes work with assistive technology.
Fixes that last
An overlay script tries to patch your website in the visitor’s browser after it loads. Real remediation changes the website itself, so it works with every screen reader, browser and device — and it doesn’t break the next time a plugin updates. The FTC’s $1 million order against an overlay vendor in 2025 shows why that distinction matters.
What we fix
- Structure and semantics: headings, landmarks, lists, tables, page titles, language.
- Keyboard access: reachable and operable controls, logical focus order, visible focus, no keyboard traps, skip links, focus not hidden by sticky elements.
- Forms: programmatic labels, instructions, error identification and suggestions, autocomplete, accessible authentication.
- Custom components: menus, modals, tabs, accordions, carousels, comboboxes and date pickers rebuilt to the WAI-ARIA Authoring Practices.
- Visual design: text and non-text contrast, reflow at 320px, text spacing, target size, color-only meaning.
- Media: captions, transcripts, audio description, pause controls for motion.
- Content: alt text, link text, readable error messages, accessible PDFs linked from pages.
How an engagement runs
- Triage. We rank issues by user impact and legal risk: anything that blocks a purchase, application or account task comes first.
- Component-first fixes. One fix to a shared header, form field or modal can close hundreds of page-level issues.
- Developer pairing. If your team prefers to do the work, we pair with them, review pull requests and answer questions in your Slack or Teams.
- Retest with assistive technology. Nothing is closed until a specialist verifies it with a screen reader and keyboard.
- Documentation. You receive a conformance report, an updated accessibility statement, and evidence of the work completed.
Platforms we work in WordPress, Drupal, Shopify, Adobe Commerce, Sitecore, AEM, Webflow, Squarespace, HubSpot, Salesforce Experience Cloud, and custom React, Next.js, Angular, Vue and server-rendered applications.
Typical results
Most sites have a few dozen distinct issues repeated thousands of times. In our experience, fixing the top ten components resolves most page-level failures, so a focused remediation sprint of four to eight weeks gets most organizations to substantial WCAG 2.2 AA conformance.
Frequently asked questions
Do you need access to our codebase?
For full remediation, yes — a branch in your repository or a staging environment. If that’s not possible we deliver fixes as tickets with ready-to-use code and test them on staging after your team merges them.
Will remediation change how our site looks?
Usually very little. Most fixes are invisible: semantic markup, labels, ARIA, focus management. Some visual changes are required, such as darker text to meet contrast ratios or visible focus indicators, and we work with your designers to keep them on-brand.
How do you prevent the problems coming back?
We fix shared components rather than individual pages, add automated accessibility checks to your build pipeline, give your content editors short training, and offer ongoing monitoring.
Find out where you stand, in writing.
Send us a few URLs or sample PDFs. Within two business days you get a free, plain-English snapshot of your biggest accessibility risks and what it takes to fix them.