Is Your Website ADA Compliant? The Small-Business Owner's 2026 Guide (and the 72-Hour Demand Letter Playbook)

Here is a question almost no small-business owner can answer about their own website: is it ADA compliant?

Not "does it look nice." Not "does it load fast." Can a blind customer actually buy from you on it?

If you just felt a flicker of doubt, keep reading. In 2025, more than 5,000 digital accessibility lawsuits were filed in the U.S. — and the majority of the businesses targeted had under $50 million in revenue. These aren't Fortune 500 cases. They're local shops, restaurants, clinics, and online stores. Businesses that look a lot like yours.

This is not a legal lecture. It's a builder's guide: what the law actually requires, the six failures behind 96% of flagged problems, what fixes really cost, and exactly what to do if a demand letter ever lands in your inbox.

Key takeaways

• If the public can buy, book, or contact you through your website, the ADA applies to it — there is no small-business exemption.
• "ADA compliant" means meeting WCAG 2.1 Level AA, the standard U.S. courts use. Per the WebAIM Million 2026 audit, 95.9% of the web's top home pages fail it.
• The $49 "accessibility widget" doesn't fix anything — sites running overlays get sued anyway, and the FTC fined accessiBe $1 million for claiming otherwise.
• Six machine-detectable failures account for 96% of all flagged errors, and most are fixable this week.
• If a demand letter arrives, you have a playbook — and panic-signing is the worst move on it.

The short answer: yes, the ADA almost certainly applies to your website

The Americans with Disabilities Act was signed in 1990, before the commercial web existed. For 35 years, courts have been closing that gap case by case — and the dominant reading today is simple: if your website is how the public buys from you, books with you, or gets information from you, it's part of your public accommodation. That falls under Title III of the ADA.

Three things owners get wrong about this:

1. "There's no specific regulation for private websites." True — and useless as a defense. Courts have overwhelmingly adopted WCAG 2.1 Level AA as the working benchmark, and consent decrees hold defendants to it. The lack of a codified rule never stopped the lawsuits.
2. "We're too small to be a target." There is no small-business exemption — the 15-employee threshold you may have heard about applies only to employment rules, not to public accommodations. Federal court data shows companies under $50M in revenue were 68% of defendants in the first half of 2026. Being small is not protection; in this arena, it's part of the appeal, because small businesses settle quickly.
3. "We don't have a physical store." Mostly wrong. Most federal courts have applied the ADA to online-only businesses too. California courts are stricter, but if you sell to customers in plaintiff-friendly states — and you do, if you sell nationwide — you're exposed there.

Governments got a dated rule: the DOJ's 2024 Title II rule requires state and local agencies to meet WCAG 2.1 AA, with deadlines extended in April 2026 to April 2027 (larger entities) and April 2028 (smaller ones). Private businesses have no dated deadline — but that same standard is what courts measure you against.

What "ADA compliant" actually means when a real person visits your site

Strip away the acronyms and compliance means one thing: a person with a disability can complete the same tasks on your site as everyone else. In practice that breaks down to four groups of visitors:

• A blind customer navigating with a screen reader (which reads your code, not your design)
• A customer with limited mobility navigating only by keyboard — no mouse at all
• A low-vision customer who needs sufficient text contrast
• A deaf or hard-of-hearing customer who needs captions on video

Picture it concretely. A blind shopper opens your store. Your product photos have no alt text, so she hears nothing about what she's looking at. The "Add to cart" control is an icon with no label, so her screen reader announces only "button." The checkout fields show faint placeholder text instead of real labels, so she can't tell which box is the email and which is the ZIP code. She was ready to buy. She can't. That locked door — on one specific transaction — is what "inaccessible" means. It's not an abstract standard. It's a lost sale and, increasingly, a legal claim.

