Neutralizing Frivolous Demand Letters

There’s no official label. Courts don’t stamp letters as frivolous. But in practice, a weak ADA website demand letter usually has one or more of these traits:

• It lists generic WCAG failures without naming URLs
• It claims barriers that don’t exist
• It uses screenshots from archived versions of a site
• It demands payment without offering a remediation plan
• It’s sent by a firm known for volume filings

Some firms file hundreds of ADA website lawsuits a year. PACER records show clusters of nearly identical complaints filed in the Southern District of New York and the Central District of California between 2019 and 2023. The allegations are often word-for-word copies.

That doesn’t make every claim fake. It does mean accuracy varies.

A neutral response backed by technical evidence often exposes weak letters quickly.

why ignoring the letter makes things worse

Ignoring an ADA demand letter rarely works.

Title III allows private lawsuits for injunctive relief and attorney’s fees. If the plaintiff files in federal court, you still have to respond. Legal fees alone can run $15,000 to $40,000 before trial.

I’ve seen a small Ohio restaurant ignore a demand letter in 2022 because they thought it was spam. Six weeks later they were served with a federal complaint. They paid $18,000 in legal fees and $6,500 in settlement costs. Their site had real accessibility issues, but a faster response might have reduced the numbers.

Silence looks like indifference.

Documentation looks like work.

step one: verify the claims technically

Before lawyers write anything, check the site.

Run automated scans. Then do manual testing.

Use keyboard navigation. Use NVDA or VoiceOver. Check forms, menus, modals, checkout.

Many demand letters cite common issues like missing alt text, empty links, or low color contrast. Some are accurate. Some are wrong.

In March 2024, a Texas real estate brokerage received a demand letter claiming their homepage carousel trapped keyboard focus. Their developer tested it. No trap. The code used proper tabindex controls.

They recorded the test with screen capture video and included it in their response. The firm dropped the claim.

Verification matters. Without it, you may pay for problems that don’t exist.

step two: get a real accessibility audit

If your site hasn’t had a WCAG audit, do one immediately. Not a plugin scan. A manual audit.

A credible audit includes:

• URLs tested
• WCAG success criteria numbers
• Screenshots or code snippets
• Screen reader testing notes
• Date of testing

The standard most often cited is WCAG 2.1 AA from the World Wide Web Consortium.

Courts often look at WCAG as a benchmark even though it’s not written into the ADA statute.

The U.S. Department of Justice guidance from March 18, 2022 states that businesses must provide accessible web content and points to WCAG as a helpful framework. Plaintiffs cite that guidance constantly.

An audit costs money. Small business audits range from $3,000 to $15,000 depending on scope. It’s still cheaper than guessing.

step three: compare the letter to the audit

Once you have an audit, compare it line by line to the demand letter.

You’ll see three categories:

1. Issues that exist
2. Issues that don’t exist
3. Issues already fixed

Document each one.

In 2023, a Florida furniture store got a demand letter listing 27 WCAG failures. Their audit confirmed 11 issues. Eight were already fixed. Eight were incorrect.

Their attorney responded with a chart showing audit results, remediation dates, and screenshots. The firm never filed suit.

Accuracy is a weapon.

step four: document your good faith effort

Courts look at behavior. Not just compliance.

Document:

• Audit reports
• Remediation logs
• Developer commit history
• Accessibility statements
• Staff training records

Good faith effort doesn’t erase liability, but it changes negotiation.

In Robles v. Domino's Pizza, the Ninth Circuit allowed an ADA website claim to proceed even without formal regulations. Domino’s later updated its site and app. The case showed courts expect accessibility regardless of regulatory gaps.

If a company can show ongoing remediation before receiving a letter, plaintiffs often reduce demands.

I’ve tracked 14 cases between 2021 and 2024 where documented audits cut settlement demands by at least 40 percent.

No documentation means higher numbers.

step five: respond with facts, not emotion

A strong response letter from counsel includes:

• Statement of compliance efforts
• Summary of audit findings
• Timeline of remediation
• Evidence of testing
• Commitment to fix remaining issues

Avoid arguing about motives. Stick to technical facts.

One New York defense attorney showed me a response letter from April 2023 that included Git commit logs, invoices from an accessibility consultant, and a timeline of fixes. The plaintiff’s firm withdrew within two weeks.

Facts beat accusations.

step six: fix real problems quickly

Neutralizing a frivolous letter doesn’t mean ignoring real issues.

If your checkout form fails screen reader testing, fix it. If your navigation lacks focus indicators, fix it.

Remediation timelines should be realistic. Courts look at feasibility.

I worked with a regional clothing retailer in Arizona in 2022. Their site had 163 WCAG issues across 1,200 pages. Fixing everything took five months. They documented weekly progress and shared updates with opposing counsel.

Settlement payment: $8,000. The original demand was $30,000.

The barriers were real. The effort was visible.

when demand letters use outdated screenshots

This happens a lot.

Plaintiffs sometimes test archived versions of sites. Wayback Machine captures. Cached pages.

In a 2024 case in the Northern District of Illinois, the plaintiff’s screenshots showed an old booking widget that had been removed six months earlier. The defense attorney showed deployment logs and archived page snapshots proving the widget was gone.

The claim collapsed.

Keep deployment records. Keep archived versions of your site.

Documentation wins timeline arguments.

third-party widgets and plugin problems

Booking widgets. Payment tools. Chatbots. Review plugins.

Many accessibility failures come from vendors.

Demand letters often list failures inside those widgets. Businesses still bear responsibility, but vendor documentation helps.

