
Making a website accessible almost always costs less than the lawsuit that forces the question — but there is no single sticker price. ADA remediation cost depends on how large your site is, what platform it runs on, how much custom code and media it contains, and whether you fix the problems in the actual markup or paper over them. A small brochure site on a mainstream platform is a modest project; a large e-commerce catalog with thousands of products, PDFs, and video is a much bigger one. The honest first step is a real audit — ours is free — so you are budgeting against a measured list of defects instead of a guess.
What drives ADA remediation cost?
Remediation is priced by the work, and the work is defined by what an audit finds. Four factors move the total more than anything else.
Number of unique templates, not pages
You do not remediate every page — you remediate every unique template. A 5,000-URL store built from a dozen layouts is far closer in cost to a 12-template site than to a 5,000-page one, because fixing the product template fixes every product. Count your distinct layouts — home, category, product, article, contact, checkout — not your URL total. That count is the single best predictor of scope.
Your platform and how much is custom-built
Correcting a theme on a mainstream platform is more predictable than untangling bespoke JavaScript widgets. A themed Shopify or WordPress site has known failure patterns and known fixes; a hand-rolled single-page app with custom modals, carousels, and drag interactions takes more hours per defect. The more of your interface a developer wrote from scratch, the more of it a developer has to revisit.
Media, PDFs, and third-party embeds
Each of these is its own line item. Prerecorded video needs captions at Level A (WCAG 1.2.2) and audio description at AA (1.2.5). Every PDF that carries real information — menus, intake forms, price lists — needs its own remediation or an accessible HTML replacement. And third-party embeds such as booking widgets, chat, and maps can reintroduce failures you do not directly control. A content-heavy site can spend more on media and documents than on the site template itself.
Automated scans versus expert human testing
Automated scanning detects only about a third of the WCAG success criteria. Screen-reader flow, focus order, keyboard traps, and meaningful alt text need a person. A quote built purely on "clear the scanner" is cheaper because it does less — and it leaves the two-thirds of criteria that plaintiffs and real users actually notice untouched.
What does a real remediation project include?
A credible engagement is more than a scan report emailed back with red highlights. It usually covers:
- An expert audit against WCAG 2.2 AA — automated tooling plus human testing, since tools alone cannot confirm conformance.
- Code-level fixes to contrast, alt text, form labels, headings, focus appearance, and target sizes in the real markup.
- A retest to confirm the fixes hold and did not break anything else, ideally ending in zero automated-scan violations plus a passing human review.
- An accessibility statement documenting your conformance target and contact path — see our accessibility statement guide.
- Ongoing monitoring, because every new page, plugin, and campaign can introduce regressions.
If a proposal skips human testing or the retest, you are buying a scan, not remediation. Before you sign anything, it is worth understanding the difference between a free and a paid accessibility audit so you know what each one can and cannot tell you.
Why is remediation cheaper than a lawsuit?
The comparison that matters is not remediation versus zero — it is remediation versus a demand letter. Most ADA website cases settle for between $10,000 and $75,000 plus a binding commitment to remediate anyway, with the average settlement running $30,000 or more, not counting your own attorney's fees. So a lawsuit bills you twice: the settlement check and the fixes you still owe.
This is a volume business. More than 5,000 digital-accessibility lawsuits were filed in 2025 — up roughly 20% over 2024 — within a near-record 8,667 total ADA Title III filings. Around 70% of the web suits targeted e-commerce. We break the numbers down in our guide to what an ADA website lawsuit costs. Remediation is the only spend in this whole ordeal that reduces future risk instead of settling with one plaintiff while leaving the door open for the next.
If you want a baseline before committing budget, a free accessibility audit shows what an automated scan of your site turns up — the same scan plaintiff firms run when they pick targets.
Do accessibility overlays lower the cost?
They promise to, and they do not. A surface-layer "compliance" overlay is a third-party script sold as making a broken site compliant for a low monthly fee — and it is the wrong tool. WebAIM's million-homepage analysis found sites using overlays averaged roughly as many detectable errors as sites without them. The National Federation of the Blind formally opposes these products, calling them "not only ineffective but harmful." And UsableNet's reports repeatedly find hundreds of companies sued each year already had a widget or overlay installed when they were sued.
Regulators agree. In January 2025 the FTC finalized a $1 million action against overlay vendor accessiBe, alleging it deceptively claimed its widget could make any website compliant; the order bars unsubstantiated compliance claims. We cover it in our post on the FTC's accessibility overlay fine.
One distinction matters. A user-facing preference widget — contrast and text-size controls on a site that is already accessible at the code level, making no compliance claims — is a legitimate convenience; our own site runs one. That is not the same thing as a "compliance" overlay that claims to fix a broken site from the outside. The compliance claim is the snake oil; the preference button is fine. Our post on why overlay widgets fail walks through the mechanics.
How do you keep ADA remediation cost down?
The cheapest remediation is the one that stays small because you caught the problem early. Three habits do most of the work.
- Fix before you are found. The failures behind most suits are mundane — 94.8% of the top million homepages had detectable WCAG failures in WebAIM's 2025 report, overwhelmingly low-contrast text, missing alt text, missing form labels, and empty links or buttons. Clearing those is inexpensive compared with clearing them under a litigation deadline.
- Work from a checklist. Knowing what "done" looks like prevents scope creep and rework. Start with our ADA website compliance checklist.
- Monitor after launch. A clean site in January can be a target by June once new products, plugins, and campaigns ship. Ongoing checks turn a big annual remediation into small, cheap corrections.
ADA Fail audits against WCAG 2.2 AA, remediates at the code level, and monitors so regressions get caught before plaintiff firms do. Request a free WCAG 2.2 audit and get a measured scope — the actual defect list your remediation budget should be built on, not a guess.
Frequently asked questions
Is ADA remediation a one-time fee or an ongoing cost?
Both, in stages. The initial audit and code-level fixes are a defined project with a start and an end. After that, accessibility is a maintenance item like security or SEO: every new page, plugin, or campaign can introduce a fresh barrier. Ongoing monitoring is a modest recurring cost that keeps a full re-remediation from ever coming back.
Can I do ADA website remediation myself?
Partly, and doing so lowers the bill. A capable developer can clear many common automated-scan failures — contrast, alt text, form labels — using free tooling. Where in-house work hits a ceiling is the two-thirds of WCAG criteria that automated scans cannot judge: screen-reader flow, focus order, and keyboard operability need expert human testing, and any full-conformance conclusion should rest on that testing rather than a passing scan.
Does remediation guarantee I will not get sued?
No honest firm can promise that — anyone can file a complaint. What genuine WCAG 2.2 AA remediation does is remove the provable barriers a plaintiff's scanner looks for and give you a documented, defensible position if a claim still arrives. That is far stronger footing than a settlement check, which buys peace with one plaintiff while leaving the barriers in place.