YOU JUST GOT SERVED WITH AN ADA WEBSITE DEMAND LETTER.

Here’s What Happens Next — And How to Stop It From Coming

A guide for business owners who can’t afford to ignore website accessibility any longer

The email or letter arrived without warning. Maybe it came through your registered agent. Maybe it landed directly in your inbox. Either way, the message was the same: your website allegedly violates the Americans with Disabilities Act, and if you do not respond — quickly — you may be facing a federal lawsuit.  Unfortunately, 96% of all websites do violate the ADA’s requirements.  You see, ADA accessibility requirements don’t only apply to your physical office; they apply to your website, which is your digital welcome mat.

Thousands and thousands of these demand letters are sent every year to businesses of every size, in every industry, in every state. In 2023 alone, more than 4,600 federal ADA website lawsuits were filed, a number that has grown substantially year over year since 2017. Many thousands more demand letters are sent and settled quietly before litigation ever begins.  ADA website violations are low hanging fruit for industrious attorneys looking for a steady cashflow. 

What you do in the next few days and weeks matters enormously. So does what you do going forward.

In this guide, I’m going to walk you through exactly what is happening, what the legal landscape looks like, how these cases are built against businesses like yours, and most importantly — how to proactively fix the problem, not just paper over it. I spent 25 years as an attorney, 15 of those as a litigator. I have been in that room. I know what serial plaintiffs’ counsel is looking for, and I know what a real defense requires.

Let’s get into it.

 Part 1: Understanding What Just Landed on Your Doorstep

What Is an ADA Website Demand Letter, Exactly?

An ADA website demand letter is typically a pre-litigation notice sent by a plaintiff’s attorney alleging that your website fails to comply with the accessibility requirements of Title III of the Americans with Disabilities Act. Title III prohibits discrimination by places of public accommodation — and courts have broadly held that business websites qualify as places of public accommodation under the statute.  For those of you who live in States that have their own Civil Rights and Human Rights Statutes, like we do in Washington State, these statutes are as broad or even broader than the ADA.

The letter will typically assert that your site cannot be used by someone who is blind, visually impaired, deaf, hard of hearing, or has some other disability. It will cite specific features or pages that allegedly present barriers. It will threaten litigation in federal court. And it will usually offer you the opportunity to resolve the matter — for a fee, a settlement, or a compliance commitment, or some combination of all three.  But, let’s get down to it, you will most likely have to pay money to resolve this matter.

Who Sends These Letters?

A relatively small number of plaintiffs’ law firms account for the majority of ADA website demand letters and lawsuits. Some of these firms operate what can only be described as a litigation volume business: identifying non-compliant websites at scale using automated scanning tools, preparing templated complaints and demand letters, and sending them in bulk to businesses across the country.

The plaintiffs named in these suits are often individuals with disabilities who work with these firms on an ongoing basis, lending their names to dozens or even hundreds of cases per year. Courts have taken note of this pattern, and some have scrutinized cases involving serial plaintiffs more closely. But the lawsuits are real, the exposure is real, and dismissal is never guaranteed.

Disturbingly, the legal resources on the Internet now make it quite easy for non-lawyers, those representing themselves pro se, to send the demand letters out.  Truthfully, there is a lot of money to be made either for an industrious per se litigant or an industrious attorney.

This is not a scam. This is not spam. This is a legitimate legal demand that deserves a serious, informed response.

What Are They Claiming You Violated?

While the ADA itself does not specify a technical standard for website accessibility, courts and the Department of Justice have increasingly looked to the Web Content Accessibility Guidelines — known as WCAG — as the benchmark for what an accessible website looks like. The most commonly referenced version is WCAG 2.1 at Level AA conformance, though WCAG 2.2 was published in late 2023 and represents the current standard.

WCAG is organized around four foundational principles that can be recalled using the acronym, POUR. A website must be:

•        Perceivable —information and interface components must be presentable to users in ways they can perceive, even if they cannot see or hear in the conventional sense.

•        Operable — meaning that interface components and navigation must be operable by users who cannot use a mouse and must rely on keyboard navigation or assistive technologies like screen readers.

•        Understandable — meaning that information and the operation of the interface must be understandable, with clear language, predictable behavior, and helpful error identification.

•        Robust — meaning that content must be robust enough to be reliably interpreted by a wide variety of user agents, including current and future assistive technologies.

