ADA website lawsuits in 2026: what a small business site actually needs
There is no ADA regulation that sets a technical standard for private business websites, but plaintiffs and courts measure sites against WCAG 2.1 Level AA. Most claims cite the same handful of failures: images without alt text, poor color contrast, forms without labels, content that can't be reached by keyboard, and videos without captions. Fixing those in the site's code covers most of the exposure. An accessibility overlay widget does not, and sites using one are still sued.
This is not legal advice. It is what we look at, as the people who build and fix the sites, when a client asks how exposed they are.
The numbers
Web accessibility litigation has grown every year for a decade. Seyfarth Shaw counted 5,006 federal ADA Title III suits in the first half of 2026, up 9% on the same period a year earlier. That figure covers physical locations and websites together. UsableNet, which tracks digital cases specifically, projected around 6,000 website and app suits for the full year, federal and state combined.
The defendants are not mostly large corporations. EcomBack’s 2025 data put 77% of defendants under $25 million in annual revenue. Small online stores are a particularly frequent target, because the same failures appear on thousands of sites and the claims can be filed at scale.
And lawsuits are only the visible part. Demand letters asking for a settlement before anything is filed are far more common.
What the standard is
The ADA itself does not specify how a private business website must be built. In practice, plaintiffs, settlements and courts point to the Web Content Accessibility Guidelines, WCAG 2.1 at Level AA.
The Department of Justice made that explicit for the public sector: its rule for state and local governments requires WCAG 2.1 AA, with the first compliance date in April 2026. Private businesses are not covered by that rule, but it confirms which standard everyone is using.
The failures that show up in most claims
Automated scans used to identify targets look for the same problems, and they appear on most sites:
- Images without alt text. A screen reader announces “image” or reads the filename.
- Low color contrast. Light gray text on white is the most common single failure on the web.
- Form fields without labels. Placeholder text that disappears when you type is not a label.
- Keyboard traps and unreachable controls. Menus, sliders and pop-ups that only work with a mouse.
- Missing focus indicators. Keyboard users can’t see where they are on the page.
- Videos without captions.
- Links that say “click here”. Out of context, a screen reader user hears a list of identical links.
- Checkout flows that break. For stores, this is where claims concentrate.
None of these is exotic. All of them are fixed in the site’s code.
Why an overlay is not the answer
Accessibility overlays are scripts that add a toolbar and try to repair problems in the browser. They are sold as a one-line fix.
They don’t fix the underlying markup, they frequently interfere with the assistive technology disabled users already rely on, and suits against sites with an overlay installed are reported every year. If anything, an overlay signals that a business knew about accessibility and chose not to fix it.
What we would do
- Audit the templates, not every page. Most sites are built from a handful of templates. Fix the template and every page using it is fixed.
- Start with the money path. Homepage, service pages, contact form, and for stores the product page, cart and checkout.
- Test with a keyboard and a screen reader. Automated tools catch only part of the problems. A person tabbing through the checkout catches the ones that block a real customer.
- Publish an accessibility statement with a contact for people who hit a barrier.
- Build it into the process. New pages, new campaigns and new plugins are where regressions come from.
If your store sells to European customers, there is a second regime to know about: the European Accessibility Act applies to US stores too.
Visible focus states, keyboard navigation and reduced-motion support are part of every component we build, not an add-on. If you want an existing site checked, that starts with a conversation.
Common questions
Does the ADA apply to my website if I have no physical store?
Federal courts are split on whether websites with no connection to a physical location are covered, and the answer can depend on where you are sued. Many online-only businesses are sued anyway, especially in New York and California. The practical answer is to treat accessibility as a requirement, not a legal argument to win.
Will an accessibility widget or overlay protect me?
No. Overlays try to patch problems in the browser instead of fixing the underlying code, and they often fail screen reader users. Lawsuit trackers keep reporting suits against sites that had an overlay installed. Disability advocates broadly oppose them.
How much does it cost to make a small website accessible?
For a site built recently on a clean codebase, the common fixes are usually days of work, not months. Older sites built on heavy templates and page builders cost more, and sometimes a rebuild is cheaper than remediation. An audit tells you which situation you're in before you commit.
