The Scheme: Selling Access That Didn’t Exist

accessiBe built its business on a single pitch: install accessWidget on your website, and any disabled person, whether they rely on a screen reader, keyboard navigation, or contrast adjustments, can use it. The company pointed to the Web Content Accessibility Guidelines, known as WCAG, a comprehensive technical standard that determines whether a website is genuinely accessible. accessiBe told businesses their software guaranteed full WCAG compliance.

According to the FTC’s proposed complaint, that claim was false. accessWidget did not make all websites WCAG compliant. The Federal Trade Commission concluded the company’s representations were “false, misleading, or unsubstantiated.” Businesses bought the plugin in good faith, believed their sites were accessible, and disabled users continued to hit barriers the software was supposed to eliminate.

The FTC also found that the software failed to address third-party web domains or subdomains that form part of a website’s overall experience, meaning a disabled user could encounter inaccessible components even on a site that had paid for the product. This limitation was never disclosed to customers before they paid.

They Hid the Fine Print Until After You Paid

The FTC’s proposed order specifically requires accessiBe to disclose, clearly and before any financial obligation, that its products cannot fix accessibility barriers on third-party domains or subdomains that may be part of the customer’s website. That disclosure didn’t exist before the FTC stepped in. Businesses were buying a compliance promise that came with hidden asterisks they were never shown.

The new prohibitions under the consent order spell out exactly what accessiBe was doing before it got caught. Provision I bars the company from claiming its AI or automated tools can make any website WCAG compliant unless it has “competent and reliable evidence” to back that up. The fact that this prohibition had to be written into law tells you everything about what the company had been doing without it.

The Paper Trail: A Timeline of Deception

The Fake Review Factory: How They Laundered Credibility

accessiBe didn’t just lie about what its product could do. The company built an infrastructure of manufactured trust. It paid publishers to write articles and reviews about accessWidget, then formatted those pieces to look like the independent, objective opinions of unaffiliated journalists and reviewers. Readers had no idea the author had a financial relationship with the company being praised.

The FTC’s proposed complaint found this tactic to be false and misleading on two levels. First, the content itself misrepresented the nature of the endorsement. Second, accessiBe never disclosed its “material connections” to those publishers. Under FTC rules, paying someone to say your product is great is advertising, and advertising must be labeled as such. accessiBe skipped that part.

This was a deliberate strategy to exploit the trust readers place in editorial content. A person with a disability searching online for honest reviews of accessibility tools would land on one of these articles and have no way of knowing they were reading a paid advertisement dressed up as a consumer report. The deception targeted the very people the product claimed to serve.

The “Impartial Author” Illusion Was the Whole Point

The FTC’s Provision III makes explicit what the company was doing: accessiBe misrepresented that its paid endorsers were “independent or ordinary users” of the product, or that they were “independent organizations providing objective information.” The company manufactured the appearance of a neutral, trustworthy marketplace of opinions. There was nothing neutral about any of it.

Provision IV now requires accessiBe to disclose “clearly and conspicuously, and in close proximity” to any endorsement, any unexpected material connection the endorser has to the company. That disclosure requirement didn’t exist in practice before the FTC acted. The company built its reputation on reviews that were, in the FTC’s plain language, deceptive.

The Math of Impunity: Fine vs. What Compliance Actually Costs

The Non-Financial Ledger: What Money Can’t Measure

The FTC’s $1,000,000 ($1,000,000 enough to pay the annual salaries of roughly 14 entry-level disability services workers) settlement sounds like accountability. It is a transaction. What it cannot price is the specific harm that flows from selling a lie to the people least equipped to absorb it. Disabled internet users were not incidental casualties of accessiBe’s fraud. They were the stated reason the product existed, which makes the betrayal structural, not accidental.

When a business installs accessWidget and believes its legal obligations under accessibility law are satisfied, the business stops looking for real problems. A blind user relying on a screen reader, a deaf user needing captions, a user with a motor disability who navigates by keyboard alone: each of those people encounters a wall the business believes isn’t there. The software’s failure doesn’t just inconvenience. It erases. It tells the user, through every broken interaction, that they were not considered worth the effort of genuine compliance.

The fake review ecosystem made this worse in a specific way. Disabled people and disability advocates who searched for honest guidance on accessibility tools were met with paid content designed to look like peer research. The decision to buy accessWidget was often framed as the responsible, community-serving choice. Organizations that trusted those reviews, including nonprofits, healthcare providers, and educational institutions that serve disabled populations, were misled by content that weaponized the appearance of advocacy journalism.

There is a compounding indignity here that the settlement dollar figure cannot capture. Accessibility is already treated as an afterthought by most of the digital economy. Disabled people have spent decades fighting for the basic right to use the same internet everyone else uses. accessiBe entered that fight not as an ally but as a company that harvested the urgency of that struggle to sell a product that, according to federal regulators, didn’t deliver on its core promise. The dignity loss is the loss of a safe place to trust: the loss of believing that a tool built for your community was actually built for your community.

The 20-year duration of the consent order is a quiet acknowledgment of how serious the FTC considered this conduct to be. Twenty years is not a slap on the wrist timeline. But for every disabled person who hit a broken link, a non-navigable form, or an inaccessible PDF on a site that thought it was covered, no part of that consent order delivers restoration. The harm already happened. The audit already wasn’t done. The complaint was already filed and dismissed as a user error. That is the ledger the settlement doesn’t touch.

