Your Municipal Client Just Got a Demand Letter. Now What?

The Call You Need to Be Ready For

It will not arrive on your timeline. A demand letter shows up in your municipal client's inbox on a random weekday — forwarded by their city attorney with a one-line message: "Can you look at this?"

The letter is two to four pages. It names a plaintiff — often a resident with a disability who encountered barriers on the municipality's website. It cites Title II of the ADA. It references specific WCAG 2.1 Level AA success criteria. It lists concrete accessibility failures: missing alt text on the permit portal, inaccessible forms on the utility payment page, a PDF meeting agenda that a screen reader cannot parse. And it includes a deadline — typically 30 days — before the plaintiff's attorney escalates to federal court.

Demand letters outnumber filed lawsuits by an estimated 7 to 10 times. With over 4,900 accessibility lawsuits filed in 2025 and plaintiff firms expanding into the municipal space after the Title II deadline, the question is not whether your client will receive one. It is when.

Your response in the first 48 hours determines whether this becomes a five-figure settlement or a documented demonstration that your client is already doing the work. Here is the playbook.

Hour 0–2: Do Not Respond to the Sender

The single most important thing to do in the first two hours is nothing — at least externally. Do not reply to the plaintiff's attorney. Do not acknowledge the claims. Do not promise to fix anything. Do not apologize. Any response can be used as evidence, and an uncoordinated reply can undermine your client's legal position before their attorney has even reviewed the letter.

What you do in these two hours is internal:

Read the letter carefully. Identify every specific claim. Demand letters typically list concrete accessibility barriers — missing alt text on specific pages, color contrast failures on specific elements, keyboard navigation issues on specific components. These are not vague accusations. They are testable, verifiable assertions about specific WCAG success criteria.

Determine which claims involve your work. If you built or maintain the website, the payment portal, the permit system, or the document library, some or all of the cited failures may trace back to deliverables you produced. This is not about blame — it is about scope. You need to know which issues are in your domain so you can act on them.

Alert your client's legal counsel. If the letter came directly to your client and they forwarded it to you, confirm that their attorney has it. If not, that is the first action item: the municipality's attorney must review the letter before anyone responds. Your role is technical support, not legal strategy.

Hour 2–8: Verify the Claims

Most demand letters are generated from automated scan results. The plaintiff's attorney ran a tool — often the same tools you use: axe-core, WAVE, Lighthouse — and compiled the failures into a complaint. This means two things: the claims are probably technically accurate, and they probably do not represent the full picture.

Your job now is to independently verify every claim in the letter.

Run your own scan. Use the same tools the plaintiff's attorney likely used. Run axe-core against the specific pages cited in the letter. Run WAVE. Check Lighthouse accessibility scores. Document the results with timestamps and screenshots.

Test each specific claim. If the letter says the permit application form lacks labels, open that form and check. If it says images on the homepage lack alt text, verify each image. If it says the payment portal is not keyboard-navigable, tab through it. For every claim, your verification produces one of three outcomes: confirmed (the issue exists as described), partially confirmed (the issue exists but is less severe than described), or not confirmed (the issue does not exist or has already been fixed).

Check for additional issues the letter does not mention. Demand letters typically cite the most obvious, automated-detectable failures — the six categories that show up in 96% of scan results. But your scan may reveal additional issues. Document these too. You want a complete picture, not a reactive one.

Document everything. Every scan result, every manual test, every screenshot — logged with dates, tools used, URLs tested, and findings. This is the beginning of your evidentiary record. If you already maintain an audit defense log, this documentation slots directly into your existing framework. If you do not have a log, start one now. Today.

Hour 8–24: Assess Your Documentation Position

This is the moment where the contractors who prepared for this scenario separate from the ones who did not.

If you have been maintaining an audit defense log — with baseline scans, documented remediations, timestamped fixes, and ongoing monitoring records — your client's attorney now has something powerful: evidence of good faith effort that predates the complaint.

A demand letter is fundamentally a negotiation tool. The plaintiff's attorney is assessing whether to pursue litigation or settle. The factors that drive that decision include the severity of the barriers, the strength of the legal claims, and — critically — whether the defendant appears to have been aware of the obligation and made efforts to comply.

An entity with no documentation, no scan history, and no remediation records looks like it ignored accessibility entirely. That entity settles quickly, often for $10,000 to $50,000 or more, plus attorney fees and mandatory remediation under monitoring.

