Back to BlogAccessibility Litigation

What to Do If You Receive an ADA Website Accessibility Lawsuit or Demand Letter

Received an ADA website accessibility demand letter or lawsuit? Learn the first steps to take, what to preserve, how an accessibility audit supports counsel, and why remediation can matter in settlement discussions.

9 steps · 8 min read · 1,492 words

Written by Edward Sm

Digital Accessibility Specialist, ADA Access Group LLC

Updated Reviewed 8 min read

Informational only — not legal advice. Court outcomes and enforcement depend on facts specific to each business.

Two professionals review documents together during a business consultation at an office desk.

Receiving an ADA website accessibility demand letter or lawsuit can create immediate pressure for a small or midsize business. The wrong response is to panic, ignore the deadline, or install a quick accessibility widget and assume the problem is solved.

A better response separates the legal work from the technical work. Your attorney handles legal deadlines, defenses, communications, insurance, and settlement strategy. An accessibility team can preserve technical evidence, evaluate the website, document barriers, support remediation, and verify fixes.

This article explains the technical and operational steps businesses commonly consider after a website accessibility claim. It is not legal advice, and a business that has received an actual complaint or demand letter should speak with qualified counsel promptly.

1. Do not ignore the letter or complaint

A filed lawsuit comes with procedural deadlines, and a demand letter may also include requested response dates. Missing a legal deadline can make a difficult situation much worse.

Send the complete document to counsel rather than responding substantively to the plaintiff or plaintiff’s attorney on your own. Counsel can determine whether the claim is in federal or state court, what causes of action are alleged, which deadlines apply, whether insurance notice is required, and what defenses may be available.

2. Preserve the current state of the website before major changes

Before making a large set of emergency edits, coordinate with counsel and preserve evidence of the website as it existed when the claim was received. That may include relevant pages, source code, screenshots, releases, plugin versions, theme versions, accessibility statements, prior audit reports, vendor contracts, and change logs.

This does not mean leaving barriers unfixed. It means creating a reliable record so the legal team and technical team can distinguish the original condition from later remediation.

3. Run a targeted manual accessibility audit

Laptop, notebook, phone, and glasses arranged for a documented website review.Preserve evidence, document findings, remediate confirmed barriers, and retest the affected workflows.

An audit after a claim should not be a generic homepage scan. Start with the specific allegations in the demand letter or complaint, then expand into the templates, components, and user journeys most likely to contain related barriers.

A useful review may include:

  • keyboard-only navigation;
  • visible focus and focus order;
  • screen-reader names, roles, states, and reading order;
  • navigation menus and mobile menus;
  • forms, labels, errors, and validation;
  • dialogs, popups, and overlays;
  • product search, filters, cart, and checkout for e-commerce;
  • appointment booking or reservation workflows;
  • images and meaningful alternative text;
  • third-party widgets and embedded services; and
  • the specific barriers alleged by the plaintiff.

Automated testing is useful for quickly finding many detectable failures, but a scanner alone cannot establish that a complex customer journey is usable with a keyboard or screen reader.

4. Give counsel a developer-ready technical report

The legal team needs more than a score. A useful accessibility report identifies what was tested, what failed, where the issue occurs, the user impact, the relevant WCAG criterion, evidence, remediation guidance, and the status of each fix.

That allows counsel to compare the actual site to the allegations instead of negotiating from assumptions. It also helps developers prioritize work that can remove real barriers quickly.

For each issue, maintain a simple lifecycle such as: identified → assigned → remediated → retested → verified.

5. Remediate real barriers promptly

Fixing the website does not automatically make a lawsuit disappear. A legal claim can involve issues beyond the current state of the site, including attorney’s fees, state-law remedies, standing, past encounters, or settlement terms.

However, meaningful remediation can still matter. Under federal ADA Title III, private plaintiffs generally seek preventive and injunctive relief, and courts have recognized that removal of the complained-of barrier can in some circumstances affect whether an ADA claim remains live. In a 2022 Ninth Circuit memorandum, the court noted that voluntary removal of an alleged barrier before trial can moot an ADA claim where the complained-of barrier has actually been removed.

More recently, a federal court decision discussed by Seyfarth Shaw in April 2026 dismissed a website accessibility action as moot after the defendant submitted evidence of commercially reasonable accessibility work and the plaintiff did not submit contrary evidence.

Those decisions do not mean that every remediation effort will produce dismissal. Mootness is fact-specific, different jurisdictions apply different precedent, voluntary-cessation principles matter, and state-law claims can change the analysis.

