Short answer: The Federal Trade Commission (FTC) says accessiBe claimed its plug-in accessWidget can make any website compliant with the Web Content Accessibility Guidelines (WCAG). The final order bars accessiBe from representing that its automated products can do so unless it has the evidence to support such claims. It names accessiBe Ltd. and accessiBe Inc. as the Respondents and requires them to pay $1,000,000.00. The Department of Justice says automated checkers and overlays that identify or fix problems with a website can be helpful tools but need to be used carefully. The pages said so on November 13, 2026.
Before you read: This guide is based on the FTC’s press releases, its complaint, its decision and order, and its business blog post on the accessiBe case. It also uses a page from the W3C Web Accessibility Initiative and one from the Department of Justice’s ADA.gov. We read them on November 13, 2026. It is general information, not legal advice.
What the FTC order says
The FTC announced a proposed order settling its complaint against accessiBe Inc. and accessiBe Ltd. (accessiBe) on January 3, 2025. Its press release of April 22, 2025 says the Commission approved the final consent order.
The decision and order, docket number C-4817, shows April 21, 2025 as its issue date. It says it is final and effective on the date it is published on ftc.gov as a final order.
The order defines “Respondents” as accessiBe Ltd. and accessiBe Inc., and their successors and assigns. Provisions I to V also reach the people the order lists as acting for the Respondents. They reach as well all other persons “in active concert or participation with any of them” who receive actual notice of the order.
In the consent agreement, the Respondents state that they “neither admit nor deny any of the allegations in the Complaint, except as specifically stated in this Decision and Order”. They admit the facts necessary to establish jurisdiction, only for purposes of this action.
Provision VII adds a rule for a later civil case by or for the Commission to enforce payment. In it, the facts alleged in the complaint will be taken as true, without further proof.
The order requires accessiBe to pay the Commission $1,000,000.00 within 8 days of the effective date. It says money paid may be deposited into a fund used for relief, including consumer redress. The January press release says the money may be used to provide refunds to consumers.
Provision VIII requires accessiBe to provide sufficient customer information to enable the Commission to efficiently administer consumer redress to all purchasers or subscribers to accessWidget.
The order covers any product or service represented “to correct website accessibility barriers through the use of automated tools, including accessWidget”. Provision I bars accessiBe from representing, expressly or by implication, that such a product “can make any website compliant with WCAG”.
It also bars saying the product “can ensure continued automatic compliance with WCAG over time as website content changes”. It bars representations about the benefits, performance or efficacy of the product as well.
Provision I applies unless the representation is “non-misleading”. The order says this includes that, “at the time such representation is made”, accessiBe possesses and relies upon “competent and reliable evidence”. It describes that evidence as “sufficient in quality and quantity based on standards generally accepted in the relevant fields”. It adds “when considered in light of the entire body of relevant and reliable evidence”, to substantiate that the representation is true.
The order defines “competent and reliable evidence” as “tests, analyses, research, studies, or other evidence based on the expertise of professionals in the relevant area”. It adds that the evidence has been “conducted and evaluated in an objective manner by qualified persons” and is “generally accepted in the profession to yield accurate and reliable results”.
The April press release says the complaint also alleged that accessiBe deceptively formatted third-party articles and reviews to appear as if they were independent opinions. Provision II bars misrepresenting any fact material to consumers concerning the good or service. Provision III bars misrepresentations about reviews and endorsements, including that statements in reviews, articles or blog posts on third-party websites are independent opinions by impartial authors or publications.
Provision IV bars representations about an endorser without disclosing any “Unexpected Material Connection” between the endorser and a Respondent, or any other individual or entity affiliated with the product.
The FTC wrote a business blog post on the case, dated April 23, 2025. It says: “before you claim your product can perform a certain task, you need evidence it will work as promised”. Its tips are to tell the truth in ads and to be clear and honest about reviews and testimonials.
In our view, the claims named in Provision I are worth looking for on the page of any widget vendor.
What the FTC says the widget was sold as
The complaint describes accessWidget as a software plug-in marketed as a tool to correct website accessibility barriers, and as a website “overlay”. It says overlays are intended “to permit temporary modifications to the user interface that may impact accessibility”, not “to permanently alter web code or design”.
Its examples are color contrast, text size, animated elements and navigational components. The complaint also says accessiBe has advertised accessWidget since 2019 as an “AI-powered web accessibility solution”.
According to the complaint, accessiBe claimed that installing accessWidget’s “one line of code” makes a website compliant with 30% of WCAG’s requirements immediately. It also claimed that an AI process makes the website fully compliant with the remaining 70% within 48 hours.
The complaint adds that accessiBe promised that accessWidget “ensures compliance even when web content is altered, by re-scanning the website every 24 hours”.
The January press release says that, according to the complaint, accessWidget did not make all user websites WCAG-compliant despite accessiBe’s claims. The release adds that, according to the complaint, the claims were therefore false, misleading or unsubstantiated.
The complaint alleges that, in a number of instances, websites running accessWidget contain or have contained barriers. It says they would make it difficult or impossible for people with disabilities to use the content for its intended purpose. The barriers it lists include missing or inaccurate alt text for key images, a missing focus indicator, keyboard traps, incorrect headings, and problems with menus, buttons and tables.
The complaint alleges that accessiBe did not disclose, or disclose adequately, what accessWidget does not cover. It lists documents, PDF, audio and video among the components that, unless additional services are purchased, accessWidget does not make accessible.
In some instances, the complaint alleges, websites running accessWidget linked to external third-party domains whose pages did not include accessiBe and were not accessible to a person with a disability. Its example is a link “to complete an e-commerce transaction or reservation”.
Provision V of the order bars accessiBe from representing that such a product can correct accessibility barriers on a website without making a disclosure. The disclosure is that the product “will not correct barriers on third-party web domains or subdomains that may be part of the overall user experience”.
The provision has an exception: “unless those domains also use the product”. It sets the timing and form: “clearly and conspicuously, and prior to the consumer incurring any financial obligation”.
What automated tools can check
The complaint cites web accessibility experts, including the W3C, for the point that “no automated testing tool alone can determine if a website meets accessibility standards”.
The W3C’s page on selecting evaluation tools, updated May 13, 2024, says: “Web accessibility evaluation tools can not determine accessibility, they can only assist in doing so”. Our guide to website accessibility checkers covers the free checkers and what to review by hand.
What the Department of Justice says about websites
The Department of Justice’s guidance on web accessibility and the ADA is dated March 18, 2022. It says automated accessibility checkers and overlays that identify or fix problems with a website “can be helpful tools”. Like other automated tools, such as spelling or grammar checkers, “they need to be used carefully”, it says. It adds that a “clean” report does not necessarily mean everything is accessible.
Our guide to ADA website compliance for a small business covers what the Department of Justice says about the ADA and websites.
In our view, the W3C and the Department of Justice point the same way: a tool’s report does not say on its own whether a website is accessible.
The checks and the statement
The statement a site publishes about its accessibility is in our guide to accessibility statements. Our guide to WCAG 2.2 covers what changed in that version. The checker guide linked above covers what a free checker runs.
Web design at Feedback Studios
Our web design page says we design and build websites for local businesses, in English and Spanish.
It says we write the words, build in WordPress so your team can change any page without code, and hand you every login.
What to check before you add or keep a widget
In our view, check these points before you add a widget or keep one:
- You compared the claims on the vendor’s page with the claims the FTC order bars accessiBe from making.
- The vendor can show the evidence behind each claim about what the product fixes.
- The vendor’s page says, before you pay, what the product does not cover, such as documents, PDF, audio, video and pages on other domains.
- The reviews and articles you read about the product say whether their authors have a tie to the vendor.
- You tested the pages by hand with the widget on, and did not rely on an automated report alone.
- You listed the pages that sit on another domain, such as a booking or payment page, and tested them too.
RememberThe FTC says accessiBe claimed accessWidget can make any website compliant with WCAG, and the final order bars that claim unless accessiBe has the evidence. The Respondents neither admit nor deny the complaint’s allegations, except as the order specifically states. The order requires accessiBe to pay $1,000,000.00. The Department of Justice says overlays need to be used carefully. The pages said so on November 13, 2026.
Questions about accessibility widgets and the FTC order
Does an accessibility widget make a website compliant?
The FTC order bars accessiBe from representing that its automated products can make any website WCAG-compliant, unless it has the evidence to support such claims. The Department of Justice says automated checkers and overlays can be helpful tools but need to be used carefully. It adds that a “clean” report does not necessarily mean everything is accessible.
What did the FTC say accessiBe claimed about accessWidget?
The FTC says accessiBe claimed accessWidget can make any website compliant with WCAG. The complaint says accessiBe claimed that installing “one line of code” makes a website compliant with 30% of WCAG’s requirements immediately. It adds that accessiBe claimed an AI process makes the website fully compliant with the remaining 70% within 48 hours, and promised a re-scan every 24 hours.
Did accessiBe admit that accessWidget failed to make websites compliant?
The January press release presents that as an allegation: according to the complaint, accessWidget did not make all user websites WCAG-compliant. In the consent agreement, the Respondents state that they neither admit nor deny the allegations, except as the order specifically states. They admit the facts necessary to establish jurisdiction, only for purposes of this action.
Does the FTC order apply to a business that installs a widget?
The order defines “Respondents” as accessiBe Ltd. and accessiBe Inc., and their successors and assigns. Provisions I to V also reach the people the order lists as acting for them, and other persons in active concert or participation with them who receive actual notice. Purchasers or subscribers to accessWidget appear in one provision, on customer information for consumer redress.
How much does the FTC order require accessiBe to pay?
The order requires accessiBe to pay the Commission $1,000,000.00 within 8 days of the effective date. The January press release says the money may be used to provide refunds to consumers.
Sources
All read on November 13, 2026. From the Federal Trade Commission (FTC), on ftc.gov. FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines (press release, January 3, 2025). FTC Approves Final Order Requiring accessiBe to pay $1 Million (press release, April 22, 2025). A million-dollar blunder: How the FTC’s settlement with software provider accessiBe can help your business avoid similar missteps (business blog, April 23, 2025). Complaint and Decision and Order (docket C-4817, issued April 21, 2025). From the W3C Web Accessibility Initiative: Selecting Web Accessibility Evaluation Tools (updated May 13, 2024). From the Department of Justice’s ADA.gov: Guidance on Web Accessibility and the ADA (March 18, 2022).