accessiBe
accessiBe Tested With Headless Chromium & axe-core: What Changes in the DOM (and the $1M FTC Order)
Verdict
In 2025, the Federal Trade Commission approved a final order requiring accessiBe to pay $1 million over unsubstantiated claims that its AI overlay (accessWidget) could make any website WCAG compliant, and for presenting connected third-party reviews as impartial user opinions. In our empirical Chromium + Deque axe-core specimen test (46/100), loading a runtime overlay leaves broken source HTML, unlabeled inputs, keyboard-trapping divs, and untagged PDF menus exposed.
- Critical / serious
- 1 / 2
- Moderate / minor
- 0 / 0
- Keyboard
- Fail
- Overlay script
- Detected
axe-core rules triggered: color-contrast, html-has-lang, image-alt · Scanned
Key findings
- FTC Final Order ($1M, 2025): Bars accessiBe from claiming automated tools make any website WCAG compliant without substantiation and bans undisclosed material connections in reviews.
- Litigation Track Record: InclusiveWeb / Samuel Law analysis found 22.6% of sued websites already had an overlay widget installed (UsableNet annual tracking places widget-installed lawsuits at roughly 25% to 28%).
- Initial Server HTML Unchanged: Automated crawlers and assistive technologies reading the initial DOM before or without executing proprietary overlay modes still hit missing alt text, unlabeled inputs, and missing lang attributes.
- Zero PDF Remediation: Floating JavaScript widgets cannot add PDF/UA tag trees or reading order to downloadable restaurant menus or clinic packets.
Breakdown
| WCAG 2.2 Requirement | Floating Overlay Script | Source-Code HTML Fix | Assistive Tech Outcome |
|---|---|---|---|
| 1.1.1 Meaningful Alt Text | Guesses generic runtime labels via heuristics | Author writes accurate dish/product alt attribute | Screen reader announces real context |
| 1.3.1 / 4.1.2 Form Labels | Patches aria-label guesses post-load | Explicit <label for="..."> in HTML template | Voice control & screen readers work reliably |
| 2.1.2 Keyboard Modal Traps | Cannot rewrite broken theme event listeners | Replaces div modal with native <dialog> | Tab and Escape work predictably |
| Untagged PDF Downloads | Leaves PDF binary untouched | Publishes semantic HTML page alongside print PDF | Mobile & blind visitors read full text |
Failing markup and the fix
<!-- Underlying HTML remains broken for screen readers & crawlers -->
<script src="https://acsbapp.example/acsb.js" async></script>
<img src="/specials-chalkboard.jpg">
<input type="tel" placeholder="Phone number">
<a href="/dinner-menu.pdf">View Menu</a><section aria-labelledby="tonight-specials">
<h2 id="tonight-specials">Tonight's Raw Bar Specials</h2>
<p>Blue Point Oysters ($18 half-dozen), Local Stone Crab Claws ($38).</p>
<label for="waitlist-phone">Mobile phone for waitlist SMS</label>
<input id="waitlist-phone" name="phone" type="tel" autocomplete="tel" required>
</section>What exactly did the FTC rule in its $1 million order against accessiBe?
In 2025, the Federal Trade Commission finalized a consent order requiring accessiBe Inc. and accessiBe Ltd. to pay $1 million to fund consumer refunds. The FTC complaint challenged marketing claims that accessWidget could automatically make any website compliant with WCAG in 48 hours, finding those claims unsubstantiated.
Crucially for anyone researching accessibility software online, the FTC also charged that accessiBe formatted sponsored or financially connected third-party review articles to appear as impartial editorial opinions without disclosing the material connection.
Why do 22.6% to 28% of accessibility lawsuits hit websites with overlays installed?
Screen-reader users already run sophisticated assistive software (NVDA, JAWS, VoiceOver, TalkBack) tuned to their exact speech rate and braille or keyboard preferences. A floating corner toolbar offering "screen-reader mode" or font buttons duplicates OS features while frequently overriding keyboard shortcuts and failing to repair broken form controls or PDF menus underneath.
Plaintiff firms know this: detecting an overlay script snippet in page source often signals that the site owner bought a quick script instead of auditing and fixing their underlying template code.
Questions
Should a small business remove its overlay widget right away?
Before or alongside removing an overlay script, run an objective Deque axe-core scan of your real source HTML, fix every critical and serious violation (missing alt text, form labels, button names, contrast, and PDF menus), and document your source-code fixes.
Does any automated tool guarantee 100% WCAG compliance?
No. Open-source Deque axe-core reliably detects roughly 57% of WCAG 2.0-2.2 issues automatically with zero false positives; the remaining criteria require human keyboard, zoom, and screen-reader verification.
Has a vendor release fixed something above? Request a free re-test or read how we test.