You Installed an Accessibility Widget. Businesses Are Still Getting Sued.

There is a very comforting version of website accessibility that goes like this: install a widget, watch the little accessibility icon appear in the corner, and congratulate everybody because the internet has now been repaired. Unfortunately, the HTML did not receive the memo.

It is easy to understand why small-business owners buy these things. Accessibility is technical, the legal conversation is confusing, and nobody running a restaurant, repair shop, bakery, dental office, boutique, or five-person service company wakes up excited to compare WCAG success criteria before breakfast. A product that promises to handle the problem automatically sounds wonderful.

The issue is not that accessibility tools are automatically useless. Some can help. The problem starts when a business treats the presence of the tool as proof that the website itself is now accessible, WCAG compliant, legally protected, or finished.

The number worth paying attention to is 134.

UsableNet publishes a monthly tracker of web accessibility litigation. For August 2026, it reported 432 new ADA web accessibility lawsuit filings. It also reported that 134 defendants were sued while using a third-party accessibility-related control or widget.

That number is worth reading carefully. It does not prove that widgets cause lawsuits. It does not prove every defendant had an inaccessible website. It does not prove every plaintiff will win. What it does prove is much simpler: having a widget on the website does not stop a business from being sued.

UsableNet is also not a court or government agency. It is a private accessibility company tracking litigation. Its monthly tracker says it monitors federal filings along with state-court filings in New York and California. That number should not be treated as a complete census of every accessibility dispute in America.

But if somebody sold you a tool and you walked away believing that the little icon effectively took website accessibility off your list forever, 134 is still a pretty good reason to reopen the list.

A lawsuit filing is not a court ruling.

This subject gets exaggerated quickly, especially by companies trying to sell fear in either direction. A filed complaint is an allegation. It is not a finding that the business violated the ADA, and the existence of a lawsuit does not tell us how the case will end.

The useful part of the litigation data is not, "Look, 432 companies were proven guilty." That is not what the tracker says. The useful part is that website accessibility continues to produce a significant amount of litigation, and businesses using third-party controls are clearly not outside that system.

If your reason for buying a widget was "this means nobody can sue me," the filing data alone is enough to retire that sentence.

The Department of Justice does not describe overlays as a magic fix either.

The U.S. Department of Justice says that businesses open to the public must ensure that the goods, services, privileges, and activities they provide online are accessible to people with disabilities. For private businesses under Title III, the DOJ does not give every business one universal technical website checklist that automatically settles every legal question.

What it does provide is practical accessibility guidance, and this part is especially relevant to the widget conversation: the DOJ says automated accessibility checkers and overlays can be helpful tools, but they need to be used carefully. A clean automated report does not necessarily mean the website is accessible.

The DOJ specifically recommends pairing automated checking with manual review. That is a very different message from "install this script and stop thinking about it."

The Department also points businesses toward technical accessibility standards such as WCAG. The current W3C Recommendation in that series is WCAG 2.2.

We already have a separate practical small-business website accessibility guide covering keyboard navigation, focus, contrast, form labels, headings, alt text, automated testing, and the other actual website work. This article is about why the widget should not be mistaken for all of that work.

The FTC already had a problem with how one major accessibility product was marketed.

In April 2025, the Federal Trade Commission approved a final consent order involving accessiBe, the company behind the accessWidget accessibility product.

The FTC had alleged that accessiBe made false, misleading, or unsupported claims that its automated product could make any website compliant with WCAG. The final order required the company to pay $1 million and restricted it from making certain WCAG-compliance claims about its automated products unless it had adequate evidence to support them.

That does not mean every accessibility widget is accessiBe. It does not mean every accessibility vendor makes the same claims. And it does not mean the FTC declared automated tools worthless.

What it does mean is that the marketing language around automated accessibility has already been important enough for a federal consumer-protection agency to step in.

The underlying website still gets a vote.

A website can have an accessibility widget and still contain unlabeled form fields, confusing heading structure, keyboard traps, invisible focus states, poor contrast, meaningless link text, inaccessible dialogs, badly written alternative text, video without useful captions, or custom controls that assistive technology cannot understand.

Some automated products may identify or modify certain parts of that experience. The important question is whether the person using the website can actually complete the task.

Can somebody book the appointment? Can they choose a service? Can they complete checkout? Can they understand the error message? Can they open and close the navigation? Can they find the business hours? Can they use the form without a mouse?

If the answer is no, telling them there is an accessibility button in the corner is a little like telling somebody the building has a wheelchair sticker while the entrance still has stairs.

This is also why basic usability and accessibility overlap so often. Our guide to fixing a confusing small-business website deals with navigation, calls to action, mobile usability, and making the next step obvious. Accessibility adds additional requirements, but both conversations start with the same rude question: can people actually use the thing?

So what should a small business actually do?

Start by getting rid of the idea that accessibility is one purchase. Treat it like part of maintaining the website.

Use automated tools because they are useful. Run WAVE or another reputable checker. Check contrast. Validate markup. Use browser accessibility tools. Let software find the things software is good at finding.

Then do the part the software cannot finish for you. Navigate the important pages with a keyboard. Review focus behavior. Test the forms. Inspect headings and labels. Review meaningful images and alt text. Test interactive components. Try zoom and responsive layouts. Get human testing involved, particularly when the website performs important transactions or serves a large audience.

Give visitors a clear way to report accessibility problems and actually respond when somebody does. Keep fixing issues as the site changes, because the website you tested six months ago is not necessarily the website sitting there today after three plugins, a redesigned form, a new booking system, and whatever Kevin installed on Friday afternoon.

If you already pay for an accessibility widget, ask better questions.

Do not panic and rip it out just because you read one article. Find out what you actually bought.

Ask the vendor what the product changes automatically, what it does not change, whether human audits are included, how issues are remediated, how frequently the site is rechecked, and what happens when your developers change the website.

If the sales material mentions WCAG compliance, ADA compliance, lawsuit protection, guarantees, indemnification, or legal support, read the actual contract and terms instead of the headline. Find out exactly what the promise covers and what conditions or exclusions come with it.

And if your business needs a legal determination about its obligations, get that determination from qualified counsel, not from the green checkmark beside the word "compliant" in a dashboard.

Sources

• UsableNet: ADA Accessibility Lawsuit Tracker
• U.S. Department of Justice: Guidance on Web Accessibility and the ADA
• Federal Trade Commission: Final accessiBe order
• Federal Trade Commission: accessiBe case record
• W3C: Web Content Accessibility Guidelines 2.2