- Large companies have mostly remediated, so plaintiff firms now target small and medium businesses with high automated scan error counts.
- Free scanning tools are the triage layer: scan-detectable errors are how you get discovered, and broken user flows are what a claim gets built on.
- A dated documentation record, before-state evidence, remediation records, and an ongoing program, is what separates a defensible business from one that looks like it did nothing.
Small businesses are targets for ADA website lawsuits because large companies have mostly remediated their websites, and plaintiff law firms have shifted their attention to small and medium businesses that don’t know their websites have accessibility issues. The vulnerability is the awareness gap: a small business with a high automated scan error count is easy to find, easy to document, and unlikely to have a record showing any accessibility effort. This article is general information, not legal advice.
How Plaintiff Firms Find Small Business Websites
Plaintiff firms don’t browse the web looking for inaccessible checkout pages. They use free automated scanning tools as a triage layer. A scan takes seconds, costs nothing, and produces a list of errors that can be dropped into a demand letter. If your homepage returns dozens of scan-detectable errors, you’re on the shortlist. If it returns few or none, the firm moves on to the next target.
That’s why the scan layer matters so much even though scans only catch a fraction of accessibility issues. Scan-detectable errors are what get you discovered in the first place. The deeper issues, a keyboard trap in your cart, a form a screen reader user can’t complete, are what a real claim gets built on once you’ve been found.
Why Small Businesses Specifically
- Enterprise websites have been sued, settled, and remediated over the past decade, so the easy large targets are gone.
- Small businesses rarely conduct (manual) accessibility audits, so error counts stay high and visible.
- Themes, plugins, and page builders reintroduce issues with every update, and nobody is monitoring.
- Most owners have never heard of WCAG conformance until the demand letter arrives.
Two Layers, Two Different Risks
| Layer | What it contains | Role in litigation | Remediation priority |
|---|---|---|---|
| Scan-detectable errors | Missing alt text, contrast issues, missing labels, empty links | How plaintiff firms discover and select targets | First |
| User flows | Checkout, forms, navigation, account tasks tested manually | What an actual claim gets built on | Second |
The sequence follows from how targeting works: eliminate scan-detectable issues first so you stop showing up in triage, then fix your key user flows so a real claim has nothing to stand on. A (manual) audit is how you find the second layer; scans never will.
If a Demand Letter Arrives
Don’t act rashly. The sequence matters: preserve first, then fix.
- Capture a dated record of the site’s state at the time of the claim: screenshots, crawls, archived copies, scan results. This is the litigation hold obligation.
- Then remediate quickly. Fixing the live site is not destroying evidence as long as the before-state was documented first.
- Tie remediation records to specific issues with dates. Fast remediation before a suit is filed supports a mootness argument, but mootness only works with dated evidence proving what you fixed and when.
Remediating without a preserved before-state can look like scrubbing evidence, a spoliation risk, and leaves you unable to prove what the issues actually were.
Settlements Cost More Than the Check
The non-monetary terms are the hidden cost. Forced audits, quarterly user testing, and ongoing monitoring and reporting obligations can exceed the settlement figure. And plaintiffs re-check after settlement: the 12 to 24 month compliance window carries breach risk. Meeting settlement terms is a deadline-and-evidence problem, so track progress against the agreed scope and hold proof you met it before the window closes.
The Record Is the Defense
Accessibility is never one-and-done. Developers and content managers reintroduce issues, so maintenance and monitoring matter. Good faith is a documentation posture: an organized, ongoing program record of audits, monitoring cadence, training, and fixes over time is what separates a defensible company from one that looks like it did nothing. An accessibility statement and contact method help in negotiation and as good-faith evidence, but they’re not a defense, and phone support alone doesn’t cure inaccessibility.
If you want to know where your website stands before a plaintiff firm does, we conduct (manual) accessibility audits with fast turnarounds and competitive pricing. Contact us and we’ll respond ASAP, usually within a few hours.
Related: website compliance ada.
Questions about your compliance path? Contact us.
