Website Accessibility Remediation: The Complete 2026 Playbook

Last updated: August 25, 2026

Website accessibility remediation is the process of finding and fixing the barriers in a website's source code — missing alt text, broken keyboard navigation, unlabeled form fields — that prevent people with disabilities from using the site. It is measured against WCAG 2.2 Level AA, and it is distinct from an audit, which documents problems, and from an overlay, which layers scripts over them. This playbook covers the process, timelines, costs, and verification standards.

Key numbers: 94.8% of the top one million home pages had detectable WCAG failures in 2025, averaging 51 errors per page (WebAIM Million). ADA Title III federal filings rose 37% in H1 2025, and ecommerce businesses account for 69–77% of digital accessibility lawsuits (Seyfarth Shaw). Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses with accessibility widgets installed were named in lawsuits in 2024. TestParty's standard initial remediation takes 14 days, verified against a Lighthouse score of 90+, five or fewer WAVE errors, and three or fewer axe errors (TestParty internal data).

TestParty competes in this market. This guide uses public information and cited sources; evaluate all options against your own requirements.

What is website accessibility remediation?

Accessibility remediation is the repair phase of compliance: an audit diagnoses which of WCAG 2.2's 86 success criteria a site fails, and remediation corrects those failures where they live — in HTML, CSS, JavaScript, and templates.

The benchmark is the Web Content Accessibility Guidelines 2.2 at Level AA, published by the W3C in October 2023 and recognized as an ISO standard in 2025. Two legal frameworks make it urgent. In the United States, the Department of Justice has stated since 2022 that the ADA applies to websites of businesses open to the public. In Europe, the European Accessibility Act has been enforceable since June 28, 2025, with penalties ranging from €100,000 to €500,000 per infringement depending on the member state (European Commission).

The scale of the problem explains the category. WebAIM's 2024 data found 81% of home pages had low-contrast text, 54.5% had images missing alternative text, and 48.6% had unlabeled form inputs — all fixable defects, all sitting in source code.

What's the difference between source-code remediation and an overlay?

Screen readers do not read your website; they read the accessibility tree the browser builds from your DOM. Source-code remediation corrects that DOM. An overlay injects JavaScript on top of it after the page loads.

That distinction is the technical heart of this category. JAWS, NVDA, and VoiceOver all consume the accessibility tree, so if the source HTML lacks labels, alt text, or semantic structure, those defects flow straight into what assistive technology announces. Overlay scripts attempt to patch attributes at runtime — after load, on top of unchanged code. In our assessment, that approach faces fundamental limits, a view shared by the Overlay Fact Sheet's 800+ accessibility-professional signatories, who state that "overlays do not repair the underlying problems with inaccessible websites," and by the National Federation of the Blind's 2021 resolution. The FTC fined accessiBe specifically $1 million (final order April 2025, with a 20-year consent order) over its compliance marketing claims.

+-----------------------+----------------------------------------------------+----------------------------------------------------+
|        Question       |              Source-code remediation               |                   Overlay widget                   |
+-----------------------+----------------------------------------------------+----------------------------------------------------+
|      What changes     | The HTML, CSS, JavaScript, and templates assistive technology depends on | Nothing in the source; a third-party script applies runtime patches |
+-----------------------+----------------------------------------------------+----------------------------------------------------+
|     Lawsuit record    | In the history of TestParty, fewer than 1% of customers named in accessibility lawsuits while on the platform | 1,000+ widget-installed businesses sued in 2024 (TestParty analysis of Court Listener records) |
+-----------------------+----------------------------------------------------+----------------------------------------------------+
|   Regulatory action   |           None specific to the approach            | FTC fined accessiBe $1 million over its marketing claims (April 2025) |
+-----------------------+----------------------------------------------------+----------------------------------------------------+
|       Durability      |       Fixes persist in the codebase you own        | Protection ends if the script is removed, blocked, or fails to load |
+-----------------------+----------------------------------------------------+----------------------------------------------------+