Beneath these four principles are 78 specific success criteria across three levels: A (the most critical), AA (the broadly accepted commercial standard), and AAA (enhanced, often aspirational). A demand letter may cite anywhere from a handful to dozens of specific violations.

Common allegations include missing alternative text on images, videos without captions, forms that cannot be navigated by keyboard, color contrast ratios that fail readability thresholds, and pop-ups or carousels that trap keyboard users or screen reader users in endless loops.

Truthfully, most businesses, professional, retail, or otherwise, don’t know about and don’t understand that this is a website development level issue.  It’s about how you need to set-up the back working room of your website so that your website is then accessible to every kind of disabled person.

Part 2: The Legal Landscape — What the Courts Have Said

Is Your Website Really Covered by the ADA?

This is the first question most business owners ask. The short answer: almost certainly yes, if you operate any kind of business that serves the public.

Title III of the ADA requires that places of public accommodation provide equal access to individuals with disabilities. The statute includes an extensive list of covered entities — retail stores, restaurants, hotels, theaters, service establishments, and many more. Courts have consistently held that businesses with a physical presence that also operate websites must make those websites accessible. More recently, courts have extended this reasoning to businesses that operate exclusively or primarily online. 

The Ninth Circuit and Eleventh Circuit have been particularly active in this area. The Ninth Circuit’s decision in Robles v. Domino’s Pizza — holding that Domino’s app and website must comply with the ADA — remains one of the most cited cases in this field. The Department of Justice has also weighed in explicitly, issuing guidance in 2022 affirming that the ADA applies to websites and directing covered entities to conform to WCAG 2.1 Level AA.

There is no federal circuit that has categorically exempted websites from ADA coverage. Some defendants have raised due process arguments based on a lack of clear notice as to the specific technical standard required, but courts have generally rejected these arguments or found them insufficient to overcome the underlying accessibility obligations.

What Does the Litigation Process Actually Look Like?

If you do not respond to a demand letter — or if negotiations break down — the next step is typically the filing of a complaint in federal district court. ADA Title III cases are filed in federal court because the ADA is a federal statute.

The complaint will allege that your website presents barriers to access for the plaintiff based on their disability, that they encountered, specific barriers, on specific dates, and that they intend to return to the site but are deterred from doing so because of the inaccessibility. This “intent to return” allegation is critical because it establishes standing — the plaintiff’s right to bring the suit in the first place.

ADA Title III cases do not allow for the recovery of monetary damages by private plaintiffs. What plaintiffs can recover is injunctive relief — a court order requiring you to fix your website — and, critically, attorney’s fees and costs. This is why the economics of these cases favor plaintiffs’ attorneys: they can recover their fees even on small cases, which makes the litigation model sustainable at scale.

Settlements in ADA website cases typically involve a combination of some monetary payment (which may be characterized as a litigation cost reimbursement or a settlement of attorneys’ fees), a commitment to remediate the website within a defined timeframe, and sometimes ongoing monitoring obligations. Settlement amounts vary widely — from a few thousand dollars on smaller cases to six figures on larger, more complex litigation — but the average nuisance settlement for a smaller business has historically ranged from $10,000 to $30,000, with legal fees on top.

The DOJ Has Entered the Chat

In March 2022, the Department of Justice issued formal guidance on web accessibility, making clear that it interprets Title III to require accessible websites and that it views WCAG 2.1 Level AA as the applicable standard. In April 2024, the DOJ went further, publishing a final rule under Title II of the ADA — which covers state and local government entities — that codifies WCAG 2.1 Level AA into regulation.

While the Title II rule does not directly apply to private businesses covered by Title III, it is a powerful signal of regulatory direction. It establishes WCAG 2.1 Level AA as a recognized federal standard and removes any remaining ambiguity about what “accessible” means in the context of digital properties. Businesses that ignore this signal do so at increasing risk.

 Part 3: What Happens If You Ignore It

The Temptation to Do Nothing

I understand the temptation. You are busy running a business. The letter sounds like a shakedown. You have never had a disabled customer complain. You may have even heard that these cases go away on their own.

Some of them do. But many do not. And the ones that do not go away get significantly more expensive the longer you wait.

