August 12, 2026

Website accessibility (ADA) lawsuits: what small business owners actually need to know in 2026

You built a website to bring in customers. You didn't expect a certified letter from a law firm in New York demanding $25,000 because a blind user couldn't complete your contact form. But that letter is landing in more small business inboxes than ever, and the plaintiffs' bar has spent the last three years turning this into a volume business.

Here's what's actually happening, what the law actually requires, and what you can do this week to lower your exposure — without falling for the fake fixes.

Why small business sites became the target

The math is simple. A handful of plaintiff-side firms have built automated scanners that crawl thousands of websites a day looking for the same handful of accessibility failures — missing alt text, form fields without labels, low color contrast, images used as buttons with no accessible name. When a site fails, a demand letter goes out. The letter typically offers to settle for somewhere between $10,000 and $50,000, which is calibrated to be cheaper than defending a lawsuit even if you'd probably win.

Big companies have in-house counsel and remediated years ago. Small businesses don't, which makes them the softer target. The plaintiff doesn't need to have been a real customer, doesn't need to prove damages in the way you'd expect, and in many jurisdictions doesn't even need to live in your state. If your site takes online orders, books appointments, or serves as a public storefront, you're in scope.

The trend line since 2023 has been up and to the right. It has not slowed down heading into 2026.

