Website accessibility remediation
We fix code, components and content in any CMS or framework, then retest until every issue is closed.
Service · Audit
Website accessibility audit
A complete WCAG 2.2 Level AA audit of your website or web app, tested by specialists using the same assistive technology your customers use.
What you get
- An issue log (spreadsheet or Jira/Azure DevOps import) with every barrier we find: the WCAG success criterion, severity, page and component, a screenshot, the code involved, and a specific recommended fix.
- An executive summary your leadership and legal counsel can read in ten minutes: overall risk, the user journeys that are blocked, and a prioritized plan.
- A remediation estimate for the work, whether you fix it yourselves or have us do it.
- A retest after you remediate, and a final conformance report.
How we test
Every audit combines four layers of testing. Tools find the obvious issues fast; people find the ones that block real users.
- Automated scanning with axe-core, WAVE and Lighthouse across the full sample, to catch machine-detectable failures such as missing labels and contrast errors.
- Keyboard testing of every interactive element: can you reach it, see where focus is, operate it, and leave it? Is focus hidden behind sticky headers (new in WCAG 2.2)?
- Screen reader testing with NVDA and JAWS on Windows and VoiceOver on macOS and iOS, completing your key tasks end to end the way a blind customer would.
- Visual and cognitive checks: 400% zoom and reflow at 320 pixels, text-spacing overrides, color-only information, motion, time limits, consistent help and error messages.
Why sampling works Most websites are built from a small set of templates and reusable components. Testing a well-chosen sample of 15–30 pages exposes nearly every distinct issue, and fixing the shared component fixes it everywhere.
What’s in scope
| Area | What we check |
|---|---|
| Templates | Home, landing, listing, detail, article, search results, error pages |
| Journeys | Sign-up, login, search, checkout or application, contact and booking forms |
| Components | Navigation, menus, modals, carousels, tabs, accordions, date pickers, chat widgets |
| Media | Captions, transcripts, audio description, auto-playing content |
| Documents | A sample of linked PDFs (full PDF remediation is a separate service) |
| Third-party | Embedded tools you rely on (payment, scheduling, maps) — flagged so you can push vendors |
Timeline
A typical engagement takes two to three weeks from kickoff to report: a short scoping call, about a week of testing, and a walkthrough of findings with your team. Large applications are split into phases so your developers can start fixing the first findings while we test the rest.
Standards we test against
- WCAG 2.2 Level A and AA — 55 success criteria, including the six A/AA criteria added in 2023.
- WCAG 2.1 Level AA — reported separately because the ADA Title II rule and HHS Section 504 rule cite it.
- Revised Section 508 and EN 301 549 on request, for federal and European procurement.
Who it’s for
Organizations that have never been audited, teams who received a demand letter, public entities preparing for the 2027 deadline, and companies about to launch a redesign who want accessibility built in rather than bolted on.
Frequently asked questions
What's the difference between an accessibility audit and a scan?
A scan is an automated tool run against your pages. It catches roughly a third of WCAG issues and produces false positives. An audit combines that scan with manual expert testing of every in-scope success criterion — keyboard operation, screen reader output, focus order, error handling, zoom and reflow — and tells you how to fix each problem.
How many pages do you test?
We test representative samples, not every URL. Most sites are built from a limited number of templates and components, so we select 15–30 pages that together cover every template, component and critical user journey (sign-up, search, checkout, contact forms, account pages). Issues found in a shared component are logged once and fixed everywhere.
Will the audit tell us if we're ADA compliant?
It tells you precisely where you do and don’t conform to WCAG 2.2 AA (and 2.1 AA), which is the technical standard the DOJ uses for ADA compliance. After remediation and a retest we issue a conformance report you can rely on.
Can you audit mobile apps?
Yes. We test native iOS and Android apps with VoiceOver and TalkBack against WCAG 2.2 AA as applied to mobile, which is what the ADA Title II rule requires for apps.
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.