Why Websites With Accessibility Overlays Still Get Sued
Updated 2026-11-18 · Verified against WCAG 2.2 Level A & AA · Information, not legal advice
In 2025 the FTC ordered overlay vendor accessiBe to pay $1 million for deceptive compliance claims, and industry tracking shows 22.6% of sued websites already had an overlay toolbar installed. Overlays inject surface scripts after page load instead of repairing broken source HTML, form labels, or PDF menus.
| Accessibility Requirement | Floating Overlay Widget | AgileADA Source-Code Fix |
|---|---|---|
| Image & Menu Alt Descriptions | Guesses generic labels at runtime | Writes accurate dish/product alt text in HTML |
| Keyboard Trap in Promo Modal | Cannot rewrite broken theme JS traps | Replaces broken div popup with native <dialog> |
| Untagged PDF Menus & Intake Forms | Leaves PDF files untouched | Flags every .pdf link and provides HTML equivalents |
| Screen-Reader User Experience | Frequently conflicts with JAWS/NVDA/VoiceOver | Uses clean native HTML that assistive tech expects |
What did the FTC rule about automated compliance claims?
In 2025, the Federal Trade Commission finalized a $1 million order against overlay vendor accessiBe after finding that marketing claims promising automated WCAG compliance were unsubstantiated.
Blind visitors who already run dedicated screen readers like NVDA, JAWS, or Apple VoiceOver do not need a redundant font-sizer toolbar in the corner of your screen; they need valid buttons, labeled inputs, and descriptive alt text in your real HTML.
Keep Your Pages Monitored Automatically Every Monday
Stop worrying about silent WordPress plugin updates or seasonal menu uploads breaking WCAG 2.2 AA conformance. Plans start at $49/month with 1-click Stripe cancellation.