A11y Suite vs accessiBe — honest comparison

This is an honest, citation-backed comparison. We’re not going to pretend overlay
products are competitive — they aren’t, and the FTC formally agreed in January 2025.
If you’re a procurement officer or compliance manager, this is the page to forward
to legal.

The short version

accessiBe and similar overlay products do not remediate
accessibility. They inject a widget that pretends to. The FTC fined accessiBe
$1 million in January 2025 for making compliance claims it couldn’t back up.

A11y Suite is the opposite approach: real code-level fixes (CSS / JS / ARIA / DOM)
stored in your WordPress database, fully revertable, plus a paper trail your
counsel can defend in court.

Capability-by-capability

Why overlay products fail (the technical reason)

Overlays inject a JavaScript file that runs in the visitor’s browser. They try to
“fix” accessibility issues at runtime by manipulating the DOM. Three problems:

1. Screen readers see the unmodified page first. Most screen readers
   cache the DOM before overlay JS runs. So announcements are wrong. Assistive tech
   users get the original broken markup, not the “fixed” one.
2. They don’t fix the actual code. When the user disables JavaScript
   (common for performance or privacy), the site is exactly as broken as it was. No
   durable improvement.
3. They generate fake compliance claims. Many overlay vendors hand
   customers a “certificate” or trust seal. That language (“100% WCAG compliant”,
   “lawsuit-proof”) is exactly what the FTC fined accessiBe for using.

What the disability community says

700+ accessibility professionals signed the Overlay Fact Sheet,
documenting that overlays do not solve accessibility and frequently make it worse.
The list includes engineers from Adobe, Deque, Microsoft, Mozilla, and the W3C.

“Web accessibility overlay products misrepresent their capabilities. They cannot
remediate without manual changes to source code… many disabled users find overlays
more harmful than the underlying inaccessible site.”

— Overlay Fact Sheet (2024)

The legal context

On 9 January 2025, the U.S. Federal Trade Commission announced a $1 million
settlement with accessiBe over deceptive marketing. Specifically: the company
was banned from claiming its software made any website WCAG-compliant, and from
suggesting that buying their product would protect customers from ADA lawsuits.

Sources:

• FTC press release (Jan 2025)
• FTC case docket
• Overlay Fact Sheet (community)
• WCAG 2.1 official spec (W3C)

What A11y Suite does differently

We approach accessibility the way Yoast approaches SEO — as a continuous
remediation workflow that lives inside your CMS, not as a magic widget:

• Every fix is a real CSS/JS patch stored in your WordPress
  database. Revertable in one click.
• Every fix is logged with timestamp, applier, and reason — usable
  as legal evidence of good-faith effort.
• The accessibility statement we generate uses “working toward”
  language. The Compliance Verification page actively scans your published claims
  for FTC-risky phrases.
• The VPAT 2.4 report is marked “DRAFT — requires IAAP-certified
  reviewer”. We never imply our automation replaces a credentialed audit.

“But the overlay was cheap and easy.”

Until the demand letter arrived. ADA serial-plaintiff law firms target sites with
overlay widgets specifically because the widget’s existence is now evidence of
trying to game compliance rather than fix it. Defending against an ADA lawsuit
costs $35,000-$75,000 on average. Settlement averages $25,000.

A11y Suite Pro is $49/year. The math is not subtle.

This page makes no claim that A11y Suite alone guarantees WCAG conformance or
ADA compliance. No software product can. A credentialed third-party audit
(e.g. WebAIM) remains the gold standard for legal certification.