ADA Website Lawsuits in 2026: What Small Businesses Need to Know
Most small business websites have accessibility barriers, and lawsuits over them are rising again. In 2025, federal website accessibility filings climbed 27% to 3,117. The safest path is to fix the real code issues, such as contrast, alt text, form labels and link names. Accessibility widgets do not fix those, and the FTC has punished false claims.
Key takeaways
- The DOJ says businesses open to the public must make their web offerings accessible, and it points to WCAG as the guide to follow.
- The FTC fined accessiBe $1 million in 2025 over claims that its widget could make any site compliant. Overlays are not a legal shield.
- WebAIM found detected WCAG failures on 95.9% of the top one million home pages in 2026. Low contrast alone showed up on 83.9%.
This article is general information, not legal advice. If you have received a demand letter or lawsuit, talk to a licensed attorney.
What does the ADA say about websites in 2026?
The ADA does not have a detailed web rule for private businesses. But the Department of Justice says businesses open to the public must give people with disabilities full and equal access to their goods and services, including those offered online. It points owners to the Web Content Accessibility Guidelines (WCAG) as practical guidance.
The DOJ published its Guidance on Web Accessibility and the ADA in March 2022. It covers businesses under Title III of the ADA, which the law calls "public accommodations." Think stores, restaurants, contractors, clinics, gyms and service firms.
The guidance says businesses have flexibility in how they comply. That sounds relaxed, but it cuts both ways. Without a fixed rule, there is no checklist that ends the risk. What matters is whether a person who is blind, deaf, or unable to use a mouse can actually use your site.
The DOJ lists common barriers by name:
- Poor color contrast between text and background
- Using color alone to show meaning, like red for "required"
- Images with no text description (alt text)
- Videos with no captions
- Forms with unclear labels, instructions or error messages
- Pages that cannot be used with a keyboard alone
It also tells owners that automated checkers help but are not the full answer. A clean scan does not mean a site is accessible. A person still needs to test it.
What changed with the DOJ Title II rule for government websites?
In April 2024 the DOJ issued a rule that requires state and local governments to meet WCAG 2.1 Level AA on their websites and mobile apps. In April 2026 it pushed the deadlines back one year. Large governments now have until April 26, 2027, and smaller ones until April 26, 2028.
This rule covers Title II entities: cities, counties, school districts, public colleges and special districts. It does not cover private businesses. Still, it matters to you for two reasons.
- It names a standard. WCAG 2.1 Level AA is now the federal benchmark for public websites. Plaintiffs, courts and buyers often use it as the yardstick for private sites too.
- It affects vendors. If you build sites, sell software or provide online services to a city or school, your work may need to meet this standard.
| Who must comply (Title II) | Original deadline | Deadline after April 2026 extension |
|---|---|---|
| State governments and local governments with 50,000 or more residents | April 24, 2026 | April 26, 2027 |
| Local governments with fewer than 50,000 residents, and special district governments | April 26, 2027 | April 26, 2028 |
The extension came through an interim final rule published April 20, 2026, with public comments accepted through June 22, 2026. Rules like this can change again, so check ADA.gov for the current status before you plan around a date.
How many ADA website lawsuits are being filed?
Thousands each year. The law firm Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, up 27% from 2,452 in 2024. That count leaves out state court cases and demand letters, which are common. So the real number of businesses facing claims is higher.
Seyfarth's year-by-year federal counts show the trend dipped and then bounced back:
| Year | Federal website accessibility lawsuits |
|---|---|
| 2022 | 3,255 |
| 2023 | 2,794 |
| 2024 | 2,452 |
| 2025 | 3,117 |
UsableNet, an accessibility firm that tracks both federal and state filings, counted 2,019 digital accessibility lawsuits in just the first half of 2025. It reported that only 36% of companies sued that year had more than $25 million in annual revenue. In other words, most targets were not big brands.
Small businesses get sued for a simple reason. Their sites are easy to test, the barriers are common, and many owners settle rather than fight. A site with dozens of detectable errors on the home page makes a fast target.
Why don't accessibility overlays protect you?
An overlay is a script or toolbar added on top of your site. It cannot rewrite the structure underneath, so the real barriers stay in place. In 2025 the FTC ordered overlay maker accessiBe to pay $1 million over claims that its tool could make any website WCAG compliant.
The FTC's final order, approved in April 2025, came after the agency alleged two problems:
- accessiBe's accessWidget did not make all customer websites WCAG compliant, so its claims were false, misleading or unsupported.
- The company presented articles and reviews as if they were independent, without disclosing its ties to the people behind them.
The order bars accessiBe from claiming its automated products can make any website compliant, or keep it compliant, unless it has proof.
Here is the plain lesson for owners. A widget is not the same as an accessible website. A blind visitor using a screen reader needs real labels on form fields, real text on buttons, and real descriptions on images. Those live in your site's code and content. If the code is broken, a toolbar on top does not change what the screen reader hears.
Overlays can also add their own bugs, and many people with disabilities already use their own assistive tools. Paying monthly for a widget can create a false sense of safety while the actual problems remain.
What are the most common website accessibility errors?
WebAIM scanned the home pages of the top one million websites in February 2026. It found detectable WCAG failures on 95.9% of them, with an average of 56.1 errors per page. Six issue types made up most of the problems, and nearly all of them are easy to fix.
| Common error | Share of home pages (WebAIM 2026) | What it means | How to fix it |
|---|---|---|---|
| Low contrast text | 83.9% | Light gray text on white, or text over busy photos, is hard to read. | Meet a 4.5:1 contrast ratio for normal text and 3:1 for large text. Check colors with a contrast tool. |
| Missing alt text on images | 53.1% | Screen readers cannot describe the image. | Add short, specific alt text. Mark purely decorative images as decorative. |
| Missing form input labels | 51% | A field says "Name" only as placeholder text, so it is not announced. | Give every field a visible label tied to the input in code. |
| Empty links | 46.3% | Icon links (like social icons) have no text, so they read as "link." | Add hidden text or an accessible name, like "Facebook page." |
| Empty buttons | 30.6% | Menu or search buttons have no name. | Name each button, such as "Open menu" or "Search." |
| Missing document language | 13.5% | Screen readers may use the wrong pronunciation. | Set the page language (for example, English) in the site settings. |
The contrast numbers come from WCAG 2.1's contrast rule. Large text means about 24 pixels, or about 18.5 pixels if bold.
Notice what is missing from that list: exotic problems. Most barriers come from everyday design choices. That is good news. It means a careful designer can prevent most of them during the build.
How can a small business fix its website, step by step?
Start with an audit that pairs an automated scan with a human test, then fix the most common errors on your most-used pages first. Contact forms, booking, checkout and phone links matter most. Add an accessibility statement, keep a written log of fixes, and retest after every major update.
A practical order of work:
- Scan your top pages. Run a free checker like WebAIM's WAVE on your home page, contact page, service pages and checkout. Save the results with a date.
- Test with a keyboard. Unplug the mouse. Press Tab through each page. Can you reach every link, open the menu, fill the form and submit it? Can you see where you are?
- Fix contrast in your brand colors. Change the colors at the style level, not page by page, so the fix spreads sitewide.
- Write alt text. Describe what the image shows and why it is there. "Technician replacing a water heater" beats "image1.jpg."
- Label every form field. Make error messages say what went wrong and how to fix it.
- Name links and buttons. Replace "Click here" with words that make sense on their own.
- Caption videos. Auto-captions are a start. Edit them for accuracy.
- Check PDFs. Menus, price lists and forms posted as scanned PDFs are often unreadable. Turn key ones into web pages.
- Add an accessibility statement. Include a phone number and email so people can report problems and get help another way. The DOJ suggests giving the public a way to report issues.
- Keep records and retest. Log what you fixed and when. Retest after redesigns, new plugins and new content.
Good accessibility also helps search and AI visibility. Clear headings, real text instead of text in images, descriptive links and alt text are the same signals that help search engines and AI tools understand a page.
What should you ask a web designer or freelancer about accessibility?
Ask which standard they build to, how they test, and what they deliver at the end. A good answer names WCAG 2.1 Level AA, includes both automated and manual keyboard or screen reader testing, and promises a written report. Be wary of anyone whose plan is a widget.
Questions worth asking before you hire:
- Which WCAG version and level do you design and build to?
- How do you test? Do you use a keyboard and a screen reader, or only an automated tool?
- Will you check our brand colors for contrast before design starts?
- Who writes alt text, and will you train our team to do it for new content?
- Are forms, menus and pop-ups built so they work with a keyboard?
- Will we get a written list of what was tested and what was fixed?
- Do you recommend an overlay? If yes, why? (A widget-only plan is a red flag.)
- What happens when we add pages later? Is there a checklist for our editors?
Platform matters less than habits. Any modern builder can produce accessible pages, or inaccessible ones. At Forty-Second Street we build in Webflow, which lets designers set semantic headings, alt text, form labels and page language directly. The work still comes down to checking each page.
Frequently asked questions
Does the ADA apply to my small business website?
The DOJ says businesses open to the public must make their online goods and services accessible, and its 2022 guidance applies that to the web. There is no size cutoff in that guidance. Courts in different parts of the country have split on some website questions, so ask a lawyer how it applies to you.
Will an accessibility widget or overlay protect me from a lawsuit?
No tool can promise that. In 2025 the FTC made accessiBe pay $1 million and barred it from claiming its automated widget makes any site WCAG compliant without proof. A widget sits on top of your code. It does not fix the missing labels, alt text and contrast problems underneath.
What standard should my website meet?
Most experts point to WCAG 2.1 Level AA. The DOJ chose that standard for state and local government sites in its 2024 Title II rule. There is no matching rule for private businesses yet, but the DOJ's business guidance points to WCAG as helpful technical guidance.
How much does it cost to fix an inaccessible website?
It depends on the size of the site and how it was built. Fixing contrast, alt text, labels and link text on a small brochure site is often a modest project. A large store with custom code, videos and PDFs takes more. Get a scoped audit first so the quote matches real issues.
What should I do if I get an ADA demand letter?
Do not ignore it, and do not panic-buy a widget. Call a lawyer who handles ADA cases. Save a copy of your site as it looks today. Then start a real audit and a written fix plan. Showing steady, documented progress is better than a quick patch.
The bottom line
ADA website claims are common, and most target ordinary businesses. You cannot buy your way out with a widget. The real protection is a site whose code, colors, forms and content work for everyone, plus records showing you keep it that way. Start with the six common errors above, since they cover most problems. If you want a second set of eyes, Book a free call with Mike or run the free 60-second check to see how your site shows up in search and AI tools.
Sources
- U.S. Department of Justice: Guidance on Web Accessibility and the ADA (2022)
- U.S. Department of Justice: Accessibility of State and Local Government Websites
- UNC School of Government: Understanding the New ADA Web Accessibility Requirements for State and Local Governments
- Plante Moran: DOJ Extends ADA Title II Web Accessibility Compliance Deadlines (April 2026)
- Seyfarth Shaw, ADA Title III blog: Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025
- UsableNet: Digital Accessibility Lawsuits Surge in 2025 (midyear report release)
- Federal Trade Commission: FTC Approves Final Order Requiring accessiBe to Pay $1 Million
- WebAIM: The WebAIM Million (2026)
- W3C: Understanding WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)
Keep reading
