Website accessibility compliance stopped being a nice-to-have somewhere around 2023, and by 2026 it is a legal exposure line item. More than 5,000 ADA web accessibility lawsuits were filed in the US in 2025, and filings are still running in the hundreds every single month this year. If your site has never been audited against WCAG, you are not flying under the radar, you are just a target nobody has noticed yet.
Why Website Accessibility Compliance Is a 2026 Problem
The shift is targeting, not volume. Plaintiff firms now file at scale using automated scanners that flag missing alt text, broken form labels and low-contrast text in minutes, then send demand letters before a human ever looks at the site. That's why the businesses getting hit are rarely big enterprises with legal teams. They are restaurants, clinics, local retailers and small e-commerce stores, precisely because smaller sites are more likely to carry the kind of unresolved, machine-detectable failures that make for an easy case.
There is also a common myth worth killing here: the idea that a small team is exempt. The 15-employee threshold in the ADA applies to Title I employment rules, not to Title III public accommodation requirements, which is the part that covers your website. A five-person company selling online is just as exposed as a five-hundred-person one.
What Courts Actually Expect
Judges and settlement negotiations both converge on the same bar: WCAG 2.1 or 2.2 at Level AA. That's the standard referenced in nearly every consent decree and demand letter template circulating right now, and a site that genuinely conforms to it is very unlikely to face a viable claim. Level AA covers things like:
- Every image carries meaningful alt text, or is marked decorative if it's purely visual.
- Forms have programmatically associated labels, not just placeholder text that disappears on focus.
- Color contrast between text and background hits at least 4.5:1 for normal text.
- Every interactive element is reachable and operable by keyboard alone, no mouse required.
- Headings follow a logical order (H1 then H2 then H3) instead of skipping levels for visual styling.
None of this is exotic. Most of it is a matter of how the site was actually built.
Why Overlay Widgets Keep Losing in Court
A popular shortcut is dropping in a third-party accessibility overlay widget, the kind that adds a floating accessibility icon and promises instant compliance through a script tag. It doesn't hold up. Recent lawsuit tracking found 134 defendants were sued despite having an overlay widget live on their site at the time of the claim. Overlays can adjust font size and contrast on the surface, but they can't fix a form that was never coded with proper labels, or a checkout flow built with divs instead of real buttons. Plaintiffs' attorneys know this now, and several have started naming the specific overlay vendor in the complaint as evidence the underlying code was never touched.
The Checklist: What to Fix First
If you're triaging a site that's never been audited, work in this order, since it roughly matches both legal risk and user impact:
- Keyboard navigation on your primary conversion path. Can someone tab through your contact form, cart and checkout without a mouse? This is the single most common failure point and the easiest for a scanner to catch.
- Alt text and ARIA labels on anything clickable. Icon-only buttons (search, cart, hamburger menu) are frequent misses because they look fine visually but announce nothing to a screen reader.
- Color contrast on body text and buttons. Run your brand palette through a contrast checker before a lawsuit does it for you.
- Form error handling. Errors that only show as a red border, with no text explanation tied to the field, fail for anyone using a screen reader.
- Video captions, if you have any product demos or marketing video on the homepage.
- A documented remediation process, so if a complaint does arrive, you can show ongoing, good-faith effort rather than silence. Courts and opposing counsel treat that difference seriously in settlement talks.
That list runs six items deep rather than the usual three because the reality of an audit doesn't compress neatly, and skipping one of the smaller items is exactly what turns a $5,000 pre-litigation settlement into a longer fight.
What a Fix Costs vs What a Lawsuit Costs
A proper accessibility remediation on an existing marketing or e-commerce site typically runs a few thousand dollars in developer time, since most of the work is targeted: fixing markup, adding labels, adjusting a handful of colors in a design system. Building it in from the start on a new site adds close to nothing to the budget, because it's largely a matter of using semantic HTML and real form controls instead of custom-styled divs.
Compare that to the other side of the ledger. Average pre-litigation demand letter settlements for small businesses run $5,000 to $25,000, and that's before any attorney's fees if the case actually proceeds to a filing. A handful of businesses have paid well into six figures after ignoring an initial demand letter and letting it escalate. The math rarely favors waiting.
Building It Into the Work, Not Bolting It On After
The businesses that handle this well don't treat accessibility as a separate audit line item that happens once a year in a panic. They build semantic markup, real focus states and proper contrast into the design system from day one, the same way they'd build in page speed or mobile responsiveness. That's the approach we take on every custom web build we ship: accessibility gets checked at the component level before a page ever goes live, not retrofitted after a demand letter shows up.
If your current site was built years ago, or handed off by an agency that never mentioned WCAG once, the honest move is a quick audit rather than assuming a widget has you covered. It usually takes less time to find out than it does to explain to a client why the site is suddenly the subject of a legal letter.