Most website risk does not show up as a broken homepage.

It shows up as a contact form someone cannot use. A checkout button without a label. A menu that traps keyboard users. A PDF that cannot be read by assistive technology. A third-party widget that promises compliance but leaves the same barriers in place.

Then the letter arrives.

This guide pulls together current ADA website lawsuit statistics and compliance data for business owners, agencies, in-house marketers, and web teams. Use it to explain the risk, prioritize fixes, and move accessibility out of the “we’ll get to it later” pile.

This is not legal advice. It is a practical planning resource, with every stat linked to its source.

Quick lawsuit benchmarks

Start with these numbers if you need the short version:

The takeaway is simple: filings move up and down by year, court, and counting method, but the risk is not going away.

Why lawsuit numbers vary by source

You will see different totals from Seyfarth, UsableNet, EcomBack, and other trackers. That does not mean one of them is useless.

The definitions are different.

Seyfarth’s 2025 analysis counted federal lawsuits alleging that people with disabilities could not use websites because the sites were not accessible or did not work with assistive technologies. EcomBack’s 2025 annual report counted ADA website lawsuits from January through December 2025. UsableNet tracks digital accessibility lawsuits involving websites, mobile apps, and video content.

For planning, do not obsess over one exact count. Use the range to understand the direction of risk. If several trackers show thousands of filings, the business lesson is the same: accessibility is now part of ordinary website governance.

2025 lawsuit statistics

  1. Seyfarth reported 3,117 federal website accessibility lawsuits in 2025. That number only captures federal court filings under Seyfarth’s methodology, so it does not represent every demand letter, settlement, or state-court action.

  2. Seyfarth said the 2025 total was a 27% increase from 2024. A one-year dip did not mean the category was fading.

  3. EcomBack reported 3,948 ADA website lawsuits for the full 2025 calendar year. That count is useful for businesses that want a broader website-focused litigation benchmark.

  4. EcomBack’s midyear report found 2,014 ADA website accessibility lawsuits from January through June 2025. The first half of the year alone was enough to make accessibility a board-level risk for high-traffic websites.

  5. EcomBack reported that 188 plaintiffs drove those 2,014 first-half 2025 lawsuits. That concentration matters because repeat-plaintiff patterns can create waves of similar complaints across industries.

  6. PR Newswire’s summary of EcomBack’s 2025 midyear report said ADA website lawsuits surged 37% in the first half of 2025. The exact rate depends on the dataset, but several sources show 2025 pressure increasing.

  7. UsableNet reported 2,019 digital accessibility lawsuits in the first half of 2025. UsableNet’s dataset covers digital accessibility, not only classic website pages.

  8. UsableNet wrote that first-half 2025 filings put digital accessibility lawsuits on track to rise nearly 20%. That is the number to show when someone argues that accessibility lawsuits have peaked.

  9. UsableNet later wrote that more than 5,000 digital accessibility lawsuits had been filed by the end of 2025. That broader count is a reminder that apps, video, and other digital experiences are part of the risk picture.

2024 lawsuit statistics

  1. Seyfarth reported 2,452 federal website accessibility lawsuits in 2024. That was still thousands of cases even in a down year.

  2. Seyfarth said the 2024 total was a 13% decrease from 2023. A decrease can reduce urgency in budget meetings, but it should not be confused with safety.

  3. Seyfarth separately reported that total ADA Title III federal lawsuit filings rebounded to 8,800 complaints in 2024. Website accessibility is one part of a larger ADA Title III litigation environment.

  4. UsableNet’s 2024 year-end report summary said state-level lawsuits and digital accessibility risk were major issues for companies heading into 2025. Businesses that only watch federal filings can miss state-level exposure.

  5. Accessibility.Works summarized UsableNet’s 2024 data by noting that 25% of all 2024 lawsuits, 1,023 cases, explicitly cited accessibility widgets or overlays as barriers rather than solutions. That number should make any “install this and we’re compliant” pitch feel suspect.

Overlay and widget risk

An overlay can be useful as one support layer, but it is not a substitute for fixing the website.

  1. EcomBack reported that 199 ADA website lawsuits in Q1 2025 were filed against businesses that had implemented accessibility widgets or overlays. The presence of a widget did not stop those claims.

  2. EcomBack’s Q1 2025 report said those overlay cases involved businesses that had implemented tools promising automated compliance. Automated help is not the same as actual remediation.

  3. EcomBack’s 2024 annual report noted an FTC enforcement action against accessiBe that resulted in a $1 million fine. The message for businesses is not “never use software.” The message is “do not confuse software claims with verified accessibility.”

A safer plan is to fix templates, forms, navigation, content, keyboard behavior, contrast, and media. If you use a tool, make it part of a wider process.

