Do accessibility widgets or overlays make a website compliant?

Ascent Vision · Published October 24, 2026

Not on their own, and no tool can promise it. In a January 2025 notice of a proposed settlement, the Federal Trade Commission said its complaint alleged that a seller's claims that its automated accessibility plug-in could make any website meet the Web Content Accessibility Guidelines were false, misleading or unsubstantiated. Justice Department guidance says automated checkers and overlays can help but need to be used carefully. Fixing barriers in the site itself, checked by people, is the safer path. This is a plain summary, not legal advice.

What the FTC alleged

The FTC's notice in the Federal Register of January 6, 2025, "accessiBe; Analysis of Proposed Consent Order To Aid Public Comment", concerns accessWidget, a web accessibility plug-in sold by accessiBe. The notice says accessiBe represented that accessWidget could make any website compliant with the Web Content Accessibility Guidelines (WCAG), a set of technical criteria used to assess website accessibility.

According to the notice, the proposed complaint alleges that the tool did not make all websites WCAG compliant and that the claims were false, misleading or unsubstantiated. It also alleges that accessiBe presented third-party articles and reviews as independent opinions without disclosing its ties to their publishers. The proposed order would bar accessiBe from claiming that its automated products can make any website WCAG compliant, or keep it compliant as content changes, unless it has competent and reliable evidence.

These are the FTC's allegations and the terms of a proposed consent order, in an agreement the Commission accepted subject to final approval; the notice is not a court finding, and this answer covers that notice only. It concerns how a product was advertised; it is not a ruling on what the Americans with Disabilities Act requires of a business. This is a plain summary, not legal advice.

The parts of a site a widget may not reach

The proposed order would also require accessiBe to disclose that its products will not fix barriers on third-party domains or subdomains that are part of the overall experience, unless those also use the product. A concurring statement printed with the notice, by two commissioners, gives making a reservation or processing a payment as examples of functions a site can rely on another domain for, and says their votes take no position on whether the ADA or WCAG require a site owner to make those outside parts accessible.

As general advice, not the FTC's: list the outside pieces your customers use, such as a booking tool or a payment page, and check them too.

What the Justice Department says

The Justice Department's guidance on web accessibility says automated checkers and overlays that find or fix problems can be helpful tools, but that "they need to be used carefully". The related answer on website accessibility covers the rest of that guidance.

What to do instead

Fix common barriers in the site itself; the related answer on website accessibility lists them, with simple checks an owner can run.
Before buying any accessibility tool, ask the seller in writing what it does not fix, and which parts of your site it cannot reach.
Be wary of any product sold as making a site fully compliant or protecting you from lawsuits; no checklist, tool or website build can promise legal compliance.
Give visitors a clear way to report a problem. The Justice Department's guidance notes that this lets owners fix issues.
If a legal letter or claim arrives, talk to a lawyer rather than relying on a tool's report.

Sources

Websites, upgraded or built

Most businesses do not need a new website. They need the one they have to load fast, say clearly what they do and ask the visitor to take one step.

See the service Work with us