Already have an accessibility widget? What it does and doesn't cover.

The short answer: an accessibility overlay or widget (accessiBe, UserWay, AudioEye's toolbar, EqualWeb and others) adds a toolbar and makes automatic script changes to your site in the visitor's browser. That can genuinely help with things like text size, contrast and simple navigation shortcuts. It cannot rewrite a PDF, add real labels to a broken form, write accurate image descriptions, or fix keyboard traps buried in your site's underlying code. Keeping the widget is your choice either way; the legal deadlines and the WCAG 2.1 AA standard apply to your code and documents, not to whether a toolbar is installed on top of them.

What an overlay actually does

An overlay is a script you add to your site, usually one line, that loads from the vendor's servers and runs in each visitor's browser. It typically adds a toolbar with options such as larger text, higher contrast, a reading guide, or a "screen reader" narration mode, and it may try to automatically add or adjust things like alt text and ARIA labels on the fly. All of that happens client-side, after your page has already loaded, on top of your original code. It does not change the file sitting on your server.

What it can't fix

Because an overlay only adjusts what a browser renders in that moment, it cannot reach into problems that live in the underlying code or in separate files:

  • PDFs and other documents. A widget script that runs on your HTML pages does not open, tag, or rebuild a PDF, Word document, or spreadsheet linked from your site.
  • Forms. An overlay can sometimes add a generic label, but it cannot know what a field is actually for, so mislabeled or unlabeled form fields, and forms that lose your entry on error, usually stay broken.
  • Image descriptions. Automatic, generic "alt text" added by a script is often wrong or unhelpful ("image1234.jpg" guessed at, or a caption that doesn't match the picture), and it can't know what a chart or a product photo is actually showing.
  • Keyboard access. If part of your site was built so that Tab skips a button, or gets stuck in a menu, that's in your page's own script and markup. A browser-side overlay layered on top usually can't repair it.

An overlay changes what a browser shows on top of your page. It does not remediate your source code. WCAG conformance is evaluated against your actual content and documents, not against whether a widget is installed.

The FTC's case against accessiBe

In January 2025, the Federal Trade Commission announced a complaint and proposed settlement against accessiBe, the company behind the accessWidget overlay, over claims that its AI-powered tool "can make any website compliant with WCAG." The FTC's press release stated plainly: "Despite the company's claims, accessWidget did not make all user websites WCAG-compliant and these claims were therefore false, misleading, or unsubstantiated, in violation of the FTC Act." The FTC also found that accessiBe "deceptively formatted third-party articles and reviews to appear as if they were independent opinions by impartial authors and failed to disclose the company's material connections to the supposedly objective reviewers." The proposed order would require accessiBe "to pay the FTC $1 million that may be used to provide refunds to consumers." (FTC press release, January 3, 2025.)

The Commission approved that order as final on April 22, 2025. It requires accessiBe to pay the $1 million. It also bars the company from claiming "that its automated products can make any website WCAG-compliant or can ensure continued compliance with WCAG over time, unless it has the evidence to support such claims." (FTC press release, April 22, 2025.)

This is a case about specific marketing claims an overlay company made, not a ruling that overlays are illegal to use. It is worth knowing about because it is the federal government's own conclusion about what one leading overlay could and couldn't actually deliver.

Sources: FTC, "FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines," January 3, 2025; FTC, "FTC Approves Final Order Requiring accessiBe to pay $1 Million," April 22, 2025.

The UserWay lawsuit

UserWay, another widely used overlay, is a defendant in a putative class action filed in 2024 by a small business, Bloomsybox.com LLC, in the U.S. District Court for the District of Delaware. The complaint alleges that UserWay marketed its widget as ensuring ADA compliance and shielding the business from lawsuits, that Bloomsybox was sued over its website's accessibility about six months after installing the widget, and that UserWay then told Bloomsybox it needed a separate paid plan to get the "legal support" it had been promised. The claims include breach of contract, negligent misrepresentation, and consumer-fraud and warranty-act violations.

As of September 2026, this case is not resolved: in February 2026 a federal magistrate judge recommended that the core claims survive UserWay's motion to dismiss rather than being thrown out, and the docket shows activity as recently as July 2026. It has not been certified as a class action, settled, or dismissed. Treat it as an ongoing lawsuit to watch, not as a finished result either way.

Sources: Bloomsybox.com, LLC v. UserWay, Inc., D. Del., docket via CourtListener; Law Office of Lainey Feingold, "Another Web Access Overlay Company Sued by a Small Business," February 2025; accessibility.build, "UserWay Overlay Class Action Advances in 2026".

What the lawsuit numbers show

AudioEye's own 2026 Web Accessibility Litigation Report states that 38.5% of businesses sued over web accessibility in 2025 already had an accessibility solution in place, usually an overlay or toolbar. In other words, having a widget installed did not keep those businesses out of court. That is a data point about outcomes, not a claim that any particular overlay caused the lawsuits it didn't prevent.

Source: AudioEye, "The 2026 Web Accessibility Litigation Report".

The legal standard, either way

Two federal rules set specific dates for many organizations, and both measure your actual content against the same technical standard, WCAG 2.1 level AA — not against whether a widget is installed:

  • State and local governments, under the Justice Department's ADA Title II rule:
    • Governments serving 50,000 people or more: comply by April 26, 2027.
    • Smaller governments, and every special district government: comply by April 26, 2028.
  • Health providers, under HHS's Section 504 rule. This covers providers that receive HHS federal financial assistance, including practices paid through Medicare Part B, Medicaid or CHIP, even if they take no other federal money:
    • 15 or more employees: comply by May 11, 2027.
    • Fewer than 15 employees: comply by May 10, 2028.

Both rules apply to your website, mobile apps and posted documents, including content a vendor or contractor provides for you, such as an overlay script itself. Neither rule mentions widgets, overlays or toolbars as a way to meet the standard, because the standard is written against the content, not against what runs on top of it.

Sources: DOJ interim final rule, Federal Register, April 20, 2026; HHS interim final rule, Federal Register, May 11, 2026.

Are widgets useless, or illegal?

No, and we're not going to tell you that. Some of what a widget adds — larger text, contrast controls, a reading-guide line — is genuinely useful to some visitors, and no rule bans running one. What the FTC case, the UserWay lawsuit and the AudioEye figures above show is narrower: a widget marketed as making a site "compliant" on its own has not held up to a federal agency's scrutiny or kept sued businesses out of court. The honest read of the evidence is that a widget is an add-on, not a substitute for testing and fixing the code and documents underneath it.

How to switch, without losing anything

You don't have to remove your widget to find out where you stand.

  1. Run a free scan with the widget still turned on. It will show you what's underneath, including problems the widget doesn't reach.
  2. Decide whether to keep the widget. That's your call — nothing about fixing the underlying code requires removing it.
  3. Fix the code and the PDFs. This is the part a toolbar can't do: real labels, real image descriptions, keyboard access, and PDFs rebuilt with tags.
  4. Re-test. Confirm the fixes hold, and keep a written record for your files.

What EveryRamp does

EveryRamp tests your website and PDFs against WCAG 2.1 AA and writes the fixes. It's fully automated — we don't do manual, page-by-page human review, and we won't tell you a page is "compliant" or "conforms"; what we say is that it passes our automated WCAG 2.1 AA tests, and we say plainly which known limits automated testing has. You can start with a free scan of your website, see a sample report, or compare the packages.

This page is general information, not legal advice.

Guides