In June 2024, a small dermatology practice in New York City filed a class action lawsuit that sent shockwaves through the accessibility overlay industry. Tribeca Skin Center had paid AccessiBe $490 annually for their "AccessWidget" overlay, trusting the company's promises of automatic ADA compliance. Despite the overlay being installed and active, they were sued in January 2024 for ADA violations. The subsequent legal battle revealed what accessibility professionals have been saying for years: overlays don't fix accessibility problems—they mask them.
The AccessiBe Reckoning: $1 Million FTC Fine
The Tribeca case was just the beginning. In April 2025, the Federal Trade Commission took unprecedented action, fining AccessiBe $1 million for false advertising. The FTC's investigation found that AccessiBe's claims about automatic WCAG compliance were "not supported by competent and reliable evidence."
But the numbers tell an even starker story. According to UsableNet's 2024 litigation report:
- Over 800 businesses were sued for ADA violations in 2023-2024 while running overlay widgets from AccessiBe, UserWay, and similar vendors
- 25% of all ADA lawsuits in 2024 explicitly cited overlay widgets as barriers rather than solutions
- Businesses with overlays were disproportionately targeted for litigation
These aren't businesses that ignored accessibility. They paid for solutions, installed code, displayed compliance badges—and got sued anyway. The pattern is consistent: plaintiff attorneys test websites using actual screen readers, document specific WCAG failures, and file complaints citing the ADA. The overlay's presence doesn't matter if the underlying issues remain unfixed.
Why Overlays Fail: Technical Reality vs. Marketing Promises
Accessibility overlays operate by injecting JavaScript into a website after the page loads. This fundamental approach contains inherent limitations that no amount of AI or machine learning can overcome:
Screen Reader Timing Issues
Screen readers parse the Document Object Model (DOM) when the page loads, before overlay JavaScript executes. By the time the overlay attempts its "fixes," assistive technology users have already encountered the barriers. As disability rights attorney Lainey Feingold noted in her analysis of the AccessiBe case, overlays "not only fail to provide the promised compliance but may also impede accessibility by interfering with necessary assistive technologies."
Semantic Structure Can't Be Retrofitted
Proper accessibility begins with semantic HTML structure—using <button> elements for buttons, <nav> for navigation, and <main> for main content. This semantic meaning is baked into the markup and cannot be convincingly added after the fact through JavaScript manipulation. When a <div> is styled to look like a button, no overlay can give it the full semantic and behavioral properties of a true button element.
Context-Dependent Solutions
Real accessibility requires understanding user intent and business context. A modal dialog on an e-commerce checkout has different accessibility requirements than one displaying educational content. Overlays apply generic solutions that often conflict with the specific needs of different interface patterns.
The Legal Landscape: Courts Aren't Fooled
Legal outcomes consistently demonstrate that overlays provide no meaningful protection. In the Tribeca case, the business was forced to:
- Pay $4,000 in attorney fees
- Pay an additional $3,500 to a website remediation company for manual fixes
- Settle the accessibility claim despite having the overlay installed
The lawsuit's detailed allegations reveal the gap between AccessiBe's marketing promises and reality:
"Despite AccessiBe's claims that its widget would make their website fully ADA compliant, a manual audit identified dozens of WCAG AA failures that the automated overlay completely missed."
This pattern repeats across hundreds of cases. The data is clear: businesses using overlays are not only failing to prevent lawsuits—they're becoming targets.
What Actually Works: Foundational Accessibility Thinking
Real accessibility begins at the design stage, not as an afterthought. Here's what actually prevents lawsuits and creates usable experiences:
Semantic HTML from Day One
Every interactive element should use appropriate HTML elements with proper semantics. This means:
- Forms using
<label>elements properly associated with<input>fields - Navigation wrapped in
<nav>elements with descriptive landmarks - Heading hierarchies that create logical document outlines
- Interactive elements that can be operated via keyboard
Manual Testing with Real Users
Automated tools can catch approximately 30% of accessibility issues. The remaining 70% require human judgment:
- Keyboard navigation testing across all interactive elements
- Screen reader testing with actual assistive technology
- Color contrast verification in different lighting conditions
- Form usability with error states and recovery paths
Continuous Integration
Accessibility isn't a one-time project—it's an ongoing commitment that requires:
- Developer training on accessibility best practices
- Design system components built with accessibility baked in
- Regular audits as content and functionality evolve
- User feedback channels for people with disabilities
The Business Case Beyond Compliance
The businesses I work with discover that foundational accessibility thinking delivers benefits that extend far beyond lawsuit prevention:
- Better SEO: Semantic HTML structure improves search engine understanding and ranking
- Improved usability for everyone: Clear navigation and well-structured forms benefit all users
- Mobile performance: Accessible markup typically renders faster on mobile devices
- Future-proofing: Well-structured content adapts better to new devices and browsing contexts
Moving Forward: Questions to Ask
If you're currently using an accessibility overlay, or considering one, here are the critical questions to ask:
- Can the solution be tested? True accessibility can be verified through manual testing with assistive technology. If a solution can't be tested, it can't be trusted.
- Does it address root causes? Accessibility issues stem from design and development decisions. Solutions that don't address these root causes provide only cosmetic changes.
- What happens when it fails? Overlays create a single point of failure. When they break, malfunction, or conflict with other code, the underlying accessibility issues remain.
- Who takes legal responsibility? Despite marketing promises, overlay vendors typically disclaim responsibility for legal outcomes in their terms of service.
The Path Forward
The AccessiBe litigation and FTC action mark a turning point in how the market treats accessibility shortcuts. Organizations serious about accessibility—and about avoiding legal risk—are moving away from overlay solutions toward comprehensive, foundational approaches.
This isn't just about compliance. It's about building digital experiences that work for the 70+ million Americans with disabilities who represent a trillion-dollar market. Overlays don't unlock this market. Accessible code does.
The businesses that understand this distinction—that invest in semantic HTML, manual testing, and continuous improvement—aren't just avoiding lawsuits. They're building better products for everyone.
If your organization is currently using an accessibility overlay and wants to transition to a foundational approach, or if you're facing accessibility litigation, I can help. My work focuses on manual audits, semantic HTML remediation, and building systems that work reliably with assistive technology. Schedule a consultation to discuss your specific situation.