An entity with a documented compliance program — baseline scans, prioritized remediation records, ongoing monitoring, an accessibility statement — looks like it has been actively working toward compliance. That changes the negotiation entirely. The plaintiff's attorney knows that a judge will weigh good faith effort. A well-documented compliance program makes litigation riskier and settlement demands lower.

If you have the documentation: Compile it into a summary package for the client's attorney. Include the baseline scan date and results, the list of issues identified and addressed, the dates each fix was verified, and the ongoing monitoring schedule. This package becomes the foundation of the legal response.

If you do not have the documentation: Be honest with your client about the gap. Then start building the record immediately. Run the baseline scan now. Begin fixing the cited issues now. Document every action with dates and verification. You cannot backdate evidence, but you can demonstrate rapid, organized response — which is itself evidence of good faith.

Hour 24–48: Fix What You Can

You will not remediate an entire website in 48 hours. You should not try. But you can address the specific issues cited in the demand letter, and doing so before the response deadline demonstrates both competence and commitment.

Prioritize the cited violations. The demand letter gave you a checklist. Work through it systematically. Fix the missing alt text. Correct the color contrast failures. Add labels to the unlabeled form fields. Repair the keyboard navigation traps. Set the document language. Tag the PDFs.

Verify each fix. After addressing each issue, re-run the scan against that specific element. Screenshot the passing result. Log it in your audit defense log with the date, the fix description, and the verification method.

Do not stop at the cited issues. If your scan revealed additional failures beyond what the letter mentioned, fix those too. When your client's attorney responds to the demand letter, the response is stronger if it can say: "We have addressed not only the issues you identified but also additional barriers we discovered during our own comprehensive review."

Prepare a remediation timeline for remaining issues. Some fixes take longer — restructuring complex tables, remediating large PDF libraries, rebuilding interactive components. Create a realistic timeline for these items and include it in the documentation package. A concrete remediation plan with specific milestones is more credible than a vague promise to "work on accessibility."

The Response: What Your Client's Attorney Needs From You

Your client's attorney drafts the actual response to the demand letter. Your role is to provide the technical substance that makes that response credible. The attorney needs:

A verified assessment of each claim. For every issue cited in the letter, a clear statement of whether the issue existed, whether it has been fixed, and the evidence supporting that conclusion.

Evidence of prior compliance efforts. If your audit defense log predates the demand letter, this is the most valuable document in the response. It demonstrates that the municipality and its contractor were already aware of accessibility obligations and actively working to meet them.

A remediation summary. What has been fixed since the letter was received, with dates and verification. This shows immediate, responsive action.

A forward-looking compliance plan. Ongoing scan schedule, remediation timelines for remaining issues, monitoring process, staff training, and accessibility statement commitment. This tells the plaintiff's attorney that pursuing litigation will be more expensive than settling — because the defendant is already doing the work.

The Conversation That Changes Your Contract

Here is the part nobody talks about in demand letter response guides: this is a contract moment.

Your municipal client just experienced a concrete, tangible threat that made accessibility real in a way that no blog post, webinar, or deadline countdown ever could. They received a letter with their name on it, from an attorney, citing specific failures in a system they paid you to build.

In the worst case, they blame you. The contract had no accessibility clause, the deliverable had no accessibility testing, and the municipality's attorney starts asking why the vendor did not flag this risk.

In the best case — the case you should be building toward right now — you are the person who already had the documentation. You had the scans. You had the log. You had the fixes underway before the letter arrived. And when the crisis hit, you were the one who guided the response, provided the technical evidence, and resolved the issues within days.

That is not just crisis management. That is a contract renewal. That is a referral to the neighboring municipality. That is proof that your accessibility services have tangible, demonstrable value.

Building the Infrastructure Before the Letter Arrives

Everything in this playbook is easier — dramatically easier — if the infrastructure exists before the demand letter shows up. The contractors who will navigate this cleanly are the ones who built the system months ago:

A baseline scan run before the April 24 deadline, with results preserved and timestamped. A prioritized remediation effort targeting the highest-risk violations first. An audit defense log that documents every scan, every fix, every decision. Accessible PDFs built from structured source files with proper tagging. An ongoing monitoring schedule that runs monthly and produces documented results.

When the demand letter arrives — and with plaintiff firms actively expanding into the municipal market, it is a when, not an if — the contractor with this infrastructure does not panic. They pull the log, compile the evidence, fix the cited issues, and help their client's attorney respond from a position of strength.

Thirty-nine days until the deadline. Build the infrastructure now. The demand letter will be easier when it comes.

---

This post is for informational purposes only and does not constitute legal advice. Consult with qualified legal counsel for guidance specific to your situation.