How to Respond to an ADA Website Demand Letter and Fix Your Site Fast
A plain-language emergency guide for small business owners who just received an ADA website accessibility demand letter, covering exactly what to do in the first 72 hours, why overlay widgets make things worse, and what a documented code-level remediation actually looks like.
Yes, your website must be fixed, and the fastest legal path is to document every step you take starting today. An ADA website demand letter is a formal legal notice that your site may violate Title III of the Americans with Disabilities Act by being inaccessible to people with disabilities. Courts and the Department of Justice treat WCAG 2.1 and 2.2 Level AA as the practical benchmark for what an accessible website looks like, and the strongest defense available to you is a documented, good-faith remediation effort that produces real code changes.
What the Letter Actually Means
ADA Title III covers places of public accommodation, and federal courts have broadly held that commercial websites qualify. A demand letter typically identifies specific barriers a screen-reader user or other person with a disability encountered, cites the ADA, and requests either a settlement payment or proof that you will remediate the site. Ignoring it increases your exposure. Responding quickly with documented progress is the legally sound path.
Note: Nothing in this article is legal advice. You should consult a licensed ADA defense attorney before responding to any demand letter. What this guide provides is a practical framework for the accessibility remediation steps that attorneys and courts look for.
Your 72-Hour Response Checklist
Step 1 — Preserve the Letter and All Related Communications
Do not delete, forward casually, or ignore the letter. Save the original, note the date received, and store all envelopes or email headers. Your attorney will need a clean chain of custody.
Step 2 — Contact an ADA Defense Attorney
Find an attorney who handles ADA Title III website cases specifically. They will evaluate the specific claims, advise on settlement versus litigation, and review any response you send. Many operate on flat fees for demand-letter responses. Do not respond to the sender directly before speaking with counsel.
Step 3 — Order a WCAG 2.2 AA Audit Immediately
You need a documented baseline. An audit against WCAG 2.2 Level AA identifies every barrier on your site and creates the starting record that demonstrates you took the matter seriously on a specific date. WCAGDefender scans any public URL against WCAG 2.1 and 2.2 Level AA at no cost, with no account required, and returns a lawsuit-risk read rather than a vague grade. Run your free scan at wcagdefender.com.
Step 4 — Begin Remediation With Documented Progress
Start fixing the barriers the audit identifies, in order of severity. Every fix should be logged with a date, a description of the change, and who made it. This log is your good-faith evidence. Remediation means changing the actual code of your site, not installing a widget on top of it.
Step 5 — Publish an Accessibility Statement
Post a brief, honest statement on your website acknowledging your commitment to accessibility, identifying the standard you are working toward (WCAG 2.1 or 2.2 Level AA), and providing a contact method for users who encounter barriers. This is a recognized good-faith signal.
Why Overlays Will Not Protect You
Accessibility overlays such as accessiBe, UserWay, and AudioEye are JavaScript widgets that load on top of your existing page markup. They cannot reliably fix structural problems like incorrect heading order, missing form labels, broken keyboard navigation, or ARIA misuse, because those defects exist in the source code the overlay sits on top of. Users who rely on their own screen readers often find that overlays interfere with the assistive technology they already have configured.
Courts have not accepted overlays as a defense in ADA website cases, and lawsuits have continued against, and sometimes named, the overlay itself as a barrier. In 2025 the U.S. Federal Trade Commission took action against accessiBe, including a settlement with a one-million-dollar penalty, over how the company marketed its automated compliance claims. Installing an overlay after receiving a demand letter does not create a defensible remediation record and may signal to plaintiffs' counsel that you are not taking the matter seriously.
WCAGDefender does not install overlays. It detects overlays already present on a site and flags them, because their presence can increase rather than reduce legal risk. Every fix WCAGDefender delivers is a copy-ready code change that goes into the actual site.
What "Substantial Compliance" Means and How to Document It
ADA Title III does not specify a precise technical standard for websites. Courts and the DOJ use WCAG Level AA as the practical yardstick. "Substantial compliance" in this context means you have identified the barriers, begun fixing them in priority order, published an accessibility statement, and can demonstrate ongoing effort with a dated record. It is not a one-time certificate and it does not mean every possible issue is resolved on day one.
A remediation report that shows which barriers existed, which have been fixed, and which remain with a projected timeline is evidence of good-faith effort. WCAGDefender produces a legal-ready packet that includes an accessibility statement, a good-faith remediation record, a draft demand-letter response, a VPAT, and an IRS Form 8826 Disabled Access Credit worksheet. That tax credit is worth up to five thousand dollars for qualifying small businesses and can offset a meaningful portion of remediation costs.
Overlay vs. Real Code Fix: A Direct Comparison
| Factor | Accessibility Overlay | Real Code Remediation |
|---|---|---|
| Fixes underlying source code | No | Yes |
| Accepted by courts as a defense | Generally no | Yes, when documented |
| Can interfere with users' screen readers | Yes, documented cases | No |
| Produces a dated remediation record | No | Yes |
| Satisfies plaintiffs' counsel | Rarely | Yes, when thorough and documented |
Next Step
Run a free, instant scan of your site at wcagdefender.com. The scan costs nothing, requires no account, and gives you a dated, lawsuit-risk baseline you can share with your attorney today. For paid remediation options, see wcagdefender.com/pricing.
Frequently asked questions
How long does a real code fix take?
It depends on the size of your site and the number of barriers found. A small business website with straightforward markup can often have its highest-severity issues remediated within one to two weeks. Larger or more complex sites take longer. What matters legally is that you begin immediately, document each fix with a date, and maintain a remediation timeline. WCAGDefender delivers platform-specific, copy-ready code fixes for Shopify, WordPress, Wix, and Squarespace, which shortens the implementation time significantly.
Will fixing my site after receiving a demand letter protect me from a lawsuit?
Documented, good-faith remediation is your strongest defense, but no tool or service can guarantee you will not be sued. What a thorough, dated remediation record does is demonstrate to a court, a mediator, or plaintiffs' counsel that you took the matter seriously and acted promptly. Courts weigh good-faith effort heavily. Installing an overlay is not considered good-faith remediation by most plaintiffs' attorneys or courts; real code changes with a documented record are.
Does WCAGDefender provide a compliance certificate?
WCAGDefender produces a legal-ready packet that includes an accessibility statement, a good-faith remediation record, a VPAT, a draft demand-letter response, and an IRS Form 8826 Disabled Access Credit worksheet. It does not issue a permanent compliance certificate, because accessibility is an ongoing practice rather than a one-time status. The documentation it produces is designed to serve as evidence of good-faith effort, which is the standard courts and the DOJ actually apply.
Can I just install an overlay like accessiBe or UserWay and tell the plaintiff my site is now compliant?
This approach has repeatedly failed in litigation. Overlays sit on top of your existing code and cannot fix structural barriers. Courts have not accepted them as a defense, and some demand letters now name the overlay itself as an additional barrier. In 2025 the FTC took action against accessiBe over its automated compliance marketing, which further undermines the legal credibility of relying on such tools. Plaintiffs' counsel is specifically looking for evidence of real code changes, not a widget installation.
What is the IRS Form 8826 Disabled Access Credit and can my business claim it?
The Disabled Access Credit under IRS Form 8826 allows eligible small businesses to claim a tax credit of up to five thousand dollars per year for costs incurred to improve accessibility. It covers accessibility consulting and remediation expenses. WCAGDefender includes a completed Form 8826 worksheet in its legal-ready packet. You should confirm eligibility with your tax advisor, but many small businesses undertaking ADA website remediation qualify.
My site is on WordPress (or Shopify, Wix, or Squarespace). Does that affect what can be fixed?
Yes, the platform determines how fixes are implemented. WCAGDefender delivers platform-specific, copy-ready code instructions for WordPress, Shopify, Wix, and Squarespace. The remediation steps for each platform differ, and generic advice that ignores your platform often leads to incorrect implementation. Getting fixes that match your actual platform reduces the chance of introducing new errors while resolving existing ones.