Once a complaint is filed, you will need to retain counsel to respond. You will face discovery obligations. You may need to engage an expert witness to evaluate your site. The litigation timeline stretches from months to years. Even if you ultimately prevail — which is not guaranteed — you will have spent far more defending the case than it would have cost to remediate your website in the first place.

The Compounding Risk: Serial Plaintiffs and Re-Filing

Here is something that many businesses do not realize until it is too late: settling with one plaintiff does not insulate you from the next one.

If your website remains inaccessible after you settle a case — or after you remediate it inadequately — a different plaintiff represented by a different firm can sue you again. And again. This is not a hypothetical. It happens regularly to businesses that treat accessibility as a legal problem to be settled rather than a technical problem to be solved.

The only durable defense against ADA website litigation is a genuinely accessible website. Not a widget. Not a settlement. An accessible website.

The Overlay Widget Problem

If you have already been sued or received a demand letter, there is a reasonable chance that someone has already pitched you on an accessibility overlay widget. These are JavaScript plugins that you add to your site and that are marketed as instant accessibility solutions — they claim to fix your site automatically, without the need for remediation.

I want to be blunt about this: the accessibility and legal communities have reached a broad consensus that overlay widgets do not reliably produce WCAG-conformant websites, and that their use has not prevented litigation. In fact, plaintiffs’ attorneys are well aware of overlays and know how to demonstrate that they fail to correct underlying code-level violations.

Several prominent organizations representing the blind and visually impaired community have published formal position statements opposing overlays. Courts have declined to dismiss cases against businesses solely on the basis that an overlay was in use. And the overlay vendors’ own terms of service frequently disclaim any warranty of legal compliance.

An overlay is not a solution. It is a liability. 

Part 4: How Violations Are Found — The Anatomy of a WCAG Audit

Automated Scanning: Fast, But Incomplete

The firms that send demand letters at volume typically begin with automated scanning tools. These tools crawl your website and flag potential WCAG violations based on rules that can be checked programmatically: missing alt text, insufficient color contrast, absent form labels, missing language declarations, and the like.

Automated tools are valuable, but they are fundamentally limited. Current research suggests that automated tools can detect somewhere between 30 and 40 percent of WCAG violations. The remainder require human evaluation. A site that passes an automated scan is not a compliant site — it is simply a site with fewer obvious violations.

The demand letters that arrive in your inbox are often based on automated scans. This means that if you remediate only the issues flagged in the letter, you may be fixing the violations that were easy to find while leaving the harder-to-find violations in place — setting yourself up for another demand letter from a more thorough plaintiff.

Manual Testing: The Gold Standard

A comprehensive WCAG audit goes well beyond automated scanning. Manual testing involves a trained evaluator navigating the site using the tools and technologies that people with disabilities actually use: screen readers like JAWS, NVDA, and VoiceOver; keyboard-only navigation; browser zoom functionality; and more.

Manual testing uncovers violations that no automated tool can detect such as focus order problems that make navigation confusing or disorienting, interactive elements that work with a mouse but fail with a keyboard, content that is announced incorrectly or incomprehensibly by a screen reader, and time-limited interactions that create barriers for users with cognitive or motor disabilities.

A thorough audit also includes evaluation of documents linked from your site — PDFs are a major source of accessibility violations that many businesses overlook entirely.

What a Real Audit Looks Like

A professional WCAG audit for a business website will typically include the following components:

•        An automated scan of all major site templates and key user pathways using industry-standard tools.

•        Manual keyboard navigation testing across the entire site, verifying that every interactive element — menus, forms, buttons, carousels, modals, accordions — can be accessed and operated without a mouse.

•        Screen reader testing using at least two screen reader and browser combinations (commonly NVDA with Chrome and JAWS with Internet Explorer or Edge, plus VoiceOver with Safari on iOS).

•        Color contrast analysis for all text and UI components.

•        Review of all multimedia content for captions, audio descriptions, and transcripts.

•        Document accessibility review for linked PDFs and other downloadable materials.

•        A detailed audit report mapping each identified violation to the specific WCAG success criterion it violates, with severity ratings, screenshots, and remediation guidance.

This is the foundation. Everything else — remediation, monitoring, legal defense — builds on the quality of this initial diagnosis.

 Part 5: Remediating Violations the Right Way

Remediation Is a Development Project, Not a Checkbox

