The web accessibility industry is undergoing a significant shift. After years of overlay widgets being marketed as one-click compliance solutions, a growing body of evidence and legal action is driving the industry toward more substantive approaches. Here’s what’s happening and what it means for your WordPress site.
The Promise vs the Reality
Accessibility overlays have been marketed with compelling promises: add a single line of JavaScript and your site becomes accessible. AI-powered remediation handles everything automatically. Compliance in minutes, not months.
The reality is more nuanced. Overlays operate at the browser rendering layer, applying CSS modifications and JavaScript enhancements on top of your existing code. This can improve the visual experience for some users — larger text, higher contrast, modified colors — but it doesn’t address the underlying markup issues that assistive technologies rely on.
What Overlays Can’t Fix
Several categories of accessibility issues exist in your HTML source code and can only be truly fixed by modifying that code:
- Missing alt text on images: Screen readers need alt attributes in the HTML. An overlay can attempt to generate descriptions at runtime, but the results are inconsistent and the underlying HTML remains unchanged.
- Heading hierarchy: If your page jumps from H1 to H4, that structure is in your HTML. An overlay can visually restyle headings but doesn’t change their semantic level for assistive technology.
- Form labels: Unlabeled form inputs need actual
<label>elements or ARIA attributes in the markup. Runtime JavaScript can attempt to associate labels, but this is fragile and doesn’t always work across all assistive technology combinations. - Keyboard navigation: Proper focus management, tab order, and keyboard interaction patterns need to be built into your site’s code and components.
- Complex widgets: Modals, carousels, dropdown menus, and custom components need proper ARIA roles, states, and properties baked into their implementation.
The Legal Landscape
The legal environment is making the limitations of overlays harder to ignore:
- In 2024, the FTC fined accessiBe $1 million for deceptive marketing claims about their overlay’s compliance capabilities
- Multiple ADA lawsuits have been filed against websites using overlay products, with courts finding that overlays alone don’t satisfy accessibility requirements
- The European Accessibility Act (EAA), effective June 2025, requires substantive compliance that overlay presentation changes may not satisfy
This doesn’t mean overlays are illegal or useless. It means relying solely on an overlay as your accessibility strategy carries risk.
What Actually Works
Effective accessibility combines multiple approaches:
- Identify real issues: Use scanning tools that analyze your actual HTML and flag specific problems (missing alt text, heading order, contrast failures, form labels)
- Fix the code: Address issues in your source markup, templates, and content — not just at the presentation layer
- Provide visitor controls: Accessibility toolbars let visitors customize their experience for their specific needs, complementing (not replacing) good underlying code
- Monitor continuously: Content changes regularly. Automated scanning catches regressions before they become complaints
- Test with real users: Automated tools catch roughly 30-50% of accessibility barriers. Manual testing and user feedback are essential for the rest
Where EASWP Fits
EASWP combines a visitor-facing accessibility toolbar (similar to what overlays provide) with a WordPress-native scanner and fix engine (what overlays don’t provide). The scanner finds issues in your real code. The AI fix engine (Pro) suggests actual code changes you can review and apply. The toolbar gives visitors immediate customization options while you work on improving the underlying code.
It’s not a silver bullet — no tool is. But it addresses both the immediate visitor experience and the underlying code quality that matters for lasting accessibility and compliance.
Learn more about EASWP’s approach →