Why Overlays Are "Like Putting a Post-it on a Bandit"

Covering problems isn't solving them.

The Overlay Problem

Understanding why overlay technology fails.

How Overlays Work (Technically)

Overlay widgets inject JavaScript into web pages after they load. The JavaScript attempts to modify the DOM (Document Object Model) to address accessibility issues—adding ARIA attributes, adjusting colors, changing focus behavior.

<!-- Original inaccessible code -->
<img src="product.jpg">
<a href="#">Click here</a>

<!-- Overlay's attempted "fix" (JavaScript injection) -->
<img src="product.jpg" aria-label="Product image">
<a href="#" aria-label="Click here link">Click here</a>

The underlying HTML remains unchanged. The JavaScript layer tries to patch over it.

Why This Approach Fails

The timing problem: Screen readers parse HTML before JavaScript executes. When a blind user visits an overlay site, their screen reader processes the original inaccessible code—not the JavaScript "improvements."

The detection problem: Overlays use automated detection that catches only 25-40% of accessibility issues. Complex issues requiring human judgment—context-appropriate alt text, logical reading order, meaningful link text—escape detection entirely.

The fix problem: Even for detected issues, JavaScript patches often fail. Injecting generic ARIA labels doesn't provide meaningful descriptions. Automated color adjustments may break design intentionally using specific palettes. Focus management patches create new issues.

The Post-it Analogy

When you put a post-it note on a mugshot, the bandit's face is still there. The post-it doesn't change who committed the crime—it just makes the photo less useful.

Overlays work the same way. The inaccessible code remains. The overlay just makes it harder to see while failing to address the actual problem.

The Evidence: Overlays Don't Work

Data and statements confirming overlay failure.

Lawsuit Statistics

Over 800 businesses running overlay widgets were sued for ADA accessibility violations in 2023-2024. These organizations paid for "accessibility solutions." They installed the JavaScript. They displayed compliance badges.

They still got sued because their sites remained inaccessible.

+------------+------------------------+-----------------------+
|    Year    |   Overlay Users Sued   |         Source        |
+------------+------------------------+-----------------------+
|    2023    |          400+          |   Industry research   |
+------------+------------------------+-----------------------+
|    2024    |          400+          |   Industry research   |
+------------+------------------------+-----------------------+
|   Total    |          800+          |    Documented cases   |
+------------+------------------------+-----------------------+

FTC Action

In April 2025, the FTC fined AccessiBe $1 million for deceptive marketing practices. The settlement found that AccessiBe's claims about WCAG compliance and ADA protection were "not supported by competent and reliable evidence."

The federal government officially confirmed what accessibility experts had been saying: overlay compliance claims are false.

Disability Community Position

> "The National Federation of the Blind, the oldest and largest organization of blind people in the United States, condemns the use of automated web accessibility overlays and calls on companies to stop deploying them."

The people overlays claim to help explicitly reject overlay technology.

Technical Expert Analysis

Web accessibility experts and practitioners consistently document overlay failures.

Adrian Roselli, recognized accessibility expert: "Overlays, as a class, have been around for years and are not a viable solution. They fail users who rely on assistive technology."

The Overlay Fact Sheet, signed by hundreds of accessibility professionals, documents technical failures and recommends against overlay use.

Real Impact: Who Overlays Harm

Understanding the human cost of overlay deployment.

Blind and Low Vision Users

Screen reader users encounter overlays differently than overlay vendors expect. Common experiences include overlay widgets themselves being inaccessible, forced interactions with unwanted "accessibility" features, underlying issues remaining unfixed, and confusion about what features actually exist.

Users with Motor Disabilities

Keyboard-only users often find overlays introduce new barriers rather than removing them. Custom focus management breaks expected navigation. Overlay controls require unexpected interactions. Keyboard traps appear where none existed before.

Users with Cognitive Disabilities

Overlays add interface complexity. Additional widgets, settings panels, and feature options create cognitive load. Users seeking simple, clear interfaces encounter cluttered additions.

All Users

Overlay JavaScript adds page load time. Performance impact affects everyone. For users on slow connections or older devices, overlays make sites slower without making them more accessible.

The Business Impact

How overlays fail organizations deploying them.

No Lawsuit Protection

The 800+ businesses sued while using overlays learned the hard way: overlay compliance claims don't provide legal protection.

Plaintiff attorneys test sites with actual screen readers. They document actual accessibility failures. The overlay's presence doesn't change their findings. In some cases, the overlay's compliance badge is cited as evidence that the organization knew about accessibility requirements and chose an inadequate solution.

Wasted Investment

Organizations pay $500-$6,000+ annually for overlays. They get no protection, no compliance, and no accessibility. The investment produces nothing of value while creating false confidence.

Brand Damage

The accessibility community knows overlays don't work. When users with disabilities encounter overlay widgets, many recognize them as inadequate solutions. This recognition damages brand perception among the exact audience overlays claim to serve.

Technical Debt

Overlays can conflict with legitimate accessibility improvements. When organizations later attempt proper remediation, they must work around overlay interference. The overlay becomes technical debt that costs additional money to remove.

