Skip to content

accessiBe: owners, product claims, the FTC order and lawsuits

accessWidget: what accessiBe claimed and what tests and users reported

From 2019 accessiBe promoted accessWidget, a JavaScript overlay sold mostly at $49 a month, as making any site compliant with WCAG and the ADA within 48 hours and as protection against lawsuits, while its licence terms said installation could not guarantee that claims would not arise. A critic's tests found more WCAG violations with the overlay switched on, blind users described blocking it, and the WAVE checker warns that it may modify content during testing. In 2023 the company's founder said he was sure issues remained on sites using the overlay. The FTC's 2025 order bars unsubstantiated compliance claims, and the company's Litigation Pledge closed to new licences in July 2026.

published
17 oct 2026
records as of
10 oct 2026
entities
93
sources
129
cite entities.csv

the questionWhat did accessiBe claim accessWidget could do, and what do tests, users and the company's own terms say?

1The product, its price and its reach

analysisaccessWidget is a website "overlay": a JavaScript plug-in that adds an accessibility interface and automated adjustments to a customer's site. According to the FTC complaint most subscriptions are the Standard plan for sites under 1,000 pages at $49 a month or $490 a year, with Advanced ($1,490 a year), Advanced Plus ($3,490 a year) and custom Enterprise plans; each covers a single web domain, and agency partners get a 20% discount that they may pass on or keep as commission. In May 2020 an Israeli business newspaper described annual prices from $490 for up to 1,000 pages to $3,500 for up to a million pages, and the company said it sold mostly through partners such as RealPage, BigCommerce, Volusion, WebFX and Digital Ocean and through thousands of web agencies; the partnership terms are not in the record. 1 2 3

analysisThe company's figures for its installed base have varied with time and unit: more than 25,000 sites in May 2020, more than 132,000 websites in May 2021, 107,526 customers on its home page in October 2021, more than 160,000 sites in August 2022, 167,743 businesses in a home-page image reproduced in the FTC complaint, more than 247,000 sites as quoted in the 2024 class action, more than 100,000 websites in 2024 and more than 85,000 in August 2026. None of these company figures is audited, and the FTC exhibit figure comes from an image transcription. 2 4 5 6 7 8 9 1

sources in this section

  1. FTC complaint, In the Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156 (proposed consent package) U.S. Federal Trade Commission · 3 Jan 2025
  2. Media source · src-029 identified by category only · Media
  3. Company statement source · src-015 identified by category only · Company statement
  4. Research source · src-081 identified by category only · Research
  5. Media source · src-095 identified by category only · Media
  6. Media source · src-030 identified by category only · Media
  7. Court record source · src-058 identified by category only · Court record
  8. Company statement source · src-007 identified by category only · Company statement
  9. Company statement source · src-033 identified by category only · Company statement

2Compliance claims

analysisFrom 2019 accessiBe promoted the product as an automatic route to legal compliance. An August 2019 Facebook post said its AI "solves web accessibility issues on every website"; the May 2020 announcement said the AI-based solution automatically made sites compliant with WCAG and the ADA, with Shir Ekerling saying it could help businesses "comply with legislation and avoid lawsuits"; and a February 2021 release described technology that modifies websites in real time to comply with the ADA and WCAG 2.1. The best-known claim was a timetable: install "a single line of JS code", the interface appears at once, and within 48 hours the AI makes the site compliant, then re-scans it every 24 hours. A March 2021 marketing email set out these steps, the FTC complaint describes the claim as 30% of WCAG requirements met at once and 70% within 48 hours, and a company description still carried by a contact-data aggregator in September 2026 promised "ADA and WCAG 2.1 compliance within 48 hours"; these statements are known as reproduced by a critics' site, the FTC and the aggregator. The FTC later alleged that claims that accessWidget makes any website WCAG-compliant were false, misleading or unsubstantiated, and its April 2025 order prohibits such representations unless they are non-misleading and supported by competent and reliable evidence. accessiBe said in January 2025 that the complaint did not challenge its ability to bring customer sites into compliance with U.S. requirements. 1 2 3 4 5 6 7

