Served with an ADA website lawsuit: first steps for a small business
Short answer: Find the response deadline on the summons, contact an attorney who handles ADA Title III cases, notify your insurer, preserve the current site, and do not ignore the complaint. Then get a dated audit and start fixing the cited barriers. This is not legal advice.
Being served with a federal complaint is stressful. It is also a situation with a clear order of operations. This guide walks through the practical first steps for a small business owner or the developer supporting one, in the days after service.
This guide is general information, not legal advice. Proofofaccess.com is not a law firm. Questions about your specific case belong with an attorney.
The first 24 hours: protect your position
1. Read the summons and note the response deadline
The summons is the document that tells you how long you have to respond and to whom. Find that date, write it down, and put it on every calendar you use. Do not rely on a number you read elsewhere, including in this guide. Deadlines depend on the court, the type of case, and how and when you were served, so the summons and your attorney are the sources to trust.
Also note:
- The court and case number
- The names of the plaintiff and any other defendants
- The date and method by which you were served
- Who in your business received the papers
2. Do not ignore it
A complaint does not go away if left unanswered. Missing a response deadline can lead to consequences that are harder to reverse than the original problem. Even if you believe the claim is weak, or the site is managed by a third party, get professional help before the deadline arrives.
3. Contact an attorney
Reach out to an attorney as soon as you can, ideally one who has handled ADA Title III matters or web accessibility claims. Experience with these cases matters because they follow recognizable patterns. If you do not already have a lawyer, your state or local bar association may offer a referral service.
Things worth having ready for the first call:
- A copy of the summons and complaint
- Any earlier demand letter or correspondence (see Got an ADA website demand letter?)
- Who built and who maintains your website
- Your hosting, platform, and any plugins or third-party widgets in use
- Any prior accessibility work, audits, or statements you have published
4. Notify your insurer
Check your business policies, such as general liability, and any other coverage you carry, and consider notifying the insurer promptly. Policies often have notice requirements, and whether a given policy covers this kind of claim varies widely. Ask your attorney or broker to help you read the terms. Late notice can create avoidable problems, so it is better to ask early.
5. Preserve the current site
Your website as it exists now may be relevant evidence. Before you change anything:
- Take a full backup of the site, including files and database
- Save the current version of the pages named in the complaint
- Record the date and keep the backup somewhere separate from the live site
- Preserve relevant emails, tickets, and messages about the site and accessibility
- Ask your attorney whether any document retention steps apply to your situation
Preserving the site does not mean freezing it forever. It means keeping a record of what it looked like when you were served, so that you can still make improvements.
What a complaint usually alleges
Complaints about website accessibility differ, but many describe barriers that a person using assistive technology would have run into. Typical allegations include:
- Screen reader barriers: content or controls that a screen reader cannot read or operate
- Missing alt text: images, including product photos and buttons, with no text alternative (WCAG 1.1.1)
- Unlabeled buttons and form fields: controls announced as just "button" or "edit text" (WCAG 4.1.2, WCAG 3.3.2)
- Keyboard problems: menus, carousels, or checkout steps that cannot be used without a mouse (WCAG 2.1.1)
- Low color contrast that makes text hard to read (WCAG 1.4.3)
- Unclear links such as repeated "click here" (WCAG 2.4.4)
A complaint states the plaintiff's allegations. It is not a finding that those things are true or that any legal violation occurred. Whether a particular barrier creates liability is a legal question for your attorney. For background on who brings these cases and why, see ADA website lawsuits explained.
The next several days: understand and document the site
6. Get a dated audit of the current state
Once your attorney is involved, a dated accessibility audit gives you a factual picture of what the site looks like today. An automated WCAG 2.1 AA scan will not find everything, since some issues need human judgment, but it can quickly show which cited barriers still exist and where else similar problems appear.
The date matters. A dated record shows what was found and when, and lets you show later progress against it. See why a dated accessibility audit record matters. Share the results with your attorney before deciding how to use them.
7. Match the complaint to what you find
Go through the complaint and list each barrier it names. For each one, note:
| Item | What to record |
|---|---|
| Page or feature cited | URL and a description |
| Barrier alleged | Plain-language summary |
| Present today? | Yes, no, or unsure, with a date |
| Likely cause | Theme, plugin, template, content, third party |
| Owner | Who will fix it |
This table becomes your working fix list. It also helps your attorney understand the technical picture.
8. Start fixing the cited barriers
Making the site more accessible is generally worth doing regardless of how the case proceeds, because it helps real visitors. Discuss timing and documentation with your attorney, then start with the barriers named in the complaint, followed by the highest-traffic and highest-risk paths such as navigation, search, product pages, forms, and checkout.
Many common fixes are small. For example, a button that contains only an icon needs an accessible name:
<!-- Before: announced only as "button" -->
<button><svg aria-hidden="true">...</svg></button>
<!-- After: announced as "Open cart" -->
<button aria-label="Open cart"><svg aria-hidden="true">...</svg></button>
And an informative image needs a short, meaningful text alternative:
<img src="blue-mug.jpg" alt="Blue ceramic mug with a wide handle">
Useful references while you work:
- WCAG 2.1 AA checklist for business websites
- How to write alt text for product images
- How to check and fix color contrast across your whole site
- Screen reader testing basics
- WordPress accessibility: themes, plugins and what to check
- WCAG fix guides for individual success criteria
9. Be cautious with quick fixes
Overlay widgets that promise instant accessibility are sometimes considered by site owners in this situation. Courts and plaintiffs have not treated them as a reliable answer, and they do not replace fixing the underlying code. Read Do accessibility overlay widgets prevent ADA lawsuits? before relying on one.
10. Keep records as you go
Keep a simple log of each change: what was changed, who changed it, when, and how it was checked. Re-test after fixes, ideally with both automated tools and a quick screen reader and keyboard pass. No tool or process can promise that a site is free of every barrier, so the goal is steady, documented improvement.
What not to do
- Do not ignore the deadline on the summons
- Do not delete pages, posts, or past versions of the site
- Do not contact the plaintiff directly without your attorney's guidance
- Do not post public statements about the case
- Do not assume a plugin, overlay, or accessibility statement resolves the matter
Where to learn more
The U.S. Department of Justice publishes information about the ADA at ada.gov, and the W3C explains the standard most audits are measured against at w3.org. You can also browse the federal ADA website lawsuit tracker for general context, and all guides for more practical walkthroughs. When you are ready to see where your site stands, run a free scan to get a dated starting point for your fix list.
Frequently asked questions
How long do I have to respond to a federal complaint?
The summons states your response deadline, and that is the date to follow. It depends on the court, the type of case, and how you were served, so no single number applies to everyone. Note it immediately and confirm it with your attorney.
Should I fix my website before I talk to an attorney?
Contact an attorney first, or at least before making major changes. Preserve a backup of the current site so that a record of its state when you were served remains. Your attorney can then advise on how to fix and document improvements.
Does fixing the cited barriers end the lawsuit?
Not automatically. Remediation is useful and often a sensible step, but how it affects a case is a legal question that varies by situation and court. Ask your attorney how your fixes should be timed and documented.
Will an accessibility overlay or plugin protect me?
Overlays and plugins do not guarantee protection, and they do not substitute for fixing the underlying code. Many accessibility problems need changes to markup, content, or design. Discuss any tool you are considering with your attorney.
What is a dated audit, and why get one?
A dated audit is a recorded check of your site against a standard such as WCAG 2.1 AA, with a clear date on the results. It shows what barriers existed when it was run and makes later improvements easier to demonstrate. It does not by itself make a site compliant, and it is not a substitute for legal advice.
Related
- Got an ADA website demand letter? What to do in the first two weeks
- ADA website lawsuits explained: who sues, why, and what the law requires
- Why a dated accessibility audit record matters
- WCAG 2.1 AA checklist for business websites
Proof of Access provides technical accessibility assessments. We are not a law firm and nothing on this page is legal advice. If you have received a demand letter or a lawsuit, talk to an attorney.