What the ADA actually says (and doesn't)

The Americans with Disabilities Act was signed in 1990, long before "website" meant anything. Title III of the ADA prohibits discrimination by "places of public accommodation." For decades, courts have been figuring out whether that includes websites.

The short version as of 2026:

Federal courts have consistently ruled that websites tied to a physical business are covered. The Ninth and Eleventh Circuits disagree on some edges, but if you have a store, office, restaurant, or clinic, assume your site is covered.
The DOJ's current position is that Title III applies to web content, and while there's no federal regulation naming a specific technical standard for private business, the DOJ has repeatedly pointed to WCAG as the practical benchmark. In 2024, DOJ finalized rules requiring state and local governments to meet WCAG 2.1 AA. Private business rules are expected to follow the same standard.
"There's no clear standard, so I'm safe" is the argument that loses in court and loses in settlement negotiations. Judges and plaintiffs both point to WCAG 2.1 AA. If your site meets it, you have a defense. If it doesn't, you don't.

Treat WCAG 2.1 AA as the standard. That's what the demand letters cite. That's what the settlements require.

WCAG 2.1 AA in plain English

WCAG stands for Web Content Accessibility Guidelines. Version 2.1, conformance level AA, is the target. Here's what it actually means for your site:

Alt text on images. Every image that conveys information needs a text description that a screen reader can announce. Decorative images get an empty alt attribute so the screen reader skips them. A product photo needs a real description. A logo needs the company name.

Keyboard navigation. A user with a motor disability, or a blind user with a screen reader, may never touch a mouse. Every button, link, form, and menu on your site has to work using only the Tab, Shift+Tab, Enter, and arrow keys. If your fancy dropdown menu only opens on hover, it fails.

Visible focus indicator. When someone tabs to a button, there needs to be a visible outline or highlight showing where they are. Designers hate these outlines and often remove them in CSS. That removal is one of the most common lawsuit triggers.

Color contrast. Text has to have enough contrast against its background to be readable by people with low vision. The minimum is 4.5:1 for normal text and 3:1 for large text. Light gray text on a white background — a design trend that refuses to die — almost always fails.

Form labels. Every input field needs a real <label> element tied to it, not just placeholder text. Screen readers announce the label. A field with only placeholder text says "edit text" and the user has no idea what to type.

Video captions. If you have marketing videos, they need captions. Auto-generated YouTube captions are a start but often not accurate enough to count.

There's more in the spec, but those six categories cover the vast majority of what shows up in demand letters.

Free tools that catch 80% of the issues

You can self-audit your site in an afternoon. Three tools do most of the work:

axe DevTools — a free browser extension from Deque. Install it in Chrome or Firefox, open your site, and run the scan. It gives you a list of violations with the exact element and a plain-English explanation of what's wrong. This is the same engine most professional auditors use.

WAVE by WebAIM — free extension and web-based scanner at wave.webaim.org. Very visual. Puts icons directly on your page showing errors, alerts, and structural issues. Good for people who learn visually.

Lighthouse — built into Chrome DevTools. Open your site, right-click, Inspect, then the Lighthouse tab. Run an accessibility audit. Gives you a score out of 100 and a categorized list of issues.

Run all three on your homepage, your most important product or service page, and your contact page. Between them you'll find most of the automatable failures. Fix those and you've removed the majority of the low-hanging fruit that plaintiff scanners look for.

What free tools don't catch

The uncomfortable truth: automated scanners find maybe 30–40% of real accessibility problems. The rest requires human testing:

Manual keyboard testing. Unplug your mouse. Try to complete a purchase, submit a form, open a menu. Can you do everything with just the keyboard? Where do you get stuck?
Screen reader UX. Reading through NVDA (free, Windows) or VoiceOver (built into Mac) reveals whether your page structure actually makes sense when read aloud. A page can pass every automated test and still be a disaster to navigate by ear.
Dynamic content. Modals, popups, "load more" buttons, live search results — automated tools frequently miss whether these announce themselves properly to assistive tech.
PDF documents. If your site hosts PDFs — menus, brochures, forms, reports — those PDFs need to be accessible too, and they usually aren't. Scanners don't check them.

The 80/20 fixes most small businesses need

If you do nothing else, these five fixes will address the majority of demand-letter targets:

Add real alt text to every content image. Not "image1.jpg." Describe what's in the picture in the context of the page.
Add proper <label> elements to every form field. Placeholder text is not a label.
Fix color contrast. Run your palette through webaim.org/resources/contrastchecker. Darken your light grays. If your brand color is a pastel used for buttons, you probably need a darker variant just for interactive elements.
Restore visible focus outlines. If your stylesheet has outline: none anywhere, remove it or replace it with a custom visible focus style.
Fix your headings. Every page should have exactly one <h1>, and headings should nest logically (h2 under h1, h3 under h2). Don't use headings for visual styling — use them for structure.

For a small brochure site, that's often a one-to-two-day job for a competent developer. For a WordPress site with a pile of plugins, expect longer, because plugin-generated markup is where a lot of the problems live.

When to hire a pro

Self-audit gets you a long way, but there are cases where you want a professional audit and remediation plan:

E-commerce. Every step of checkout has to work with a keyboard and a screen reader. This is where plaintiff firms focus.
Healthcare and education. Higher scrutiny, higher expectations, often overlapping regulations (HIPAA, Section 508, state laws).
Any site over about 50 pages. The manual review burden crosses over into needing dedicated hours.
You've already received a demand letter. Do not respond to a demand letter without both an attorney and someone who can actually document remediation. Settlements often require a remediation plan and follow-up audits.

A real audit combines automated scans across every template, manual keyboard and screen reader testing on key user flows, and a written report tied to specific WCAG success criteria.

The overlay trap

You've seen the ads. Drop in one line of JavaScript, get an accessibility widget in the corner of your site, become "ADA compliant" overnight. accessiBe, UserWay, and similar products have been sold heavily to small businesses.

Here's the reality: the DOJ has publicly stated that automated overlays do not by themselves make a website accessible. Multiple lawsuits have been filed against businesses that had overlays installed — the overlays did not prevent the suit, and in several cases the plaintiff specifically cited the overlay as evidence of a bad-faith attempt to paper over real problems. The National Federation of the Blind has been unambiguous that overlays are not a solution and often make screen reader experiences worse.

If someone tries to sell you a $49/month widget that promises legal compliance, walk away. You're paying to feel safer while remaining exposed.

The real cost math

Remediating an existing site is expensive because you're fixing decisions someone else made — sometimes years ago, across dozens of pages, with plugins and third-party embeds in the mix. Building accessibility in from the start, when the site is designed and coded, adds maybe 10–15% to a build. That's it.

I'd rather build you a site that passes WCAG 2.1 AA on day one than remediate a site that failed on day 800 because a plaintiff firm's scanner found it first.

If you're planning a new site or a rebuild, accessibility should be part of the spec, not an afterthought. I build sites in React and Next.js with accessibility baked into the components, and I'll run the audit on the finished product before it goes live. If you'd like to talk through a build, or you want a quick self-audit walkthrough on your existing site, get in touch at thewizrdz.io and we'll figure out where you stand.