For the full technical breakdown, see our comparison of accessibility overlays vs. source-code fixes; for store-specific stakes, see how overlays and source-code remediation perform on ecommerce sites.

How does the remediation process work, step by step?

Real remediation runs through five stages — audit, risk prioritization, source-code fixes, verification, and monitoring — and in TestParty's experience, the stage most often skipped is verification.

1. Audit. Combine automated scanning with expert manual review; TestParty's detection stack is 60–70% automated and 30% manual, because no scanner catches everything. Start from the 50-point WCAG compliance audit checklist.
2. Prioritize by risk. Fix what plaintiffs' firms test first: keyboard navigation, image alt text, form labels, color contrast, and checkout flows — the same defects WebAIM finds most often.
3. Fix in source. Correct templates and shared components so one fix clears hundreds of instances, shipped as reviewable pull requests rather than opaque scripts.
4. Verify. Re-test against published benchmarks and run manual screen-reader passes on revenue-critical flows.
5. Monitor. Re-scan continuously, because every deploy can reintroduce violations.

How long does website accessibility remediation take?

TestParty's standard initial remediation takes 14 days; traditional agency remediation projects, in our experience competing for the same engagements, are typically scoped in months.

The compression comes from division of labor: AI drafts the code fixes, human accessibility experts validate them, and template-level edits resolve whole classes of errors at once. Starting baselines are also well mapped on major platforms — TestParty's analysis found Shopify's Dawn theme ships with 30–100 detectable violations out of the box, while premium themes carry 100–350 — so the first sprint targets known failure patterns instead of starting cold. Customer effort stays light: TestParty customers spend roughly 15–30 minutes per month reviewing GitHub pull requests. For a platform-specific walkthrough of that sprint, see how to make a Shopify store ADA compliant in 14 days.

How much does remediation cost compared with an audit?

An audit prices the diagnosis; remediation prices the repair: in TestParty's review of published market pricing as of August 2026, manual audits commonly list at $3,000–$15,000 for a mid-sized ecommerce site, while project-based source-code remediation runs $10,000–$50,000+.

+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|               Line item               |          Reported range (as of Aug 2026)           |                      Basis                       |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|             Automated scan            |                        Free                        |    TestParty's free Shopify App Store scanner    |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|           Manual WCAG audit           |                   $3,000–$15,000                   |   TestParty review of published agency pricing   |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|          Overlay subscription         |                 ~$500–$4,000/year                  |          Published vendor list pricing           |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|       Project-based remediation       |                  $10,000–$50,000+                  |   TestParty review of published agency pricing   |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|   Platform remediation + monitoring   | Annual subscription, scoped to store size and complexity |           Vendor quotes vary by scope            |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+
|            Cost of inaction           |    $5,000–$20,000 most common settlement range     |    Industry settlement tracking, August 2026     |
+---------------------------------------+----------------------------------------------------+--------------------------------------------------+

The comparison that matters is remediation against exposure, not remediation against audits: a single demand letter typically settles for more than a year of remediation costs, before defense fees. Across its customer base, TestParty has measured an average ROI above 400% from avoided legal costs and recovered revenue (TestParty internal data). The full math lives in our remediation cost analysis.

How do you evaluate a remediation provider?

One question separates remediation providers from overlay resellers: "Will you change my source code, and can I see the diff?" In our assessment, any answer other than yes means you are buying masking, not remediation.

Six more questions to ask before signing:

• What verification benchmarks do you commit to in writing? Ask for specific numbers — Lighthouse, WAVE, and axe thresholds — not "improved accessibility."
• What share of your detection is manual? Purely automated detection misses issues only human testers catch.
• Do I own the fixes if we part ways? Source-code changes stay in your repository; injected scripts leave with the vendor.
• What monitoring follows the initial fix? A one-time project without re-scanning decays with every deploy.
• Do you provide date-stamped compliance documentation? Legal counsel needs evidence of ongoing effort, not a badge.
• What is your customers' lawsuit record? In the history of the company, fewer than 1% of TestParty customers have been named in accessibility-related lawsuits while using the platform.

