· Matt Proctor · Accessibility  · 6 min read

The Math on ADA Compliance for Ecommerce (With Actual Numbers)

A $2,000 settlement. $1,500–$3,000 to fix it properly. Here's why the math on proactive accessibility work is so obvious once you see it.

A $2,000 settlement. $1,500–$3,000 to fix it properly. Here's why the math on proactive accessibility work is so obvious once you see it.

In February 2026, a client settled an ADA lawsuit for $2,000.

That number sounds small. It mostly is. But it came with an attorney fee, a compliance demand, a monitoring period, and several hours of internal time spent on something that had nothing to do with growing their business. And then they had to fix the site anyway.

The total cost of being reactive was higher than the total cost of being proactive would have been. By a significant margin.

This is the math that makes ADA compliance compelling: not the ethics argument (though that matters too), and not the “be a better business” framing. Just the numbers, plainly laid out.

What a lawsuit actually costs

ADA demand letters targeting websites typically follow a pattern. An attorney working with a plaintiff (often a serial litigant who tests sites with automated scanning tools) sends a demand letter citing specific WCAG violations on your site and requesting a settlement to avoid litigation.

Settlements in these cases typically range from $2,000 to $25,000 depending on the size of the business and how aggressively the plaintiff presses. Smaller ecommerce stores usually settle in the $2,000–$5,000 range. The reasoning: it’s cheaper than defending a lawsuit, even if you might win.

The direct payment is only part of the cost:

  • Your attorney’s time reviewing the demand and advising on response: $500–$2,000
  • Internal time coordinating the response, gathering documentation, communicating with your attorney: 5–15 hours
  • Compliance obligations built into most settlements: you agree to bring the site into compliance within 60–90 days, which means you’re doing the remediation work anyway
  • Reputational risk if the lawsuit becomes public, which is uncommon but not impossible

Then you still fix the site. So you’ve paid the settlement, paid legal fees, lost internal time, and you’re now doing the remediation work that would have prevented all of it.

What proper remediation actually costs

For a typical Shopify store, bringing a site to WCAG 2.2 Level AA is a defined project. Not open-ended, not ongoing: a project with a start and an end.

We’ve done this work enough times to have a reasonable sense of what it takes:

Audit: 3–5 hours. A systematic review of the site against WCAG 2.2 Level AA criteria: keyboard navigation, color contrast, alt text, form labels, focus management, touch targets, semantic HTML structure. The output is a prioritized list of violations with specific file and element references.

Remediation: 8–15 hours for a typical Shopify store with a commercial theme and standard customizations. The actual work: fixing keyboard navigation issues in custom JavaScript components, adding alt text to images (or writing a system so your team adds it going forward), labeling form inputs, correcting contrast failures in CSS, fixing focus indicators, addressing heading structure issues.

Testing: 2–3 hours. Manual keyboard testing, screen reader testing with NVDA or VoiceOver, re-running automated scans to confirm fixes.

Total: 12–23 hours. At typical agency rates, that’s $1,500–$3,000 done properly, once.

The overlay widget subscription most merchants install instead costs $49–$99/month, or $600–$1,200/year, indefinitely. It also doesn’t actually achieve WCAG compliance (courts have ruled on this repeatedly), so it doesn’t reduce your legal exposure. You’re paying annually for something that doesn’t solve the problem.

Who is actually filing these lawsuits

It’s worth understanding the mechanism, because it’s not what most merchants imagine.

The plaintiffs in most ecommerce ADA cases are serial litigants. Not users with disabilities who were genuinely harmed by your specific site. These are people who have filed dozens or hundreds of similar cases, often in Florida, New York, and California where the filing fees are low and the legal framework is plaintiff-friendly.

Their process is automated. They (or their attorneys) run WCAG scanning tools across large lists of ecommerce URLs. Any site that returns violations above a certain threshold gets a demand letter. The selection is not personal. They don’t know who you are. Your store showed up in a list and it failed a scan.

This is why the 97% WCAG failure rate across the web matters: nearly every ecommerce store is technically eligible for one of these letters. Being a small business doesn’t protect you. Not having many customers doesn’t protect you. Having an overlay installed doesn’t protect you (courts have addressed this directly).

The stores that are genuinely protected are the ones that have done the actual remediation work and can document it.

The asymmetry in plain terms

ScenarioDirect CostOngoing CostLegal Exposure
Do nothing$0$0High
Install overlay$0 upfront$600–$1,200/yearStill high
Proper WCAG remediation$1,500–$3,000 onceLow (new features built accessibly)Low
Settle after lawsuit$2,000–$5,000 settlement + $500–$2,000 legal+ remediation costReduced but not gone

The proactive path is the cheapest path. It just requires spending money before the problem arrives rather than after.

The five-minute check before calling anyone

If you want a rough read on your site’s current state before engaging a developer, start here:

  1. Run your homepage through WAVE (wave.webaim.org). Free, instant, flags the most common violations. High error counts, especially missing alt text and missing form labels, are the issues that attract automated scanners.
  2. Tab through your checkout. Open your store, press Tab, and navigate to checkout using only the keyboard. If you hit a dead end (a button you can’t reach, a modal you can’t close, a field you can’t identify), that’s a keyboard trap and a meaningful violation.
  3. Check your contrast. Use the Colour Contrast Analyser browser extension on your primary text color. Light gray text on white backgrounds almost always fails.
  4. Inspect your images. Right-click a product image → Inspect Element. If the alt attribute is missing entirely (not just empty), that’s a violation.
  5. Try a filter or dropdown. Add a filter to a collection page using only a keyboard. Can you open it, make a selection, and close it without a mouse?

These five checks won’t tell you everything, but they’ll tell you quickly whether you’re looking at a minor cleanup or a more significant project.

A practical recommendation

If you haven’t thought about accessibility since you launched your store, now is a reasonable time to take a look, not because a lawsuit is imminent, but because the cost of a proactive audit is low and the information is useful regardless.

We do ecommerce site audits that include accessibility as a component alongside SEO, performance, and conversion analysis. If you prefer to scope accessibility specifically, we can do that as a standalone project. Either way, the output is a specific list of what needs to change, in what order, with estimated effort, so you can make a real cost-benefit decision with actual numbers rather than anxiety about a hypothetical.

The $2,000 settlement client, for what it’s worth, now has a properly remediated site. We fixed it over a few days after the settlement. It cost about what we quoted above. They wish they’d done it first.


Last Updated: May 2026

Matt Proctor

Matt Proctor

Co-Founder & Head of Technology

Matt Proctor is a co-founder of A Bunch of Creators and has spent over a decade building and scaling ecommerce businesses. As CTO and COO of Occasion Brands, he grew the company from $6M to over $60M in annual revenue, leading agile teams across product development, digital marketing, and technology. He brings that operational experience — the kind that comes from actually running stores, not just building them — to every client engagement. Matt holds a degree in computer science with a minor in English, which explains his insistence on both clean code and clear communication. Learn more about our team.

Back to Blog

Related Posts

View All Posts »