accessiBe AI Overlay: Automated Accessibility Compliance Claim Evidence Questions
Checked May 22, 2026
The FTC finalized a $1 million settlement finding accessiBe overstated what its AI overlay could do for web accessibility compliance. This case shows the evidence burden behind automated compliance claims.
What was claimed
accessiBe's AI-powered web overlay was marketed as capable of making any website compliant with accessibility standards — including WCAG — through automated means, without stated requirements for human review or ongoing maintenance.
Source and date
- Source
- FTC v. accessiBe Inc.
- Source type
- Regulator enforcement
- Source date
- April 22, 2025
- Checked date
- May 22, 2026
- Regulator or source
- FTC
Why this mattered
Claims that AI can fully automate compliance with an accessibility standard carry a high evidence burden. WCAG compliance involves criteria that automated tools cannot fully address without human judgment. Buyers relying on such claims without understanding coverage limits may face accessibility and regulatory risk if the automated tool does not cover the full standard.
Risk pattern
Automated compliance promise without stated audit method or human review boundary
Evidence gap
Which WCAG version and success criteria the tool covers, the audit method and test scope, which issues remain outside automated detection, what human review and testing remains necessary, and how the tool handles dynamic content, third-party scripts, or ongoing maintenance.
What the source said
The FTC found that accessiBe's claims that its overlay would make websites fully compliant with accessibility standards were not substantiated. The settlement required a $1 million payment and prohibited accessiBe from making unsubstantiated compliance claims.
Buyer questions
Ask these before relying on a similar claim from any vendor.
- Which WCAG version and success criteria does the tool cover through automation?
- Which accessibility issues remain outside the automated workflow and require human review and testing?
- Does the tool handle dynamic content, third-party scripts, and mobile accessibility?
- What ongoing maintenance is required after installation to maintain the coverage level claimed?
How this applies to your vendor evaluation
If a vendor you are evaluating makes a claim with this pattern, use the checker to review their specific wording against the evidence standard this case documents.
Wording boundary direction
Supports identification of some accessibility issues under [named WCAG version and criteria]; manual review, testing with assistive technologies, and ongoing maintenance remain necessary for accessibility compliance.
A lower-risk wording boundary narrows the scope, discloses the test conditions, and does not overstate what is covered.
Update and response status
Disclaimer
This case description draws from the FTC press release cited above. It is not legal advice, a compliance certification, or an accessibility audit.
This tool generates evidence-burden notes, evidence requests, and buyer questions based on publicly accessible source content. It does not determine whether a product is true, false, compliant, or suitable for any purpose. It is not legal, investment, procurement, or professional compliance advice. See the full disclaimer.
Check a vendor making a similar claim
Check a similar vendor claim →