One of the most common misconceptions about WCAG compliance is that it can be achieved quickly and cheaply by making a few surface-level changes to a website. For some sites with limited violations, remediation is relatively straightforward. For others — particularly older sites built without accessibility in mind, or sites with complex interactive features — remediation is a substantial development effort.

Effective remediation requires access to your site’s source code and the ability to modify it. This means your development team — whether in-house or an agency — needs to understand not just what to fix, but how to fix it correctly in the context of your specific platform, framework, and content management system.

Common Violations and How They Are Fixed

Missing or Inadequate Alternative Text

Every non-decorative image on your site needs a text alternative — an alt attribute in the HTML that describes the image to someone who cannot see it. The fix sounds simple, but doing it well requires judgment: alt text should be descriptive and meaningful, not generic (“image” or “photo”) and not stuffed with keywords. Decorative images should have empty alt attributes (alt="") so that screen readers skip them rather than announcing them as unlabeled images.

Keyboard Navigation Failures

Every interactive element on your site — every link, button, form field, dropdown menu, modal window, and custom widget — must be reachable and operable using only the Tab, Enter, Space, and arrow keys. Common failure modes include custom JavaScript components that intercept keyboard events, modal dialogs that do not trap focus correctly, and dropdown menus that close before a keyboard user can reach them. These require code-level fixes, not cosmetic changes.

Color Contrast

WCAG 2.1 Level AA requires a color contrast ratio of at least 4.5:1 between text and its background for normal-sized text, and 3:1 for large text. Many websites fail this criterion due to design choices — light gray text on white backgrounds, or colored text over colored backgrounds — that look elegant but are functionally unreadable for users with low vision. Fixing contrast issues requires coordination between your design and development teams.

Form Accessibility

Web forms are among the most commonly violated and most consequential areas of WCAG compliance. Every form field must have a programmatically associated label. Error messages must be descriptive and linked to the field that caused the error. Required fields must be indicated in a way that does not rely solely on color. Auto-complete attributes should be provided for common personal information fields. Forms that fail these requirements create real barriers for screen reader users trying to complete transactions, contact your business, or sign up for your services.

Video and Multimedia

Any video on your site that contains spoken dialogue or meaningful audio information must have synchronized captions. Videos that are primarily visual — like silent product demonstrations — need audio descriptions. Live video streams need real-time captions. This is one of the areas where small and medium businesses are most frequently caught off guard, particularly if they have embedded YouTube videos where they do not control the captioning.

Prioritizing the Remediation Roadmap

Not all violations are equal. A well-structured remediation plan prioritizes violations by their impact on users and their likelihood of driving litigation. Critical violations — those that make core site functionality completely inaccessible to users with certain disabilities — should be addressed first. Lower-severity issues can be addressed in subsequent phases.

A realistic remediation timeline for a typical small to medium business website ranges from four to twelve weeks, depending on the number and severity of violations, the complexity of the site, and the capacity of the development team. During that period, it is reasonable to document your remediation plan in case you receive a follow-up from plaintiffs’ counsel — courts and opposing counsel do give credit for documented, good-faith remediation efforts.

Part 6: Monitoring — Why This Is Never a One-Time Fix

The Regression Problem

Here is a reality that most accessibility vendors do not emphasize enough: websites change constantly. New pages are added. Content is updated. Plugins are installed. Templates are modified. Themes are upgraded. Third-party scripts are swapped in and out. Every one of these changes is an opportunity to introduce new accessibility violations.

A website that achieves full WCAG conformance today will not maintain it automatically. Without an ongoing monitoring program, regression is inevitable. And regression creates renewed legal exposure.

What an Ongoing Monitoring Program Looks Like

Effective accessibility monitoring involves several complementary components:

•        Automated scanning on a scheduled basis — at minimum monthly, ideally more frequently for sites that are updated regularly — to catch newly introduced violations before they become entrenched.

•        Integration of accessibility testing into your development workflow, so that new features and content go through accessibility review before they are published, not after.

•        Periodic manual audits — at least annually for stable sites, more frequently for high-traffic or frequently updated sites — to catch the manual-only violations that automated tools miss.

•        A documented accessibility policy and feedback mechanism on your website, so that users with disabilities can report barriers they encounter. This is both a best practice and a signal of good faith.

•        Accessibility statements that accurately describe your site’s current conformance level, known limitations, and contact information for accessibility support.

The Feedback Loop: From Monitoring Back to Remediation