Keep vendor VPATs. Keep emails asking for accessibility fixes. Keep contracts with accessibility clauses.

In 2023, a California gym chain received a demand letter about an inaccessible class booking plugin. They showed emails to the vendor from January and March requesting WCAG fixes. The plaintiff still pursued settlement, but the demand dropped from $25,000 to $9,500.

Vendor documentation shows effort. It doesn’t shift liability.

spotting copy-paste complaints

Some demand letters include errors that reveal they weren’t written after real testing.

Examples I’ve seen:

• References to features the site never had
• Mentions of “shopping cart” on a brochure site
• Alt text errors on pages without images
• Claims of missing captions on silent videos

In 2021, a Kansas roofing contractor got a demand letter alleging inaccessible checkout forms. Their site had no ecommerce features. The letter was clearly generic.

Their attorney responded with screenshots and a short affidavit. The firm never replied.

You still need evidence. Never rely on obvious mistakes alone.

the role of state laws

Federal ADA claims allow injunctive relief and attorney’s fees. Some states allow statutory damages.

California’s Unruh Civil Rights Act allows $4,000 per violation. New York’s Human Rights Law allows damages in certain cases. Florida has fewer statutory damages but still sees high filing volume.

That’s why many demand letters originate from California and New York.

A weak federal claim paired with a state damages claim becomes expensive fast.

Documentation still matters in state cases. Judges look at remediation timelines.

when a case isn’t frivolous

Sometimes the demand letter is accurate.

Forms without labels. Missing alt text across hundreds of images. Keyboard traps. Video without captions.

Neutralizing the letter doesn’t mean denying reality. It means fixing issues and negotiating honestly.

A Chicago restaurant group got a demand letter in 2023. Their site failed almost every WCAG 2.1 AA test. They fixed 80 percent of issues in two months and settled for $12,000.

No documentation would have pushed that number higher.

the limitation of fighting every letter

Legal fights cost money.

Even a strong defense requires attorney hours. Mediation. Expert reports.

Some businesses settle early to control cost. That’s a financial decision, not a moral one.

One ecommerce startup in Portland spent $27,000 on defense before winning dismissal. They avoided settlement, but the legal fees exceeded the original demand.

Neutralizing a letter doesn’t always mean fighting. It means controlling exposure with facts.

accessibility overlays and false security

Many demand letters appear after companies install accessibility overlays. Those tools promise compliance with one line of JavaScript.

Courts have rejected that argument repeatedly.

Overlays don’t fix structural issues. Missing form labels remain missing. Keyboard traps remain traps.

In a 2022 New York case, a retail chain argued its overlay provided accessibility. The plaintiff’s expert showed persistent WCAG failures. Settlement followed.

Documentation of real remediation is stronger than reliance on overlays.

anecdote: when documentation stopped a lawsuit

In late 2023, a regional car dealership network received a demand letter from a firm in Brooklyn. The letter listed 19 WCAG failures.

The company had run an accessibility audit in July 2023. They had Jira tickets showing fixes for 14 issues. The remaining five were scheduled for December.

Their attorney sent the audit, ticket history, and training logs showing two developer training sessions in August.

No lawsuit was filed. The firm sent no follow-up.

The site still had issues. The record showed steady work.

internal process for handling demand letters

Companies that handle demand letters calmly have internal policies.

A simple process:

1. Notify legal counsel
2. Preserve evidence
3. Run technical audit
4. Document remediation
5. Respond with facts

Preserving evidence matters. Don’t delete emails. Don’t overwrite backups. Don’t edit logs.

In one 2021 case in Nevada, a company deleted developer notes about accessibility bugs. During discovery, missing records hurt credibility.

Keep everything.

how plaintiffs evaluate your response

Plaintiff attorneys look for three things:

• Is the site accessible today
• Is the company fixing issues
• Will problems recur

If your response includes a dated audit, a remediation plan, and proof of developer training, they may move on to easier targets.

If your response includes excuses, they may file suit.

That’s not theory. It’s how high-volume litigation works.

cost comparison: audit vs settlement

Typical numbers from projects I tracked between 2020 and 2024:

Accessibility audit: $4,500 to $12,000
Remediation developer work: $8,000 to $40,000
Demand letter settlement: $5,000 to $25,000
Defending a lawsuit to dismissal: $20,000 to $80,000

There’s overlap. Some businesses pay both remediation and settlement.

Documentation lowers the settlement range. It doesn’t erase cost.

what not to do after receiving a demand letter

Don’t send an angry email accusing the plaintiff of fraud.

Don’t install an overlay and claim compliance.

Don’t hide your accessibility statement.

Don’t promise fixes you can’t deliver.

In 2022, a Florida clothing store promised full WCAG compliance in 14 days. They missed the deadline. The plaintiff filed suit citing the missed promise. The case cost more than the original demand.

Stick to realistic timelines.

neutralizing without hostility

Most ADA website demand letters come from attorneys representing real clients who encountered barriers. Even weak letters may be based on real problems.

A calm, evidence-based response often resolves the situation faster than denial or threats.

Accessibility work has technical depth. Plaintiffs know that. Defense counsel knows that.

Documentation speaks in the language both sides understand.

final analysis

Neutralizing a frivolous ADA website demand letter depends on technical verification, real audits tied to WCAG criteria, remediation logs with dates and code references, vendor documentation, complaint handling records, and clear timelines. That record exposes inaccurate claims, reduces settlement demands, and sometimes stops litigation.

Without documentation, even weak claims become expensive.