Can an accessibility audit help reduce a settlement?

Potentially, yes — but never as a guaranteed formula. A documented audit and verified remediation can give counsel better facts for settlement discussions. Instead of negotiating while the website remains unexamined, counsel may be able to show which allegations were confirmed, which were not reproduced, which barriers were fixed, what additional work is underway, and how the business plans to prevent regression.

That can improve negotiating leverage in some cases and may help the parties reach a lower or more practical settlement than they would without technical evidence or remediation. But an audit does not erase a claim, guarantee a dismissal, or guarantee that a plaintiff will accept a lower dollar amount.

The settlement amount can depend on many factors outside the accessibility consultant’s role: the jurisdiction, claims pleaded, plaintiff, counsel, litigation history, statutory remedies, attorney’s fees, strength of defenses, business facts, insurance, timing, and whether the matter has already progressed through litigation.

The accurate business statement is: a prompt audit and documented remediation may strengthen your legal team’s position and can support settlement negotiations.

6. Keep the roles separate: attorney, accessibility consultant, developer

Accessibility litigation is easier to manage when responsibilities are clear.

  • Attorney: legal advice, response strategy, deadlines, pleadings, defenses, settlement negotiations, confidentiality, insurance, and legal communications.
  • Accessibility consultant: technical evaluation, manual testing, WCAG mapping, evidence, remediation guidance, retesting, and accessibility documentation.
  • Developer or agency: code and content changes, component fixes, platform configuration, third-party coordination, and implementation.

Depending on counsel’s strategy, technical work may sometimes be coordinated through counsel. Businesses should ask their attorney how communications, reports, and testing should be structured in the context of active litigation.

7. Do not treat a widget as the litigation response

Installing an accessibility widget after receiving a claim is not the same thing as evaluating and fixing the underlying website. A widget may alter some aspects of presentation or interaction, but it does not automatically repair inaccessible templates, checkout flows, forms, dialogs, PDFs, or third-party applications.

The Federal Trade Commission’s 2025 accessiBe order also illustrates why businesses should be cautious about broad automated-compliance claims. The practical goal after a claim should be evidence-based testing and remediation, not a marketing badge.

8. Retest the exact workflows that matter to the claim

After remediation, retest the affected components and the complete user journey. If a checkout issue involved keyboard focus, do not stop after a developer changes the CSS. Verify the full flow with a keyboard. If a screen-reader user could not identify a control, retest the accessible name, role, state, and behavior in context.

Keep dated records of the verification. A remediation ticket without retesting is weaker evidence than a verified result.

9. Build a monitoring process after the immediate case

Accessibility can regress. A redesign, marketing popup, new booking tool, updated theme, payment provider, or third-party script can reintroduce barriers after a successful remediation project.

After the urgent issues are resolved, establish a recurring process that combines automated monitoring with periodic manual testing of high-value user journeys. For many SMBs, quarterly review plus an annual deeper re-audit is more practical than treating accessibility as a one-time emergency.

A practical response sequence

  1. Send the demand letter or complaint to qualified counsel.
  2. Identify legal and insurance deadlines.
  3. Preserve the relevant website state and documentation.
  4. Have counsel coordinate the technical review as appropriate.
  5. Perform a targeted manual accessibility audit.
  6. Document confirmed barriers and remediation priorities.
  7. Fix high-impact issues and the allegations that can be validated.
  8. Retest and document the results.
  9. Provide technical evidence to counsel for use as counsel considers appropriate.
  10. Continue monitoring after the dispute is resolved.

How ADA Access Group can support the technical side

ADA Access Group is not a law firm and does not provide legal advice. We can work with a business and its counsel on the technical side of a website accessibility matter, including manual accessibility testing, developer-ready audit findings, remediation guidance, retesting, and ongoing monitoring.

If you received an ADA website accessibility demand letter or lawsuit, request an urgent Website Accessibility Review. Bring the specific allegations so the technical review can focus on the issues and user journeys that matter most.

Sources

This article is general technical and business information, not legal advice. If your business has received a demand letter or lawsuit, consult qualified legal counsel about your specific facts and deadlines.

Article Tags

ADA website lawsuitADA demand letterwebsite accessibilityWCAG auditaccessibility remediationsettlementlitigation supportmanual testing

Need a website accessibility audit?

This article explains the topic. The audit is a manual WCAG 2.2 AA review (WCAG 2.1 AA where a requirement names 2.1) with a prioritized report — not another automated scan.