Back to reviews and guides

Received an ADA Demand Letter? Here's What to Do Next

If you receive an ADA demand letter act quickly: acknowledge receipt, preserve evidence, notify counsel and run a targeted accessibility audit. Prioritise fixes for core user flows, document every step, and provide a measured response with realistic timelines.

How to respond to ADA compliance demand letters is a common question after someone sends a notice about your website or premises. This guide gives a clear, step by step path you can follow right away. It focuses on practical actions you can take, technical priorities, and mistakes to avoid.

First actions: what to do in the first 48–72 hours

1. Acknowledge receipt but do not admit fault

Send a brief acknowledgment saying you received the letter and you are reviewing the matter. Do not confirm liability or promise full compliance before you know the details. Keep the reply factual and measured.

2. Identify the sender and the claimed problems

Note who sent the letter. Is it a plaintiff, a law firm, or an accessibility consultant? Record the specific pages, examples, or attachments cited. If the letter lacks detail, ask for precise URLs, screenshots, device details and the date the alleged problem was observed.

3. Preserve evidence

Save the original letter, emails, server logs, and the exact versions of the webpages or documents cited. Capture dated screenshots and the HTML/CSS served that day. Preservation makes later testing and defence easier.

4. Notify the right people

Tell your legal team, product owner, engineering lead and accessibility contact. If you use an external accessibility vendor, notify them now so they can scope an audit quickly.

5. Contact experienced counsel

Engage a lawyer who has experience with ADA and accessibility cases. They will advise on deadlines, negotiation options and whether the claim targets your website, physical premises, or both.

How to respond to ADA compliance demand letters: a practical 6-step process

  1. Step 1 — Triage the claim

    Decide whether the claim is high priority. Claims that affect checkout, login, booking, or core user flows should be treated as urgent. Create a short triage report listing affected URLs, priority, and initial resource needs.

  2. Step 2 — Ask for details and an extension if needed

    If the demand letter is vague, request specific examples and a reasonable timeline to investigate. A short extension can buy time to run a targeted audit. Your legal counsel can draft this request.

  3. Step 3 — Run a targeted accessibility audit

    Combine automated scans with manual testing. Automated tools find many defects but will miss keyboard issues, screen reader behaviour, and dynamic content problems. Include:

    • Automated scans across the cited pages
    • Manual keyboard-only navigation tests
    • Screen reader checks with NVDA, VoiceOver or JAWS on representative pages
    • Accessibility checks for PDFs and media

  4. Step 4 — Prioritise fixes and build a remediation plan

    Prioritise defects that block access to essential functions. Provide a remediation plan that lists fixes, owners, and estimated completion dates. Use WCAG 2.1 Level AA as the baseline unless a different standard was requested.

  5. Step 5 — Draft a measured response

    Your response should:

    • Acknowledge receipt
    • Summarise the steps you will take to investigate
    • Request any missing details
    • Offer a realistic remediation timeline and milestones
    • State that you will provide evidence of remediation

    Have counsel review the response before sending it.

  6. Step 6 — Negotiate and document any agreement

    If the sender offers to settle, document the agreement in writing. Include a remediation checklist, timelines, reporting cadence and how proof of fixes will be delivered. Keep copies of every communication.

Quick template: what to include in your reply

Use this as a framework for your reply. Have a lawyer adapt it to your case.

  • Reference the date of the demand letter and the pages cited.
  • Confirm you have received the letter and are investigating.
  • Request any additional details needed to reproduce the issues.
  • State that you will conduct an accessibility audit using recognized standards.
  • Provide estimated milestones for investigation and remediation.
  • Offer to share remedial evidence and to discuss reasonable accommodations.

Technical remediation checklist for web teams

Focus on core accessibility barriers first. The list below covers common failures that often appear in demand letters.

  • Semantic headings and proper HTML structure
  • Alt text for images where meaning is conveyed
  • Keyboard operability for menus, forms and interactive widgets
  • Visible focus indicators and logical tab order
  • Labels and instructions for form fields; clear error messages
  • Colour contrast that meets WCAG 2.1 Level AA for text and UI elements
  • Accessible ARIA usage, avoiding incorrect or redundant ARIA roles
  • Captions and transcripts for audio and video content
  • Accessible PDFs or HTML alternatives to documents
  • Skip links to bypass repeated content

Testing and proof: how to show you fixed problems

Proof matters. Store dated evidence and test records. Useful items to keep:

  • Audit reports from automated tools
  • Screenshots or screen recordings showing fixes
  • Accessible code diffs or ticket references from your issue tracker
  • Manual test scripts and results using keyboard, NVDA or VoiceOver
  • User testing notes if you engaged people with disabilities

Common mistakes that worsen the situation

  • Relying only on automated scans. They miss keyboard and screen reader problems.
  • Promising fast total compliance without a plan. That raises expectations you may not meet.
  • Using commercial overlay widgets as a substitute for real repairs. Courts and regulators have expressed scepticism about overlays when core issues remain.
  • Not documenting fixes thoroughly. Lack of records undermines defence or negotiation.

Standards and terms you should know

  • ADA — Americans with Disabilities Act. Often cited in US demand letters.
  • WCAG 2.1 Level AA — the common technical benchmark for web accessibility.
  • Section 508 — US federal standard for government websites and systems.
  • WAI-ARIA — accessibility techniques for dynamic web content and widgets.

If the matter proceeds to litigation

If the sender files a lawsuit, your lawyer will advise on deadlines, discovery obligations and how to present remediation evidence. Continue remediation while litigation proceeds. Stopping fixes can weaken your position.

When to call an accessibility specialist

Call an external accessibility expert when you need impartial testing, user testing with people who have disabilities, or a remediation plan you can deliver. Specialists help translate audit findings into clear engineering tickets and QA checks.

Responding to an ADA demand letter well depends on acting quickly, investigating thoroughly, and documenting everything. Get legal advice, run a combined automated and manual audit, prioritise core user flows and keep the sender informed with realistic timelines.

Need a next step now — preserve the original letter, capture dated screenshots of the cited pages and ask your counsel to request precise examples from the sender.