Accessibility widgets have become a popular way for businesses to address ADA compliance concerns.
The appeal is easy to understand. Many organizations are under pressure to improve accessibility while managing competing technology priorities, limited resources and increasingly complex digital environments. Widgets often promise a faster path to compliance by giving users additional tools to adjust how content is displayed and navigated.
The lawsuit numbers suggest that approach may not be enough on its own.
According to UsableNet’s ADA Website Compliance Lawsuit Tracker, plaintiffs have filed more than 4,000 digital accessibility lawsuits annually since 2021. The company’s 2025 Digital Accessibility Lawsuit Report recorded 3,943 lawsuits across California, New York and Florida.
The trend has continued into 2026. In April alone, 478 digital accessibility lawsuits were filed. More than 100 involved defendants that had previously faced an ADA digital accessibility lawsuit. Nearly a quarter were using third-party accessibility widgets.
That statistic is helping drive a broader conversation about where accessibility problems actually begin.
For years, accessibility discussions largely centered on websites and mobile applications. Those remain important, but many accessibility professionals argue that businesses often focus on the visible parts of the digital experience while overlooking the systems creating the content behind it.
“Accessibility widgets are being treated as a shortcut to ADA compliance, but the lawsuit data shows they are not a shield,” said Chris Hartigan, CEO of MHC. “Organizations need to look deeper at the systems creating their documents, notices and digital communications, because accessibility risk often starts long before a customer sees the final message.”
That distinction matters because customers rarely interact with a website alone.
A patient may download medical forms. A policyholder may receive a statement by email. A customer may access invoices through a portal. A resident may receive notices from a government agency. Every one of those interactions depends on information being accessible before it reaches the screen.
Think PDFs. Statements. Invoices. Benefit notices. Regulatory disclosures.
Many of those documents are generated automatically by back-end systems that were never designed with modern accessibility requirements in mind. If accessibility barriers are introduced during document creation, they can follow the content through every delivery channel that comes afterward.
A widget can change how a website behaves. It cannot rewrite an inaccessible PDF that was created upstream. It cannot correct a document workflow that produces inaccessible content from the start.
That reality is one reason many accessibility programs continue to rely on the Web Content Accessibility Guidelines, or WCAG, as the benchmark for digital accessibility. While WCAG is most often associated with websites and mobile applications, its principles increasingly influence how organizations approach forms, statements, notices and customer communications more broadly.
The challenge is that accessibility issues are often harder and more expensive to address once they become embedded in existing processes.
Legacy document systems, disconnected workflows and aging communication platforms can create barriers that are difficult to identify until customers encounter them. By that point, organizations may find themselves addressing accessibility concerns one document or one website page at a time rather than solving the problem at its source.
The issue is attracting attention from regulators as well.
The Department of Justice’s ADA Title II web and mobile app accessibility rule established accessibility requirements for state and local government websites and mobile applications, with compliance deadlines beginning in 2027 and 2028. While the rule applies specifically to public entities, many accessibility professionals view it as part of a broader shift toward clearer and more measurable accessibility expectations.
The significance of the rule extends beyond government.
Organizations across industries are paying close attention because accessibility requirements are becoming more visible and more specific. Businesses that once viewed accessibility primarily as a website concern are increasingly examining how information is created, managed and delivered throughout the customer journey.
That shift is particularly noticeable in customer communications.
Organizations today communicate across websites, mobile apps, email, digital portals and document repositories. Information moves through multiple systems before it reaches the intended audience. When accessibility is addressed only at the final presentation layer, underlying issues can remain untouched.
MHC has also examined how new accessibility regulations are reshaping customer communications compliance, particularly as businesses work to align digital communications, document workflows and customer experience initiatives with evolving accessibility expectations.
For many organizations, the conversation is becoming less about individual web pages and more about the infrastructure that supports communication overall.
“Accessibility should not be a final layer,” Hartigan said. “If the systems creating customer communications are not built with accessibility, traceability and compliance in mind, organizations are only reducing risk at the surface. The work needs to happen where those communications are created, managed and delivered.”
The argument is not that accessibility widgets have no value. Many organizations use them as part of broader accessibility efforts, and they can provide useful tools for certain users.
The question raised by recent lawsuit data is whether businesses are relying too heavily on visible fixes while overlooking less visible risks.
As organizations communicate through email, portals, mobile applications, PDFs and digital documents, accessibility becomes increasingly tied to the systems responsible for creating and distributing information.
The lawsuit data may not prove that widgets fail. What it does suggest is that accessibility challenges often run deeper than a website alone.
For businesses evaluating ADA compliance efforts, the more important question may no longer be whether a website appears accessible. It may be whether the systems behind that website are creating accessible information in the first place.