analysisSnapshots of the company's own site record the wording. On October 20, 2021 the home page called accessiBe "The #1 Automated Web Accessibility Solution for ADA & WCAG Compliance", at $49 a month with a "2-minute installation for 24/7 automatic accessibility" and an "accessibility statement and certificate of performance"; on October 16, 2022 it said one line of JavaScript would make any website compliant with WCAG 2.1, ADA Title III, Section 508 and EN 301549 "in up to 48 hours"; and a February 2021 snapshot called accessiBe the only automatic AI solution "proven to make websites fully WCAG and ADA compliant and beat legal cases". These company statements were captured by a critics' site and quoted in the 2024 class action complaint. Commissioner Andrew Ferguson's January 2025 statement quotes accessiBe advertising accessWidget as "the #1 fully automated ADA and WCAG compliance solution", "always ensuring compliance by rescanning and re-analyzing your website every 24 hours". 1 8 9

sources in this section

  1. Research source · src-081 identified by category only · Research
  2. Company statement source · src-015 identified by category only · Company statement
  3. Company statement source · src-013 identified by category only · Company statement
  4. FTC complaint, In the Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156 (proposed consent package) U.S. Federal Trade Commission · 3 Jan 2025
  5. Other source · src-032 identified by category only · Other
  6. Media source · src-064 identified by category only · Media
  7. FTC Decision and Order, In the Matter of accessiBe Inc. and accessiBe Ltd., Docket No. C-4817 U.S. Federal Trade Commission · 21 Apr 2025
  8. Court record source · src-058 identified by category only · Court record
  9. Concurring Statement of Commissioner Andrew N. Ferguson, joined by Commissioner Melissa Holyoak, In the Matter of accessiBe, Inc. U.S. Federal Trade Commission · 3 Jan 2025

3Lawsuit protection and what the terms said

analysisaccessiBe also marketed protection from lawsuits. A January 2020 Google advertisement read "Avoid Lawsuits with Accessibe"; an October 2020 snapshot answered "Does accessiBe protect me from lawsuits? Absolutely!" and offered a Litigation Support Package; the 2021 FAQ said the accessibility statement and monthly audits should be "enough to stop any lawsuit"; and an August 2022 welcome email listed "Protection from accessibility lawsuits" and "Dedicated support for legal actions" among the benefits. These statements are quoted in court filings and on a critics' site. In 2021 Shir Ekerling wrote on LinkedIn that critics had never encountered a company "that got sued because of accessiBe", only companies that came to accessiBe with an existing legal situation, and in an August 2020 video, known only from Adrian Roselli's description, the chief executive said the company had obtained dismissals in customers' cases. In May 2023 Ekerling apologised to members of the National Federation of the Blind for "emphasizing our marketing on avoiding legal action", and in June 2023 he said such wording had been removed years earlier. 1 2 3 4

analysisThe licence terms, as quoted and read by Roselli in 2020 and 2021, said that installing the systems "cannot guarantee that claims will not arise" and does not on its own fulfil all legal accessibility requirements, defined the standard as WCAG 2.1 level AA and conditioned the systems' functionality on the customer's site already being coded to W3C standards without errors or validation warnings; Roselli concluded that the compliance promise applied only to sites that were already compliant, and the full terms of those years are not retained. accessiBe's Litigation Pledge page states that from July 15, 2026 the pledge is no longer available for new licences, while remaining in effect for eligible earlier ones; under it a customer may settle a covered claim without the company's consent, but unless accessiBe agrees the settlement must contain no findings against accessiBe or its products, must not disparage it and must stay confidential, and settlement amounts are not covered damages. Roselli also wrote in October 2023 that accessiBe's site had rewritten the U.S. tax authority's description of the disabled access credit to imply that its overlay was explicitly covered, omitting a qualifier on consulting services; that is a critic's comparison, and neither document of that time is retained. 2 5

sources in this section

  1. Court record source · src-058 identified by category only · Court record
  2. Research source · src-076 identified by category only · Research
  3. Research source · src-081 identified by category only · Research
  4. Company statement source · src-077 identified by category only · Company statement
  5. Company statement source · src-120 identified by category only · Company statement

4Tests and user reports

analysisAdrian Roselli, an accessibility consultant and critic of the company, reported in June 2020 that enabling the overlay on accessiBe's own AI page raised the WCAG violations found by Deque's Axe checker from 4 to 12 and by The Paciello Group's ARC from 19 to 38, and in January 2024 that its keyboard-navigation mode still introduced failures on a customer's site; these are a critic's tests, not an independent audit. In an August 2020 video reply, as Roselli describes it, the chief executive said the company was "very much aware" that such tools find more errors with accessiBe and attributed this to deliberate code changes. WebAIM's WAVE checker warns that the accessiBe integration "may temporarily modify content when WAVE is activated"; Roselli traced a function in the script that reacts to WAVE, and quotes WebAIM's June 2023 announcement that WAVE tells users that accessiBe and UserWay overlays may manipulate page content to suppress detection of errors. Roselli also summarised an April 2024 newspaper test in which the overlays of accessiBe, AudioEye, EqualWeb and UserWay each failed to remove testable errors, with accessiBe ranked worst, and a May 2023 Nielsen Norman Group study in which screen-reader users did not find the accessiBe and UserWay menus useful; neither the article nor the study is retained. 1 2 3