The Alternative: Source Code Remediation

What actually works.

How Source Code Remediation Works

Source code remediation fixes accessibility issues in actual HTML, CSS, and JavaScript. When screen readers parse the page, they encounter accessible code from the start.

<!-- Before remediation -->
<img src="product.jpg">

<!-- After source code remediation -->
<img src="product.jpg" alt="Blue cotton t-shirt with crew neck, shown on model">

No JavaScript timing issues. No detection gaps. No patches over patches.

Why It Works

+------------------------+-----------------------+--------------------------+
|         Factor         |        Overlays       |       Source Code        |
+------------------------+-----------------------+--------------------------+
|    When accessible     |   After JS executes   |       Immediately        |
+------------------------+-----------------------+--------------------------+
|      What changes      |      DOM overlay      |       Actual code        |
+------------------------+-----------------------+--------------------------+
|   Detection coverage   |         25-40%        |   99%+ (expert review)   |
+------------------------+-----------------------+--------------------------+
|     Customers sued     |          800+         |      0 (TestParty)       |
+------------------------+-----------------------+--------------------------+

TestParty's Approach

TestParty combines AI detection (Spotlight) with expert source code remediation. Findings feed directly into fixes. Fixes arrive as GitHub PRs. Your site's actual code becomes accessible.

No post-it notes. Real solutions.

Making the Switch

Moving from overlay to actual accessibility.

If You Currently Use an Overlay

You're not alone—many organizations chose overlays based on convincing marketing. The path forward is straightforward.

Immediate actions:

1. Stop relying on overlay for compliance claims
2. Remove overlay compliance badges (they invite scrutiny)
3. Assess actual accessibility state (overlay masked issues)
4. Plan source code remediation

The Transition Timeline

Week 1: Remove overlay. Run comprehensive accessibility scan (TestParty Spotlight or similar). Understand actual state.

Weeks 2-3: Expert remediation addresses findings. Source code fixes delivered via GitHub PRs.

Week 4: Compliance achieved. Continuous monitoring begins.

Timeline: 14-30 days from overlay to compliance.

Cost Comparison

+------------------------+----------------------------+---------------------+
|         Factor         |          Overlay           |      TestParty      |
+------------------------+----------------------------+---------------------+
|      Monthly cost      |          $49-$500          |    $1,000-$5,000    |
+------------------------+----------------------------+---------------------+
|   Lawsuit protection   |       0% (800+ sued)       |   100% (<1% sued)   |
+------------------------+----------------------------+---------------------+
|   Actual compliance    |             No             |         Yes         |
+------------------------+----------------------------+---------------------+
|      FTC findings      |   Claims unsubstantiated   |         N/A         |
+------------------------+----------------------------+---------------------+

Frequently Asked Questions

Why are overlays compared to "putting a post-it on a bandit"?

Like covering a mugshot with a post-it, overlays hide accessibility problems without addressing them. The inaccessible code remains—overlays just add a JavaScript layer on top. Screen readers parse the original inaccessible HTML before overlay JavaScript executes. The "fix" never reaches users who need it. The underlying violation stays untouched.

Have businesses actually been sued while using overlays?

Yes—over 800 businesses using AccessiBe, UserWay, and similar overlays were sued for ADA violations in 2023-2024. The overlay's presence didn't prevent lawsuits because plaintiff attorneys test with actual screen readers and find actual violations. The FTC fined AccessiBe $1 million in 2025 for unsubstantiated compliance claims.

What does the disability community say about overlays?

The National Federation of the Blind explicitly condemns overlays, stating they "harm more than they help." Hundreds of accessibility professionals signed the Overlay Fact Sheet documenting technical failures. The people overlays claim to serve actively oppose overlay technology because it doesn't work and often makes their experience worse.

Why don't overlays work technically?

Screen readers parse HTML before JavaScript executes—overlay "fixes" arrive too late. Automated overlay detection catches only 25-40% of WCAG violations. Complex issues requiring human judgment (contextual alt text, reading order, meaningful descriptions) escape detection entirely. Even for detected issues, JavaScript patches often fail to provide meaningful accessibility.

What should I do if I'm currently using an overlay?

Remove the overlay (it provides no protection and may invite scrutiny). Run a comprehensive accessibility scan to understand actual state. Implement source code remediation through expert services like TestParty. The transition takes 14-30 days to move from overlay masking to actual WCAG 2.2 AA compliance.

How does source code remediation differ from overlays?

Source code remediation fixes actual HTML, CSS, and JavaScript. Screen readers encounter accessible code immediately—no JavaScript timing issues. Expert review catches 100% of issues, not just the 25-40% automated tools detect. <1% of TestParty customers have been sued versus 800+ overlay users. Real fixes, not cosmetic patches.

Related Resources

For more on overlay alternatives:

• Sued with AccessiBe Installed — Real lawsuit scenarios
• Automated Accessibility Remediation — How real fixes work

Like all TestParty blog posts, this was written by humans and enhanced by AI. This content is for educational purposes only. Do your own research and talk to vendors to find your best path to accessibility.