Website accessibility lawsuits in 2025: the data, and what actually reduces your risk

If you run a small business website and assume accessibility lawsuits are a big-company problem, the 2025 numbers are worth two minutes of your time. Federal filings hit 3,117, up 27 percent in a single year, and most of the businesses on the receiving end were not big companies at all.

Here is what the year actually looked like, why the target has moved to smaller sites, and the short list of things that genuinely lower your exposure. None of this is legal advice. It is the lay of the land before you decide what to do about your own site.

The numbers, and what they add up to

The filings are a matter of public record, and the pattern in them is not subtle.

Read together, those rows tell one story: more suits, aimed lower, and often at the same companies twice. Where they get filed keeps shifting, but the volume does not let up. New York led with 1,021 filings, Florida more than doubled to 961 (from 470 the year before), and Illinois reached 585. California, once the busiest venue of all, dropped to 4 after an appellate ruling that online-only businesses are not covered there. No single state got safer. The filers simply follow the courts where the claims hold up, and the national total climbs regardless.

Two industries carry most of the risk. Roughly 70 percent of website cases were against e-commerce, and about 21 percent against food service. If customers buy or order from your site, you are standing in the part of the room where the suits land.

Why the target moved to smaller businesses

It is tempting to picture these cases chasing national retailers. In 2025 they mostly did not: 64 percent of defendants reported under $25 million in revenue. The reason is simple economics. A complaint against a small business is cheap to prepare, the barriers on the site are easy to spot from the outside, and a quick settlement is usually cheaper for the owner than a fight. That math favors filing widely against small sites, and it is exactly what the numbers show.

The figure that should stay with you is the repeat rate. Nearly half of 2025's filings named a company that had already faced an accessibility claim. Once your site is on a list, settling without fixing the underlying problems buys quiet, not safety. The same barriers are still there, the same tools find them again, and a second letter follows the first.

Why an accessibility widget will not save you

A lot of owners install an overlay widget, a single line of JavaScript that promises to make a site accessible automatically, and consider the matter closed. The 2025 data does not back that up. Sites running overlays kept getting sued at a steady pace all year, and in plenty of complaints the widget is named as part of the problem rather than the cure.

The reason is simple once you see it. An overlay sits on top of your site and adjusts what a visitor sees as the page loads. It does not touch the code underneath, so the barriers a screen reader or a keyboard user actually runs into are often still there. An overlay that never touches the code cannot remove the barriers that live in the code. We break down the overlay data on its own in a separate piece.

What actually lowers your risk

First, the standard you are aiming at. There is no formal Department of Justice regulation that sets a technical bar for private business (ADA Title III) websites. In practice, courts and the DOJ keep coming back to the same reference, the Web Content Accessibility Guidelines, and case law now treats WCAG 2.1 Level AA as the working benchmark. When the DOJ finalized its 2024 rule for state and local governments, it wrote WCAG 2.1 AA into that rule, which only cemented it further as the version everyone points to. So WCAG 2.1 AA is the target, and the work that moves you toward it is the work that lowers your exposure.

Five steps, in order:

1. Find the real problems. Start with an audit against WCAG 2.1 AA across your main page templates, not a glance at the homepage. An automated scan is the fast first pass, and a genuinely useful one, as long as you know its ceiling: software can only judge about a quarter of the WCAG success criteria on its own, so a scan gives you a real, specific list of what is broken and flags the rest for a person to check. It shows you where you stand and what to fix first. It is not a certificate that says you are finished.
2. Fix the code, worst first. Remediate the actual HTML and interactions, in the order that matters most to real use. Missing text alternatives, unlabeled form fields, poor keyboard access, and low contrast are the usual, high-impact offenders.
3. Confirm the fixes. Re-check each item against the standard, so a fix that looks correct is confirmed to be correct.
4. Write it down. Publish an accessibility statement and keep your audit and remediation records. Showing steady, documented effort is part of how these matters get resolved.
5. Keep at it. A site is never finished. Every new page, template tweak, or third-party embed can introduce a fresh barrier, which is why sites that were fixed once quietly drift back out. Ongoing monitoring catches those regressions before a tester does.

Where to start this week

Run a scan and get a prioritized list of the accessibility issues on your pages, and where they are. Fix the issues at the top, publish an accessibility statement, and set a rhythm for checking the site so the work holds instead of decaying. If a demand letter has already arrived, talk to an attorney before you reply.

None of this makes you lawsuit-proof, and anyone who tells you otherwise is selling something. What it does is close the barriers a plaintiff's tester would find, and leave you in a far stronger spot if a claim ever comes.

FAQ

Is my small business really at risk if I am not a big retailer?

Yes. In 2025, 64 percent of the businesses sued over website accessibility made under $25 million a year. The model runs on filing volume, and small e-commerce and food-service sites are the easiest volume to file against.

What accessibility standard does my website need to meet?

For private businesses under ADA Title III there is no formal federal regulation naming a standard, but courts and the DOJ consistently point to WCAG 2.1 Level AA, and it is treated as the working benchmark. The 2024 DOJ rule for state and local governments adopted the same version.

Does an accessibility overlay or widget protect me from a lawsuit?

The 2025 data says no. Businesses using overlay widgets kept getting sued, and the widget is sometimes named in the complaint. An overlay does not change your underlying code, so it cannot be relied on to remove the barriers a claim is built on.

Can an automated scan make my site compliant?

No. Automated testing can evaluate only about a quarter of the WCAG success criteria. A scan is a fast, accurate way to find a real set of problems and see what to prioritize, and it tells you what still needs a human. It is a starting point for fixing your site, not a compliance certificate.

I received an accessibility demand letter. What should I do?

Talk to an attorney before you respond. This article is information, not legal advice, and the right move depends on your specific situation.