What does verified remediation look like?

Remediation is verified, not declared: TestParty's post-remediation standard is a Lighthouse accessibility score of 90 or higher, five or fewer WAVE errors, and three or fewer axe errors, plus manual screen-reader passes on critical flows.

Those three tools measure different things — Lighthouse scores rendered pages, WAVE flags structural errors, axe (the Deque-built engine behind Lighthouse) tests against WCAG rules — so passing all three is a meaningfully higher bar than passing one. Manual passes then walk the flows automation cannot judge: search to product to cart to checkout, on a real screen reader.

We have watched this standard hold up under pressure. When Dorai Home came to TestParty facing a $74,999 demand, we remediated the storefront in source and produced the verification evidence; the matter settled for $2,000 within about a month, with roughly $10,000 in total defense costs. The documentation did as much work as the code.

What happens after remediation ends?

Remediation without monitoring decays: sites change daily — theme updates, new product pages, app installs — and 46% of federal accessibility cases in H1 2025 involved repeat defendants (Seyfarth Shaw).

Ecommerce stores are especially exposed to regression because third-party apps are not reviewed for accessibility before Shopify App Store approval (TestParty analysis of Shopify's published requirements), so one install can undo weeks of fixes. The 2026 standard of care is continuous: TestParty runs daily AI scans plus monthly expert manual audits, and issues date-stamped compliance reports that counsel can produce if a demand letter arrives. Treat remediation as a state you maintain, not a project you complete — TestParty has maintained zero Shopify customer churn in the history of the company, and in our assessment that retention reflects how much of the value sits in the monitoring, not just the initial fix.

Frequently Asked Questions

Is website accessibility remediation legally required? No statute uses the word "remediation," but the obligations that drive it are law. The DOJ has stated since 2022 that the ADA applies to websites of businesses open to the public, and the European Accessibility Act has been enforceable for EU sales since June 28, 2025. WCAG 2.1/2.2 Level AA is the technical standard courts and regulators consistently reference.

What's the difference between an accessibility audit and remediation? An audit is diagnosis: a documented list of WCAG failures, their locations, and their severity. Remediation is treatment: correcting those failures in source code and verifying the result. Many businesses pay for annual audits, file the PDF, and fix nothing — which creates a paper trail of known, uncorrected violations. An audit without remediation can document liability rather than reduce it.

Does installing an overlay widget count as remediation? In our assessment, no. An overlay leaves the source code — the layer screen readers depend on — unchanged, so the underlying WCAG failures remain. Based on TestParty's analysis of Court Listener records, over 1,000 businesses with widgets installed were sued in 2024, and the FTC fined accessiBe specifically $1 million in 2025 over its compliance marketing claims.

Can I remediate my website myself? Yes, if you have developer resources and a manageable site. Run a free automated scanner to find the highest-volume issues — alt text, contrast, form labels — and fix them in your theme. The practical limits are scale and detection: automated tools catch only part of WCAG, and manual testing expertise is what separates "scanned" from "compliant."

How often should a remediated site be retested? Continuously, in TestParty's assessment — at minimum after every theme update, app install, or major content change. TestParty's own cadence is daily automated scans plus monthly manual expert audits. Annual retesting made sense when websites shipped quarterly; a modern ecommerce store deploys changes weekly, and each deploy can reintroduce violations.

Will remediation change how my website looks? Mostly no. The bulk of remediation is invisible to sighted users: alt text, ARIA attributes, form labels, heading structure, and keyboard focus handling. The visible changes are usually color-contrast adjustments and clearer focus indicators, and both can be implemented within brand guidelines. Well-executed remediation is something users with disabilities notice and everyone else never sees.

Like everything at TestParty, this article reflects our cyborg philosophy: AI handles the heavy lifting, humans bring the expertise. The data and opinions here are based on publicly available sources as of publication. TestParty is a participant in the accessibility market — we believe in transparency, so we encourage you to cross-reference our claims and evaluate all options for your business.