Compliance Practice

ADA Web Remediation and WCAG 2.2 AA Compliance

ADA web remediation means fixing the accessibility barriers in your website's code so people using screen readers, keyboards and other assistive technology can use it, then verifying the fixes and monitoring so they stay fixed.

Accessibility fixed in the code, verified with assistive technology, and monitored so it stays fixed. No overlay widget, no automated-scan theater.

Accessibility symbol representing inclusive web design

What this service actually is

Website accessibility has become a legal exposure for almost every business that sells online. Demand letters citing the Americans with Disabilities Act arrive by the thousands each year, and they are not limited to large companies. The two most common responses are both wrong: install an overlay widget and hope, or run an automated scanner and treat a clean report as compliance.

Automated tools catch roughly a third of real accessibility barriers. They can tell you an image has no alt attribute. They cannot tell you that the alt text says image_4837.jpg, that a custom dropdown is unreachable by keyboard, that a modal traps focus behind it, or that a screen reader announces your checkout total as an unlabeled number. Overlay widgets are worse than incomplete: they have been named in litigation themselves, and the accessibility community broadly rejects them.

This practice does the actual work. We audit against WCAG 2.2 AA with automated tooling for coverage plus manual testing with keyboard-only navigation and real screen readers, then remediate in your codebase. Findings are delivered as developer-ready tickets with the element, the failing success criterion, the reason it fails, and the corrected markup or pattern. Then we re-test to confirm, and monitor on a cadence so new content and new releases do not silently reintroduce barriers.

The compliance benefit is the reason most clients call, but it is rarely the largest one. Accessible markup is better markup: correct semantics and heading structure improve search visibility, keyboard and focus discipline reduces user error, and captioning and contrast improvements help a far wider population than the one they were required for.

The problems we are usually hired to solve

A demand letter just arrived

You need a documented, dated remediation program underway quickly. We prioritize the barriers that carry the most exposure and produce the evidence trail counsel needs.

An overlay widget that did not help

The widget is installed and the site is still inaccessible. We remove the dependency and fix the underlying markup, which is the only durable answer.

Keyboard-inaccessible interfaces

Custom dropdowns, tabs, carousels, and modals built without roles, focus management, or keyboard handlers. These are the most common serious failures we find.

Forms that cannot be completed

Unlabeled inputs, errors announced only in color, and validation messages a screen reader never receives. On checkout and intake flows this is both a legal and a revenue problem.

Procurement or grant requirements

A public-sector or enterprise buyer requires a VPAT or an accessibility conformance statement you cannot currently produce honestly.

Regression after every release

The site was remediated once and drifted back. We add automated checks into the pipeline and a content-authoring standard so the fix holds.

How an engagement actually works

  1. 01

    Initial scan and exposure triage

    A fast automated pass across the site to establish scale, plus a manual look at the highest-risk paths: home, navigation, search, product or service detail, forms, and checkout. Within a few days you get a plain-language summary of where you stand, what carries the most legal exposure, and what full remediation is likely to involve. This is deliberately low-commitment, because you should know the size of the problem before buying a solution to it.

  2. 02

    Detailed WCAG 2.2 AA audit

    The full audit combines automated coverage with manual testing: keyboard-only traversal of every interactive component, screen reader verification across at least two combinations, contrast measurement, zoom and reflow behavior to 400 percent, motion and animation review, and form and error-handling behavior. Each finding records the page, the element, the failing success criterion, the impact, and a severity rating.

  3. 03

    Prioritized remediation plan

    Findings are grouped by root cause rather than listed page by page, because one bad component pattern usually generates dozens of findings. That grouping is what turns an intimidating audit into a tractable work plan, and it is where most of the cost reduction in the project comes from. Each group carries corrected markup, an effort estimate, and a priority based on exposure and user impact.

  4. 04

    Code-level remediation and verification

    We implement the fixes in your codebase, or work alongside your developers if you prefer to keep the changes in-house. Remediated components are re-tested with keyboard and screen reader before being marked closed. Verification is by assistive technology behavior, never by a scanner reporting zero violations.

  5. 05

    Monitoring and sustained compliance

    Ongoing scheduled scanning with alerting on new violations, periodic manual spot checks of key flows, accessibility checks wired into your deployment pipeline, and a short authoring guide for whoever adds content. Where required, we produce an accessibility conformance report or VPAT and keep it current.

What you receive

WCAG 2.2 AA audit report

Every finding with page, element, failing success criterion, user impact, severity, and the corrected pattern. Written to be actionable by a developer, not filed by a lawyer.

Root-cause remediation plan

Findings grouped by underlying component or pattern, with effort estimates and a priority order based on exposure and real user impact.

Implemented code fixes

Accessible component patterns in your codebase with correct semantics, roles, labels, focus management, and keyboard support.

Assistive technology verification

Documented re-testing with keyboard-only navigation and multiple screen reader and browser combinations, recorded per remediated item.

Monitoring and pipeline checks

Scheduled scanning with alerting, plus automated accessibility checks in continuous integration so regressions fail before release.

Conformance documentation

An accessibility statement, and where procurement requires it, a VPAT or accessibility conformance report kept current as the site changes.

Who this is for

Ecommerce and lead-generation sites

Any business transacting online, which is where the large majority of ADA web demand letters are directed.

Healthcare, education, and public-adjacent organizations

Where accessibility obligations are explicit and often contractual, and where the affected user population is disproportionately large.

SaaS products selling to enterprise or government

Where a VPAT or conformance report is a procurement gate and cannot be produced without real remediation behind it.

Frequently asked questions

It is the work of finding and fixing the WCAG 2.2 AA failures on a website at the code level, verifying each fix with assistive technology, and documenting conformance. It replaces overlay widgets, which do not fix the underlying code.

No. Overlays modify the page after it loads and cannot repair semantics, focus order, or component behavior. They have been cited in litigation against the sites using them, and accessibility advocates broadly reject them. The only durable remediation is in the code itself.

Courts have widely treated websites of public accommodations as covered under Title III, and the Department of Justice has stated that ADA requirements apply to web content. WCAG 2.1 or 2.2 at level AA is the standard used in practice in settlements and consent decrees, which is why we audit against it. We are not attorneys and this is not legal advice; we work alongside your counsel.

The initial scan takes a few days. A detailed audit of a typical marketing site or storefront runs two to three weeks. Remediation depends on how many distinct component patterns are broken rather than page count: most sites land between four and ten weeks, and a large application can run longer.

Usually yes, given repository access, and that is the common arrangement. Some clients prefer we deliver the corrected patterns and coach their team through implementation, which transfers the capability. Both work; the second is slower and cheaper.

Rarely in any meaningful way. Most fixes are invisible: markup semantics, labels, roles, focus order, and keyboard handlers. The visible changes are usually limited to color contrast adjustments and focus indicators, and we work within your existing design system to make them.

A one-time fix decays. Every new page, product, component, and content update is an opportunity to reintroduce a barrier, and if you are ever challenged, a current monitoring record is far stronger evidence of good faith than a two-year-old audit.

Yes, as a side effect. Correct heading hierarchy, descriptive link text, meaningful alt attributes, semantic landmarks, and captioned media are simultaneously accessibility requirements and things search engines use to understand a page.

Related services

Start with a scan, not a contract.

Send us your URL. You will get a plain-language read on where you stand and what remediation would realistically involve.

Start a conversation