analysisIn a January 2021 WebAIM survey reported by a U.S. business magazine, 67% of web accessibility practitioners rated overlays as a product class "not at all" or "not very" effective, rising to 72% among respondents with disabilities. Blind users described accessiBe as an obstacle in 2021: one could reach a NameCheap account only after blocking accessiBe in the computer's hosts file, another found a blog post far easier to navigate with accessiBe disabled, and users shared the script's domains so that it could be blocked; these individual accounts are quoted by the Overlay Fact Sheet and Roselli. Shir Ekerling told a U.S. network news outlet in 2021 that critics rarely gave specifics and did not really test the product, and the chief marketing officer Roy Gefen said users could face a learning curve. At a February 2021 meeting with blind advocates, according to Roselli, a founder asserted that a silent majority of users were happy with accessiBe. In a June 2023 podcast, as transcribed by Roselli, Ekerling said he was "sure 100% that there are issues today with websites using the overlay" and that it was not a perfect solution, and in a 2020 video he acknowledged that three of seven points the company had presented as WCAG AA requirements should not have been tied to WCAG. 4 5 1 6

sources in this section

  1. Research source · src-076 identified by category only · Research
  2. Research source · src-081 identified by category only · Research
  3. Research source · src-115 identified by category only · Research
  4. Media source · src-116 identified by category only · Media
  5. Research source · src-075 identified by category only · Research
  6. Media source · src-095 identified by category only · Media

5JAWS, privacy and promotion

analysisIn 2019 accessiBe said it had developed the product with a developer from the team behind the JAWS screen reader: its chief executive said so in a video, a company knowledge-base post said development had worked "back to back with a developer from the JAWS team" for more than 18 months, and a representative repeated it in an August 2019 blog comment, as critics documented. In March 2021 Vispero/Freedom Scientific, the maker of JAWS, wrote to Roselli that "Neither Vispero nor any of its developers have ever worked with accessiBe relative to any products and services" and asked him to remove the reference. In July 2021 Roselli quoted the accessibility specialist Léonie Watson's concern that accessiBe's privacy policy would let it identify her as a person with a disability and link that to her name and other public information, and wrote that accessiBe had not answered her request for its data protection impact assessment; no regulator has addressed these concerns in the record. In June 2023 Ekerling said accessiBe knew nothing about those users, had never tracked any user, gathered user data or sold such information, and called the contrary claims untrue and misleading. 1 2

analysisCritics also questioned how accessiBe promoted itself. Roselli reported in 2020 that a June 2020 article in The Next Web on lawsuit risk, quoting the vice-president of marketing Yan Kotliarsky five times, carried a paid-content notice saying it was brought by ACE, an accessiBe product, and listed other favourable articles he considered paid; the chief executive replied, as Roselli describes it, that "companies do marketing" and that accessiBe partners with marketing agencies, while denying that it ever paid for tweets. Joe Dolson of the WordPress accessibility team reported in February 2021 that all 33 positive reviews on accessiBe's WordPress plug-in page were removed after he reported them; Roselli wrote that an online-encyclopedia article about accessiBe was flagged as spam in 2020 and its author blocked; a critic identified five sock-puppet accounts boosting accessiBe on Twitter in May 2023; and Roselli reported that accessiBe deleted critical comments under one of its articles, which the chief executive later attributed to its web host removing two comments it believed to be hate comments. These are critics' allegations, not findings of a court or regulator. 1

sources in this section

  1. Research source · src-076 identified by category only · Research
  2. Research source · src-062 identified by category only · Research

timeline · 2026

  1. Litigation Pledge closed to new accessWidget licences

cite this dossier

DossierTwist, “accessiBe: owners, product claims, the FTC order and lawsuits”, dt.005, 17 October 2026, https://dossiertwist.com/dossiers/accessibe/

Free to read, cite and republish with credit under CC BY 4.0: credit “DossierTwist” and link to the dossier.

Data: JSON, CSV and the network graph.

We listen to all sides: responses are shown next to the claims they answer. To send a correction or a reply, write to dossiertwist@proton.me.