The technical rules behind all of this are the Web Content Accessibility Guidelines (WCAG), published by the W3C. The version to know: WCAG 2.1 Level AA is your legal floor (it's what courts cite); WCAG 2.2 Level AA is your target (it includes everything in 2.1 plus nine newer criteria — visible focus indicators, minimum touch-target sizes, alternatives to drag-only interactions). Aim at 2.2 and you cover 2.1 automatically.

The lawsuit math that should make you uncomfortable

Website accessibility litigation is one of the fastest-growing categories of civil suit in the country. The numbers, from 2025–2026 filings data:

And these cases are industrialized. A small number of plaintiffs and firms file hundreds of near-identical complaints a year: run an automated scan across a list of sites, flag the machine-detectable failures, send the letter. The failures are provable by a tool, so the cases are cheap to bring and expensive to defend. The same handful of errors appears on the majority of websites — a plaintiff needs to know nothing about your business to find a violation on your site.

State laws raise the stakes further. California's Unruh Civil Rights Act treats any ADA violation as a state violation with statutory damages of at least $4,000 per violation — no proven financial loss required. That's a major reason California is one of the busiest filing venues in the country.

The two cases that settled the argument: National Federation of the Blind v. Target (2008) ended in a $6 million class-action settlement and established that an online store could be sued for being inaccessible. Robles v. Domino's (2019) held that the ADA applies to a business's website and app even though the government has never issued website accessibility regulations — and the Supreme Court declined to hear Domino's appeal. "No rules exist yet" has not worked as a defense since.

The $49 widget that makes everything worse

When owners first learn about this risk, the instinct is to find the fastest possible fix — and an entire industry sells exactly that: an accessibility overlay, a line of JavaScript that drops a little widget onto your site and promises instant compliance.

Here is the honest version: an overlay sits on top of your site at page load. It cannot rewrite the underlying HTML that a screen reader actually reads. The missing alt text, the unlabeled form fields, the empty links — they're all still there in the source. Assistive technology reads the source, not the marketing.

The data is blunt:

• 1,416 businesses running an overlay were sued anyway in 2025 — up from 1,023 the year before. In the first half of 2026, nearly a quarter of suits targeted sites with a widget installed.
• In 2025, the FTC ordered overlay vendor accessiBe to pay $1 million for claiming its product could automatically make any site WCAG compliant. The FTC called the claims "false, misleading, or unsubstantiated."

An overlay doesn't fix code — and plaintiffs' firms increasingly cite the widget itself as a barrier in their complaints. If your developer or a plugin vendor sold you one as "compliance," remove it and spend that money on actual fixes.

The six failures behind 96% of all flagged errors

The WebAIM Million — the largest annual audit of the web — found that just six failure types account for 96% of all detected WCAG errors across a million home pages. These are also what automated scanners and serial plaintiffs flag first, because they're unambiguous and machine-detectable. Work through these and you've eliminated the vast majority of your measurable exposure:

1. Low-contrast text (83.9% of pages). Text that melts into its background. Fix: hit a 4.5:1 contrast ratio for normal text (3:1 for large text). Darken the text or lighten the background — free, and usually a theme setting.
2. Missing image alt text (53.1%). Product photos and banners that say nothing to a screen reader. Fix: write a concise alt attribute describing each meaningful image; use empty alt (alt="") only for purely decorative ones.
3. Missing form input labels (51%). Search bars, checkout fields, and newsletter forms that never say what to type — placeholder text is not a label. Fix: tie every input to a real <label>.
4. Empty links (46.3%). Links wrapping an icon or image with no text — your navigation collapses for screen readers. Fix: give the link real text or label the icon with aria-label.
5. Empty buttons (30.6%). "Submit," "Add to cart," or menu buttons with no accessible name. Fix: put text inside the button or add an aria-label describing the action.
6. Missing document language (13.5%). No lang attribute means screen readers can pick the wrong pronunciation engine. Fix: declare it once — <html lang="en">.

The 10-minute self-audit: unplug your mouse

Automated scanners catch only 30–57% of real accessibility issues — keyboard navigation, focus management, and whether error messages make sense when read aloud all need a human. Here's the free version a non-technical owner can do today:

1. Put your mouse aside. Press Tab through your homepage. Can you see where you are at every step — a visible focus outline on links, buttons, and menu items?
2. Try to complete your core task by keyboard alone — add a product to the cart, submit the contact form, book the appointment. If you get trapped somewhere or a control never receives focus, a keyboard-only customer is stuck there too.
3. Zoom to 200% in your browser. Does the layout survive, or does content overlap and buttons disappear?
4. Turn images off (or just imagine them gone). Does the page still make sense — do buttons and links still say where they go?
5. Read your form error messages out loud. "Invalid input" helps nobody. A good error names the field and the fix: "Enter a valid ZIP code."

Ten minutes, zero tools, and you'll find more real barriers than a $99 automated scan.

What fixing it actually costs (honestly)

Compliance guides published in 2026 put professional remediation for a small-to-medium business site at roughly $5,000–$20,000, depending on page count and how deep the problems go. Here's how the options actually break down:

The range that matters most is the last row. Emergency remediation typically costs three to four times the proactive rate — which is the entire financial argument for doing this before anyone writes to you. And skip the overlay "shortcut": the money you spend on it buys zero reduction in risk.

One more cost nobody mentions: every new page, image, and form element is a chance to reintroduce a barrier. Compliance is maintenance, not a one-time project. Budget a monthly scan and a quick accessibility pass on every redesign.

Got a demand letter? The 72-hour playbook

If a letter citing ADA website violations arrives, the instinct is either panic or ignore. Both are wrong. Here's the order of operations:

1. Don't ignore it — and don't panic-sign anything. Many letters demand a quick settlement with a short fuse. The fuse is the tactic. Acknowledge receipt, note the deadline, and buy yourself counsel before you agree to anything.
2. Preserve everything, then scan your site yourself. Save the letter, the envelope (the postmark matters), and any referenced screenshots. Then run your own audit of the pages they cite — you need to know whether their claims are real before your lawyer calls.
3. Hire a lawyer who defends ADA website cases — not a generalist. This is a volume practice with established playbooks on both sides. A specialist knows which firms settle for what and which claims are inflated.
4. Get an independent accessibility audit — not the plaintiff's. You need your own expert's findings: what's genuinely broken, what the letter exaggerates, and what fixing it costs. That report also becomes your remediation roadmap.
5. Start fixing immediately and date everything. Remediation in progress, documented with before/after evidence and an accessibility statement, changes the negotiation.

The quiet truth about this industry: the demand letter is the product. Firms send tens of thousands because quick settlements are cheaper than defense. Fixing your site doesn't just reduce legal risk — it takes you off the list of easy targets.

The part nobody does: staying compliant

A site that was compliant in March regresses by June — new plugin, new banner, new checkout field, each a fresh chance to reintroduce a barrier. The maintenance discipline is simple:

• Run an automated scan monthly (free tools cover the machine-detectable six).
• Do a manual keyboard pass after every redesign or template change.
• Keep a dated accessibility statement on your site with a contact for reporting issues — it documents effort and gives users a path that isn't a lawsuit.
• Train whoever publishes content: alt text on upload, real labels on forms, no "click here" links.

Do the boring six fixes this week. Your future self — the one who never gets the letter — will thank you.

Want to know where your site stands? Run it through our free website audit and see what comes back — or if you'd rather have a developer handle the remediation properly, book a call and we'll walk through what your site actually needs. Our web development services cover accessibility remediation alongside new builds.