What to Do If Your Business Gets an Accessibility Demand Letter

Treat an accessibility demand letter as a business risk that requires legal counsel, documentation, and code-level remediation on a timeline. Do not ignore it. Do not install an overlay widget and assume you are protected. Document your site's current state immediately, bring in a qualified attorney, and begin fixing the underlying barriers with dated records of each step.

Why is ignoring the letter the worst option?

A demand letter is not a court order, but it is often the first step before a lawsuit (webability.io). If you do not reply to the letter, you will probably be sued within 90 days (acquia.com). The letter typically names specific accessibility barriers, requests remediation, and sets a response deadline. Most ADA demand letters allow 30 to 60 days (audioeye.com).

Even if the claim seems unfair or exaggerated, ignoring it signals that you are not taking the complaint seriously. Courts and plaintiffs look at whether you are actively addressing accessibility, and silence works against you.

Do not install an overlay widget as your fix

When panic sets in, many businesses rush to install an accessibility overlay, a JavaScript widget that promises instant compliance. Overlay widgets do not make a website ADA compliant and won't hold up against a demand letter or lawsuit (accessibility.works). Accessibility overlay widgets routinely make websites harder for assistive technology users to navigate, and public legal filings show that installing one often increases your likelihood of receiving an ADA demand letter rather than preventing it (laymance.com).

The FTC fined accessiBe $1 million in January 2025 for claiming its overlay could make any website WCAG-compliant. More than 5,000 digital accessibility lawsuits were filed in the U.S. in 2025, and roughly 1,400 of them targeted sites that already had an accessibility widget installed (corea11y.com). Overlays do not fix the underlying HTML, and screen readers interact with the source code, not the JavaScript layer added after the page loads.

What should you do in the first 72 hours?

In the first 48 hours after receiving an ADA demand letter, do not ignore it, do not admit liability, preserve the letter and everything in it, document your website's current accessibility state, and contact legal counsel before you respond.

Take screenshots, save any existing scan results or audit records, and run a fresh accessibility audit so you have a timestamped record. Documenting your state now, before fixes, is one of the most valuable and most overlooked steps in the first 48 hours. This baseline establishes where you started and supports your legal position. The free AI-visibility check (/check) can give you a snapshot of how your site appears to automated scanning, though a full WCAG audit will require both automated and manual testing.

Engage an attorney experienced in ADA and digital accessibility matters before you respond to the sender. Digital accessibility law is still evolving and varies by state, so professional counsel matters here. Don't respond informally or admit fault before getting legal input (accessibilitychecker.org).

Start real remediation with dates and evidence

Courts and plaintiffs look at whether you are actively addressing accessibility. The sooner you begin scanning for issues and fixing them against WCAG 2.1 AA, the stronger your position of good-faith effort becomes. WCAG 2.1 Level AA includes 50 success criteria: all 30 Level A criteria and all 20 Level AA criteria. Most laws currently name WCAG 2.1 AA, so it is the minimum target.

Once fixes are made, document everything: before-and-after screenshots, code changes, audit results, and internal emails. These can be valuable if the issue escalates or comes up again. Real remediation means editing the source code to remove keyboard traps, add missing alt text, label form fields, fix color contrast, and ensure that users relying on assistive technology can complete the same tasks as everyone else.

A remediation plan with specific dates shows you are moving forward, not stalling. Note which issues you are addressing first, who is responsible for each fix, and when you expect to complete them. If an issue cannot be resolved immediately, document why and set a realistic timeline for fixing it.

How ActiScore helps with the evidence trail

ActiScore's pricing (/pricing) includes accessibility scoring as one of 10 categories audited on every scan. Each scan produces a timestamped report showing exactly which WCAG barriers exist, which ones have been resolved since the last scan, and where the remaining work is. That dated audit trail is the kind of documentation that demonstrates good-faith effort, and it gives your attorney the technical evidence to support your response.

The record matters because settlement discussions and court proceedings depend on whether you can show you took the complaint seriously and moved to fix the problems. A sequence of scans with improving scores, paired with developer commit logs and dated screenshots, builds that record.

What the letter does and does not establish

The demand letter is an allegation, not proof. A close look at the claims may also reveal whether the demand letter is legitimate. For example, an ADA demand letter might identify empty (or null) alternative text for images as a barrier to access. Verify the claims with your own audit. The issues listed in the letter may reflect only what one user encountered on one page, not every barrier across your site.

It's possible your website, app, or other digital experience contains accessibility issues that are not named in the demand letter. A full audit identifies the complete scope, which is what you need to fix the site properly and reduce the risk of receiving another letter months later.

Timelines for remediation vary by complexity

Small sites with straightforward issues can often reach WCAG 2.1 AA within three to six months. Larger sites, sites with complex applications, or sites with thousands of pages can take 12 to 24 months depending on the functionality involved. That timeline matters when your attorney negotiates a response or settlement. Claiming you will fix everything in two weeks when you have 500 pages and a custom checkout flow is not credible. A realistic timeline with milestones, backed by evidence that work is already underway, is.

If your site is large or technically complex, prioritize the issues that prevent users from completing key tasks: form submission, checkout, account login, and navigation. Fix those first, document the fixes, and continue working through the rest of the audit in order of user impact.

What compliance evidence looks like in procurement and governance

Organizations with procurement requirements or governance controls already understand that compliance is not a checkbox, it is a process backed by evidence. The same principle applies here. You need to show what you tested, what you found, what you fixed, when you fixed it, and how you are maintaining accessibility going forward. The guide (/guide) explains how continuous monitoring fits into that process.

Accessibility is not a one-time project. New content, new features, and changes to your CMS or framework can introduce new barriers. Ongoing scans catch those issues before they accumulate into another demand letter. The businesses that avoid repeat complaints are the ones that treat accessibility as part of their development workflow, not an emergency response.