In recent years, accessibility overlays have exploded in popularity. Tools like AccessiBe, UserWay, and other “quick fix” widgets promise instant ADA compliance, automated WCAG fixes, and legal protection with a single line of JavaScript.

It sounds good—too good.
And that’s because it is.

Despite the marketing claims, accessibility overlays do not—and cannot—make a website accessible. In many cases, they actually increase legal exposure, frustrate disabled users, and create a false sense of security.

Here’s why.

1. Overlays Don’t Fix the Code — They Mask It

The most important truth:

Accessibility must be built into the underlying HTML, structure, roles, labels, and interactions.

Overlays cannot rewrite source code. They only add a visual layer on top of the existing site.

Which means:

• Incorrect ARIA roles remain incorrect

• Missing alt text remains missing

• Broken labels stay broken

• Poor heading structure stays poor

• Keyboard traps remain

• Components with the wrong markup stay inaccessible

You can’t fix structural problems with paint.

2. Screen Readers Often Ignore or Interfere With Overlays

Blind and low-vision users rely on screen readers like JAWS, NVDA, and VoiceOver.

Overlays:

• Add extra navigation noise

• Introduce duplicate landmarks

• Hijack keyboard focus

• Conflict with user settings

• Hide or overwrite accessible labels

Many blind users immediately disable overlays because they disrupt access.

So the group these tools claim to help is the one most harmed.

3. Overlays Violate the User’s Own Accessibility Settings

People with disabilities already configure:

• Browser zoom

• OS color modes

• Custom contrast settings

• Screen reader verbosity

• Font size overrides

• Reduced motion preferences

Overlays override those preferences with their own presets.

 That’s not accessibility.

That’s forcing a person into your version of accessibility instead of respecting theirs.

4. Overlays Fail Most WCAG Requirements

Out of ~78 WCAG 2.2 success criteria, overlays can touch maybe 10–15.

They cannot automate:

• Semantic structure

• Logical reading order

• Focus states and focus order

• Component-level behavior

• Live region accuracy

• Form error handling

• Accessible name/description relationships

• Keyboard navigation

• Timing and interaction rules

• Motion/animation triggers

• Captions or transcripts

• PDF accessibility

Most of WCAG must be implemented by humans who understand the standard.

5. Courts Have Repeatedly Ruled Overlays Insufficient

This is critical—especially for law firms and regulated industries.

Federal rulings have shown that overlays do not eliminate ADA liability, including:

• Martinez v. Cot’n Wash Inc.

• Gil v. Winn-Dixie

• American Council of the Blind v. Hobby Lobby

In nearly all cases:

The presence of an overlay did not protect the business.

Plaintiffs even increasingly target sites because they use overlays—they signal a lack of true compliance.

6. Overlays Often Introduce New Accessibility Problems

Ironically, they regularly create issues such as:

• Keyboard traps

• Duplicate controls

• Blocked menus

• Incorrect ARIA injections

• Broken skip links

• Inflated DOM size (bad for screen readers)

Trying to automate accessibility often breaks accessibility.

7. Overlays Offer a False Sense of Security

This is the most dangerous part.

Businesses install an overlay expecting:

• Instant compliance

• Legal protection

• Actual accessibility

But they get:

• A superficial widget

• No improvement to underlying barriers

• Increased risk

• A misleading WCAG “score”

• No actual accessibility for users

Compliance is not the same as appearing compliant.

8. What Actually Works: Manual, Human-Driven Accessibility

Accessibility requires:

• Proper semantic HTML

• Clear structure

• Keyboard support

• Assistive technology testing

• WCAG 2.2 alignment

• Accessible design patterns

• Clean forms and interactions

• Alt text based on context, not automation

• PDF tagging

• Human judgment

This cannot be automated.

This is where an accessibility consultant—someone who understands UX, design systems, interaction patterns, and assistive tech—makes all the difference.

9. Overlays Can Work as Enhancements—But Never as Compliance

Aperio Accessibility Consulting’s stance is simple:

✔ Overlays may offer optional user control enhancements

…but

❌ They cannot fix your underlying code

❌ They cannot make your site WCAG 2.2 compliant

❌ They cannot protect you from ADA claims

Use them after your website is accessible—not instead.

Final Thoughts: Accessibility Requires Real Work—But It’s Worth It

Accessibility is not just a legal requirement.
It’s good design.
It’s good UX.
It’s inclusion.
It’s professionalism.

Overlays promise shortcuts but deliver band-aids.

Real accessibility delivers:

• Better user experience

• Stronger SEO

• Lower legal risk

• Greater trust

• A wider audience

• A more ethical digital presence

If you’re ready for actual accessibility—not surface-level automation—Aperio Accessibility Consulting can help.