The FTC’s action also exposes a broader structural failure. The existence of a market for fake compliance tools is itself evidence that the web accessibility ecosystem has not generated sufficient accountability for businesses that ignore genuine accessibility standards. accessiBe filled that gap with a product the FTC says was built on false claims, and the market rewarded it until a regulator intervened. The disabled community deserved better infrastructure than a consent order.

Legal Receipts: Straight from the Government’s Mouth

“The proposed complaint alleges that accessWidget did not make all websites WCAG compliant, and that the company’s claims were false, misleading, or unsubstantiated.” FTC Analysis of Proposed Consent Order, Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156

“Formatting the third-party articles and reviews as independent opinions by impartial authors and publishers was false and misleading, and accessiBe’s failure to disclose its material connections with the publishers of those articles was deceptive.” FTC Analysis of Proposed Consent Order, Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156

“Provision III prohibits accessiBe from misrepresenting that statements made in third-party reviews, articles, or blog posts about its automated products are independent opinions by impartial authors; that an endorser is an independent or ordinary user of the automated product; or that the endorser is an independent organization or is providing objective information.” FTC Analysis of Proposed Consent Order, Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156

“Provision V requires accessiBe to disclose, in connection with representations that accessWidget or the company’s other artificial intelligence or automated products correct accessibility barriers on a website, that such products or services will not correct barriers on third-party web domains or subdomains that may be part of the overall user experience, unless those domains also use the product. Such disclosure must be made Clearly and Conspicuously, and prior to the consumer incurring any financial obligation.” FTC Analysis of Proposed Consent Order, Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156

“Provision I prohibits accessiBe from representing that its automated products, including accessWidget’s artificial intelligence and other automated technology, can make any website WCAG compliant, or can ensure continued compliance with WCAG over time as web content changes, unless the company has competent and reliable evidence to support the representations.” FTC Analysis of Proposed Consent Order, Matter of accessiBe Inc. and accessiBe Ltd., File No. 222-3156

Societal Impact Mapping: Who Actually Paid the Price

Public Health: Inaccessible Healthcare Websites Have Real Consequences

WCAG compliance is not an abstract technical standard. For millions of Americans with disabilities, it determines whether they can book a medical appointment online, access their health records through a patient portal, or navigate the website of a pharmacy to request a prescription refill. When businesses relied on accessWidget’s false compliance claims, healthcare-adjacent websites believed themselves covered while disabled patients continued to face barriers to basic health information and services.

The FTC’s finding that accessWidget failed to correct barriers on third-party subdomains compounds this problem. A hospital’s main website might use the plugin. The patient portal, hosted on a subdomain or third-party platform, would remain inaccessible. The business believed it was compliant. The patient with low vision or motor impairment trying to log in at 11pm faced the same locked door they always had. accessiBe’s software gave institutions a false sense of legal safety while doing nothing for the user on the other end of the screen.

Economic Inequality: The People Who Can Least Afford to Be Scammed Were Scammed

Disabled Americans face significantly higher rates of unemployment and poverty than the general population. The internet is not optional for people navigating government benefit applications, remote work opportunities, accessible banking, or online education. Every website that falsely believed it was WCAG compliant because of accessWidget represented another digital door slammed on a population that already faces structural economic exclusion.

Small businesses and nonprofits that serve disabled communities were also among the buyers of accessWidget. These organizations, often operating on thin margins, paid for a product they were told would handle their legal accessibility obligations. The FTC’s finding that the product’s claims were unsubstantiated means those organizations spent real money and received false assurance. Their budgets absorbed the cost. Their clients absorbed the broken experience.

The fake review apparatus specifically targeted people doing research before spending money. For a small organization with limited technical staff, a credible-looking independent review on a third-party website can be the entire basis for a purchasing decision. accessiBe manufactured that credibility. The downstream cost of that manufactured trust fell on the organizations that bought the product and the disabled people those organizations were supposed to be serving.

The “Cost of a Life” Metric

What Now? Here Is Where You Apply Pressure

Leadership and Corporate Accountability

The consent order covers both accessiBe Inc. and accessiBe Ltd. (collectively identified in FTC File No. 222-3156). Specific executive names are not listed in the source document. Principals, officers, and employees of accessiBe are required under Provision IX to receive and sign acknowledgment of the consent order. That means the people running this company know what was found and are legally on the hook to comply.

Regulatory Watchlist

• Federal Trade Commission (FTC): File a complaint at ftc.gov/complaint if you purchased accessWidget based on WCAG compliance claims that proved false.
• Department of Justice (DOJ) Civil Rights Division: Responsible for enforcing the Americans with Disabilities Act, including web accessibility requirements.
• Department of Education Office for Civil Rights: Relevant for any educational institution that relied on accessWidget to satisfy accessibility obligations.
• Consumer Financial Protection Bureau (CFPB): Relevant if financial services companies used accessWidget to falsely represent ADA/digital accessibility compliance.
• State Attorneys General: Many states have consumer protection laws that mirror or exceed FTC standards. File state-level complaints if you were harmed in your state.

Grassroots Resistance and Mutual Aid

The disabled community has been doing the work of holding the digital world accountable long before the FTC showed up. Organizations like the National Federation of the Blind, the American Foundation for the Blind, and local disability rights coalitions have the knowledge and the networks to push back. Support them with money if you have it, time if you don’t, and noise always. If you run a website, commission a real manual WCAG audit from a certified accessibility professional. Do not outsource civil rights to an AI plugin. The fix for fake compliance is actual compliance: slow, unglamorous, and human.