Monitoring is not the end of the process — it is the beginning of the next cycle. When monitoring detects new violations, those violations need to flow back into a remediation queue with clear ownership and timelines. This closed loop — audit, remediate, monitor, detect, remediate again — is what genuine accessibility management looks like in practice.

Businesses that have this system in place are in a fundamentally different position when a demand letter arrives. They can demonstrate to plaintiffs’ counsel, and if necessary to a court, that they have an active, documented, good-faith compliance program. This is not a guarantee of dismissal, but it is a powerful mitigating factor.

Part 7: What to Do Right Now

If You Have Already Received a Demand Letter

First: do not ignore it. Do not forward it to your web developer and assume the problem will be handled. Do not call the plaintiff’s attorney without having counsel of your own in place.

The demand letter has a response deadline. Failing to respond by that deadline — or failing to respond substantively — will almost certainly result in a complaint being filed. Once litigation begins, your costs increase dramatically and your options narrow.

Second: retain counsel who has experience with ADA Title III website cases. This is a specialized area of law. General business litigation counsel may not be familiar with the technical dimensions of WCAG compliance or the litigation dynamics of these cases. The right attorney will know which plaintiffs’ firms are serial litigators, what their usual settlement demands look like, and what a realistic defense or resolution strategy is.

Third: commission a professional accessibility audit immediately. Your counsel will need to understand what violations actually exist on your site in order to assess your exposure and advise on strategy. An audit also begins building the record of a good-faith remediation effort, which matters both in settlement negotiations and in litigation.

If You Have Not Yet Received a Demand Letter

Consider yourself fortunate, and do not wait for one to arrive.

The demand letter volume shows no sign of declining. The tools that plaintiffs’ firms use to identify non-compliant websites are increasingly sophisticated and increasingly affordable. If your website has accessibility violations — and the overwhelming majority of websites do — it is a matter of when, not if, someone finds them.

The most cost-effective path to compliance is always proactive remediation: audit your site, fix the violations, put monitoring in place, and maintain compliance going forward. The cost of proactive remediation is a fraction of the cost of litigation or even a negotiated settlement.

It is also worth noting that accessibility is not only a legal obligation — it is good business. An estimated one in four American adults lives with some form of disability. Making your website accessible is not a concession to litigation pressure; it is an expansion of your addressable market.

Part 8: What to Look for in an Accessibility Partner

Not all accessibility vendors are equal. When evaluating an accessibility partner, here are the questions you should ask:

•        Do they perform manual testing, or only automated scanning? Any vendor that relies exclusively on automated tools is offering you an incomplete and legally insufficient audit.

•        Do they have experience working with businesses that have received ADA demand letters or been involved in litigation? The legal context matters, and your vendor should understand it.

•        Can they provide a detailed written audit report that maps violations to specific WCAG success criteria? A vague or summary report will not serve you well in a legal context.

•        Do they offer ongoing monitoring, or only a one-time audit? Point-in-time compliance is not durable compliance.

•        What is their remediation support model? Do they work with your development team, or do they expect you to figure out how to implement their findings on your own?

•        Do they carry professional liability insurance? This is a sign of a mature, professional operation.

You should also be cautious of vendors who promise immediate, complete compliance without understanding your site. Genuine accessibility is a process, not a product. Any vendor who tells you they can make your site fully compliant in 48 hours without touching the underlying code is selling you something that will not hold up to scrutiny.

Conclusion: This Is a Legal Problem That Has a Technical Solution

ADA website accessibility compliance sits at the intersection of law and technology in a way that most businesses are not equipped to navigate alone. The demand letters are real. The litigation exposure is real. The violations on your website — most likely — are real.

But this is a solvable problem. A proper audit will tell you exactly what is wrong. A competent development team can fix it. A monitoring program will keep it fixed. And a documented compliance program will put you in the strongest possible position, whether you are responding to a demand letter, defending litigation, or simply trying to run a business that treats all of its customers fairly.

I built this practice because I spent 25 years watching businesses face legal exposure that could have been avoided with better information and better preparation. Website accessibility is no different. The information exists. The tools exist. The process exists.

You just need to start.

Ready to find out where your website stands?

We offer professional WCAG audits, guided remediation support, and ongoing monitoring programs designed for businesses that want real compliance, not a widget and a prayer. Contact us to schedule a consultation.