ADA Website Compliance for Small Businesses: The Lawsuit Wave and the Fix

ADA website compliance means your website can be used by people with disabilities: someone using a screen reader can navigate it, someone who cannot use a mouse can operate it from a keyboard, and someone with low vision can read it. There is no government certification for it. In practice, compliance means meeting the Web Content Accessibility Guidelines (WCAG) at level 2.1 AA, because that is the standard courts and the Department of Justice keep pointing to.

Small business owners mostly learn about this from a demand letter. A law firm writes that your website violates the Americans with Disabilities Act, attaches a list of technical failures, and offers to settle. The letter is real, the legal exposure is real, and the fix is more boring and more affordable than the letter makes it sound. This post covers all three.

Does the ADA really apply to my website?

Yes, treat it as settled for practical purposes. Title III of the ADA requires “places of public accommodation” to be accessible, and the Department of Justice has taken the position for years that this covers the websites of businesses open to the public. The DOJ said it plainly in its 2022 web accessibility guidance.

The case most people cite is Robles v. Domino’s Pizza. A blind customer could not order through the website or app with his screen reader. The Ninth Circuit ruled in 2019 that the ADA applied, and the Supreme Court declined to take the case, leaving that ruling standing. Domino’s, with all its legal budget, ended up where every small business ends up: fixing the website.

Courts in different circuits still differ on details, like whether a website needs a connection to a physical location to be covered. Do not build your plan on that distinction. Plaintiffs’ firms know which courts to file in, which is why New York and Florida lead the country in these cases year after year.

One more signal worth knowing: in April 2024 the DOJ finalized a rule requiring state and local government websites to meet WCAG 2.1 AA. That rule covers governments, not private businesses, but it tells you exactly which standard regulators consider the bar.

Why are small businesses the target?

Because the economics work. Digital accessibility lawsuits have run at more than 4,000 per year in the US in recent years, according to UsableNet, which tracks these filings, and that count does not include demand letters that settle before anyone files. A significant share of filings come from a small group of serial plaintiffs working with specialized firms.

The playbook is volume. Automated scans find sites with detectable failures (missing alt text, unlabeled forms, bad contrast). Letters go out. Most recipients settle, typically for four to five figures, because settling costs less than defending. Small businesses are attractive targets precisely because they rarely fight.

The way out of that pool is not legal cleverness. It is being a site the scan does not flag.

What standard do I actually have to meet?

WCAG 2.1 Level AA. It is not written into Title III as a private-business regulation, but it is the standard DOJ settlements reference, the standard the 2024 government rule adopted, and the standard courts treat as the benchmark. (WCAG 2.2 was published in 2023 and adds a few criteria; meeting 2.1 AA puts you nearly all the way there.)

WCAG reads like a technical document, but the level AA failures that show up in lawsuits are a short, repetitive list:

• Images without alt text. A screen reader hits your photo and says “image” with no idea what it shows.
• Buttons and links that do not say what they do. “Click here” and icon-only buttons with no label.
• Forms without labeled fields. The contact form works fine visually and is a wall of anonymous boxes to a screen reader.
• Low color contrast. Light gray text on white backgrounds fails a measurable ratio (4.5:1 for normal text).
• No keyboard access. Menus, popups, or checkout steps that only work with a mouse.
• Missing focus indicators. Keyboard users cannot see where they are on the page.
• Videos without captions.
• Broken heading structure. Headings chosen for font size instead of hierarchy, which is how screen reader users skim a page.

Notice what this list is: craftsmanship, not exotic engineering. A well-built site passes most of it by default. A cheaply assembled one fails most of it by default, which is one more entry in the list of what separates a fair website price from a false economy.

How do I check my site today, for free?

You can get a solid read on your exposure in under an hour, without buying anything:

1. Run WAVE (wave.webaim.org). Paste your homepage URL. It flags missing alt text, contrast failures, and unlabeled forms visually on the page. Run it on your homepage, contact page, and any page where money changes hands.
2. Run Lighthouse. In Chrome, right click, Inspect, Lighthouse tab, run the accessibility audit. It scores the page and lists specific failures with links explaining each fix.
3. Do the keyboard test. Put the mouse away. Using only Tab, Shift+Tab, Enter, and arrow keys, try to use your menu, fill your contact form, and complete whatever your most important action is. If you get stranded, so does anyone who cannot use a mouse.
4. Check your videos and PDFs. No captions on videos and image-only scanned PDFs are both common flags.

Automated tools catch roughly the failures that automated plaintiff scans catch, which makes them a good proxy for lawsuit exposure. They do not catch everything a human audit catches, but a site that passes WAVE, Lighthouse, and the keyboard test has left the easy-target pool.

Are accessibility overlay widgets the fix?

No. Overlays are the widgets that add a floating accessibility button offering font resizing and contrast toggles, sold as one-line-of-code compliance. They do not fix the underlying page structure, screen reader users widely report they make sites harder to use, and they do not stop lawsuits: UsableNet’s tracking consistently finds hundreds of defendants each year that had an overlay installed when they were sued.

If a vendor promises full ADA compliance from a script tag, that promise is the product. The actual fix happens in the site itself: the markup, the forms, the images, the navigation.

What does fixing it cost, and what is the tax credit?

For a typical small business site, remediation is a scoped project: fix the flagged issues page by page, or fold accessibility into a rebuild you already needed. On a small site the work often lands in the hundreds to low thousands of dollars, far below what a single settlement runs.

The part almost nobody tells small business owners: the IRS pays for half. The Disabled Access Credit (IRS Form 8826, Section 44) gives businesses with $1 million or less in revenue or 30 or fewer full-time employees a tax credit of 50% of eligible accessibility expenditures between $250 and $10,250 in a year, up to $5,000. Website accessibility work performed to comply with the ADA can qualify. Confirm the specifics with your tax preparer, but do not leave this on the table.

Frequently asked questions

Can my small business really be sued over its website?

Yes. Company size does not exempt you from Title III, and filing data shows small businesses are frequent targets because they usually settle. Restaurants, medical practices, law firms, and e-commerce shops appear constantly in the filings.

Is there an official ADA certification for websites?

No. Nobody can sell you a certificate that immunizes you. Compliance is a state your site is in (meeting WCAG 2.1 AA), not a document you hang on the wall, and it needs rechecking whenever the site changes.

What should I do if I already received a demand letter?

Do not ignore it and do not pay it on day one. Talk to a lawyer with ADA Title III experience before responding, and start fixing the listed issues immediately, because remediation both limits ongoing exposure and matters in any negotiation. What you should not do is fix nothing and settle, which leaves you in the target pool for the next letter.

Does WCAG compliance help my Google ranking too?

Largely, yes. Alt text, heading structure, labeled links, and fast clean markup are the same things search engines reward. Accessibility work and SEO work overlap heavily, which is part of why it belongs in the build, not bolted on after.

Where to start

Run WAVE and the keyboard test on your three most important pages this week. That tells you in an hour whether you have a small punch list or a real project, and either answer is better than finding out from a law firm.

Every site I build meets WCAG 2.1 AA from day one, because accessibility is part of building a site correctly, not an add-on. If your current site failed the tests above, or you are planning a rebuild and want compliance included instead of retrofitted, my websites page shows exactly what I build and what it costs.

---

Jose Lugo is a CISSP-certified security engineer who builds fast, secure, accessible websites for small businesses at josecustom.ai.