Compliance deadlines and standards

  1. The DOJ’s Title II web rule was published in the Federal Register on April 24, 2024. The rule created specific accessibility requirements for web content and mobile apps provided by state and local governments.

  2. The DOJ fact sheet says WCAG 2.1 Level AA is the technical standard for state and local government web content and mobile apps. Private businesses should still ask counsel about their own obligations, but WCAG 2.1 AA is now a very visible U.S. government reference point.

  3. The DOJ fact sheet says entities with a total population of 50,000 or more have a compliance date of April 26, 2027. That date matters for public-sector teams and the vendors that build or maintain their digital services.

  4. The DOJ fact sheet says public entities with a population under 50,000, or any special district government, have a compliance date of April 26, 2028. Smaller public entities still need time for audits, procurement, remediation, and training.

  5. The DOJ explains that Title II covers services, programs, and activities that state and local governments offer online and through mobile apps. That is why accessibility planning must include more than the homepage.

  6. The DOJ gives examples including public schools, public universities, courts, hospitals, libraries, transit agencies, parks, police departments, and elections offices. If your company sells web services to these organizations, accessibility is not just their problem.

What plaintiffs and users often find

Lawsuits are legal events, but the underlying issues are usually ordinary website problems.

  1. WebAIM found detected WCAG failures on 95.9% of the top one million home pages in its 2026 analysis. That does not mean every site will be sued, but it does show how common detectable barriers are.

  2. WebAIM found an average of 56.1 detected accessibility errors per home page in 2026. If your team has never run an accessibility audit, assume there is work to do.

  3. WebAIM reported that 96% of detected errors came from six categories: low contrast, missing alt text, missing labels, empty links, empty buttons, and missing document language. That makes the first round of fixes easier to prioritize.

  4. WebAIM found missing form input labels on 51% of home pages. Forms are where legal risk and lost revenue often meet.

  5. WebAIM found low contrast text on 83.9% of home pages. Contrast issues are common, visible, and often fixable without rebuilding the whole site.

  6. WebAIM found empty buttons on 30.6% of home pages. Empty buttons often come from icon controls, sliders, menus, popups, and theme components.

  7. WebAIM found missing alternative text for images on 53.1% of home pages. Alt text matters most when the image carries information or functions as a link.

A practical risk-reduction plan

You cannot eliminate every legal risk with one sprint, but you can stop making the same mistakes.

Start with the money paths. Test checkout, appointment scheduling, quote requests, contact forms, login, search, account creation, payment, document downloads, and support flows. These are the paths most likely to frustrate users and create business damage.

Then fix the shared components. Headers, menus, footers, cards, modals, accordions, tabs, sliders, form components, alert banners, and cookie notices appear across many pages. One component fix can improve hundreds of URLs.

Finally, add accessibility to normal quality control. WebAIM’s methodology notes that automated tools have limits and that absence of detected errors does not prove a page is accessible or conformant. Use automated scans, but pair them with keyboard testing, screen reader checks, focus order review, visible focus checks, and content review.

A workable first 30 days looks like this:

  • Run an automated scan on the homepage, top service pages, top landing pages, and every revenue path.
  • Manually test the same paths with only a keyboard.
  • Fix form labels, error messages, button names, link names, contrast, missing alt text, and heading order.
  • Review overlays, widgets, chat tools, schedulers, payment embeds, maps, and PDF downloads.
  • Document what was fixed, what remains, who owns it, and when it will be retested.

The point is not to create a perfect binder. The point is to prove you have a real process.

One more practical note: keep accessibility work tied to release management. When a new theme, plugin, page builder block, popup, scheduling embed, or checkout change ships, retest the affected flow. WebAIM’s data shows that common issues like missing labels, low contrast, empty buttons, and missing alt text are widespread across home pages, so small template changes can quickly reintroduce old problems.

How to use these numbers in a business case

If leadership thinks accessibility is only a compliance expense, use the lawsuit trend line. Seyfarth’s 2025 count rose 27% from 2024, and EcomBack counted 3,948 ADA website lawsuits in 2025. That is enough to justify an audit.

If the team wants to buy a quick overlay and move on, use the overlay data. EcomBack reported 199 Q1 2025 lawsuits against businesses with widgets or overlays, and Accessibility.Works summarized UsableNet data showing 1,023 2024 cases citing widgets or overlays as barriers. That is enough to justify real remediation.

If everyone feels overwhelmed, use the common-error data. WebAIM found that 96% of detected errors came from six categories. That is enough to start.

If your website has not been tested recently, do not wait for a complaint to tell you what users already know. Start a project with Your Web Team and we’ll help you audit the highest-risk pages, fix the patterns that repeat, and build accessibility checks into your normal website workflow.

FAQ

Do small businesses get ADA website lawsuits?

Yes. Lawsuit datasets include many business types and sizes, and UsableNet’s lawsuit tracker notes that 36% of companies sued in the first half of 2025 had annual revenue above $25 million, up from 33% in 2024. That also means many sued companies were below that revenue level.

Does an accessibility widget prevent lawsuits?

No. EcomBack reported 199 Q1 2025 ADA website lawsuits against businesses that had implemented accessibility widgets or overlays. Tools can help, but they do not replace fixing code, content, forms, navigation, and third-party embeds.

What standard should we use for planning?

WCAG 2.1 AA is a practical baseline because the DOJ’s Title II rule uses WCAG 2.1 Level AA for state and local government web content and mobile apps. Many teams also consider WCAG 2.2 AA when planning new design systems.