There's a quiet but persistent uptick in ADA Title III demand letters and lawsuits targeting law firm websites. The pattern is consistent enough now that any marketing director or operations partner at a 10–250 attorney firm should at least understand it.
This post is descriptive, not legal advice. We are not your counsel. But the technical patterns plaintiff firms cite are public record, and your firm should know them.
The pattern
A serial-plaintiff firm identifies a law firm website (often via automated scanning of attorney directories or local-search results), runs an automated WCAG scan, picks 5–15 issues from the report, and sends a demand letter. The demand typically requests a specific dollar amount and a remediation timeline. Settlement is the default outcome — defending is more expensive than the demand.
The cited issues are almost always the same: missing alt text on practice-area imagery, color contrast failures on calls-to-action, unlabeled form fields on contact and intake forms, missing focus indicators, inaccessible PDFs of intake forms or attorney bios.
Why law firms specifically
Three factors compound:
- Visibility: law firm sites optimize aggressively for local search, which means they're easy to find through automated tooling.
- Asymmetric risk: a public ADA complaint against a firm that practices, say, employment law or civil rights creates reputational mismatch the firm desperately wants to settle quietly.
- Predictable settlement math: plaintiff firms have data on what firms in your size range typically pay to make a complaint disappear. The number is usually in the low five figures plus remediation costs.
What you can verify yourself, today
You don't need to hire anyone to know whether your firm has the kind of issues that show up in these demand letters. The fastest check:
- Open your firm's homepage and the top three practice-area pages.
- Try to navigate them with the keyboard alone (Tab, Shift+Tab, Enter). Note where the focus indicator disappears.
- Submit your contact form using only the keyboard. Note any place you couldn't tell what field you were on.
- Open any linked PDF (intake form, retainer template, attorney bio). In Acrobat or Preview, check Tools → Accessibility → does it have tagged structure?
These five minutes catch a meaningful share of what shows up in demand letters.
What automated scanning catches that manual checking doesn't
A single scan of a 50-page firm site will surface several hundred discrete issues an attorney working through the site by hand will miss — especially anything template-driven. If a header issue exists on one practice-area page, it usually exists on all of them. Manual checking finds one instance; automated scanning finds the pattern.
SEO Score API's law firm vertical runs continuous WCAG 2.1 AA scans plus SEO checks against your full firm site, with a timestamped audit log retained per your tier. The /industries/law-firms page has the full feature breakdown and a free single-page scan to try right now.
What does WCAG 2.1 AA actually require?
WCAG 2.1 AA is the accessibility standard most plaintiff firms reference and most courts have aligned with. It covers four principles — perceivable, operable, understandable, robust — through ~50 specific success criteria. About 30–40% of those criteria are testable mechanically; the rest require human judgment. Your goal is to clear the automatable criteria first and then have a human check the rest.
What if I receive a demand letter?
Get defense counsel before you do anything else. Do not respond directly. Do not auto-remediate without documenting what you changed and when — that record becomes important in the response. Do preserve the current state of your site so opposing counsel cannot allege you destroyed evidence.
Having a pre-existing audit log of your accessibility scanning program is materially helpful at this stage; it shows good-faith ongoing effort rather than panicked response. That's part of why we recommend continuous monitoring before anything happens, not as a reaction to a letter.
What about overlay widgets?
Overlays (accessiBe, UserWay, AudioEye) are AI-driven scripts that overlay accessibility "fixes" on top of an inaccessible site. They've themselves been the subject of lawsuits, and plaintiff firms now routinely name them in complaints rather than considering them protective. Some courts have explicitly held that an overlay does not satisfy ADA Title III. Most accessibility practitioners now consider them anti-patterns.
Audit-and-evidence tools (which is what we are) take the opposite approach: scan, report, document, and let your team or your developer remediate the underlying code or content.
The minimum reasonable accessibility program for a small firm
Three things, in order:
- A continuous automated scan of the public site, with monthly review.
- An annual or biannual manual audit by an accessibility specialist or a consultant familiar with WCAG.
- A documented remediation workflow — when an issue is found, who fixes it, on what timeline, and where it gets logged.
That's the program. It does not cost five figures to set up, and it materially reduces the risk profile that plaintiff firms target.
Ready to scan your firm's site? Try a free single-page scan on the law firms page →