Website Accessibility Overlay vs. Real Code Fix: Which Is Better?

A factual, side-by-side breakdown of accessibility overlays and genuine code remediation — what each does technically, where each fails legally, and which approach fits your situation.

What Each Approach Actually Does

Accessibility Overlays

An accessibility overlay is a third-party JavaScript widget loaded after your page renders. It sits on top of your existing HTML without modifying your source code. At runtime the script attempts to inject ARIA attributes, adjust color contrast, or reorder focus — but it is working against a finished DOM, not building a well-structured one. Common overlay vendors include accessiBe, UserWay, AudioEye, and EqualWeb.

Because the overlay does not touch your source files, every problem it attempts to patch still exists in your codebase. If the script fails to load — due to a network error, an ad blocker, or a corporate firewall — your original, unmodified page is what users and automated audit tools see.

Real Code Remediation

Code remediation means fixing defects directly in your site's source: adding correct ARIA labels, replacing non-semantic markup with proper HTML elements, establishing a logical heading hierarchy, ensuring keyboard focus order matches visual order, and writing descriptive alternative text into the actual image tags. The fix persists whether or not any third-party script loads, and it is what a human auditor or court-appointed technical expert will inspect.

WCAG 2.2 AA Success Criteria That Overlays Cannot Reliably Satisfy

The W3C Web Content Accessibility Guidelines 2.2, published at w3.org/TR/WCAG22, define the technical benchmark used by U.S. courts and the Department of Justice. Several Level AA success criteria require structural decisions baked into source HTML — decisions an overlay cannot retroactively make with consistent reliability:

• 1.3.1 Info and Relationships (Level A, foundational to AA conformance): Information conveyed through visual formatting must be programmatically determinable. A table that uses CSS to look like a table but is built from <div> elements fails this criterion. An overlay can inject ARIA roles at runtime, but the mapping is often incomplete or inaccurate for complex layouts.
• 1.3.2 Meaningful Sequence: The reading order of content must be determinable from source order. Overlays cannot reliably reorder DOM nodes without breaking interactive behavior.
• 2.4.3 Focus Order: Keyboard focus must follow a sequence that preserves meaning. If the source DOM order does not match visual order, an overlay's focus-management script can introduce new traps or skip interactive elements entirely.
• 4.1.2 Name, Role, Value: Every user interface component must expose its name, role, and current value programmatically. Correct ARIA authoring requires understanding each widget's interaction pattern; automated overlay injection frequently applies incorrect roles.
• 2.4.11 Focus Not Obscured (Minimum) and 2.4.12 Focus Not Obscured (Enhanced) — new in WCAG 2.2: A focused component must not be entirely hidden by author-created content. An overlay's floating widget button can itself become the obscuring element.

The Legal Landscape

ADA Title III (42 U.S.C. § 12182) prohibits discrimination on the basis of disability by places of public accommodation, a category that federal courts have extended to websites. The DOJ's 2024 final rule under Title II explicitly adopts WCAG 2.1 Level AA for state and local government websites. For private businesses under Title III, no single technical standard is codified, but WCAG 2.1 and 2.2 Level AA function as the accepted yardstick in litigation and DOJ enforcement guidance. Information on ADA enforcement activity is publicly available at ada.gov.

Courts have generally not accepted the presence of an overlay as a complete defense to an ADA website complaint. Demand letters and filed complaints have named overlay vendors by product name as a barrier rather than a remedy — particularly when the overlay interferes with a user's existing assistive technology, such as a screen reader that the overlay's script overrides.

In 2025 the U.S. Federal Trade Commission reached a settlement with accessiBe that included a one-million-dollar penalty, citing concerns about how the company marketed automated accessibility compliance. That enforcement action is the most direct federal signal to date that automated-only solutions marketed as compliance guarantees face regulatory scrutiny.

Side-by-Side Comparison

Who Should Choose Which Approach

When Real Code Remediation Is the Clear Choice

Small businesses with fewer than 100 pages are the best candidates for direct code remediation on a defined timeline. The scope is manageable, the fixes are permanent, and the legal documentation produced — an accessibility statement, a good-faith remediation record, and a VPAT — is meaningfully more defensible than a subscription receipt for an overlay service. If you have received a demand letter, a court will ask what you actually changed in your site, not what widget you installed.

When an Overlay Might Seem Appealing (and Why That Logic Usually Breaks Down)

Overlays are marketed as a fast, low-effort path to compliance. For large organizations with thousands of pages and a multi-year remediation roadmap, some use overlays as a temporary stopgap — but legal and disability-rights advocates consistently caution that doing so does not pause the litigation clock and may antagonize users who rely on assistive technology. A stopgap that triggers additional complaints is not a useful stopgap.

Where WCAGDefender Fits

WCAGDefender (wcagdefender.com) is a veteran-owned accessibility scanner and real-code remediation service built specifically for small businesses managing ADA demand-letter risk. It does not install an overlay. It scans any public URL against WCAG 2.1 and 2.2 Level AA and returns a lawsuit-risk assessment rather than a vague compliance grade. Critically, it detects overlays already present on a site — because those widgets are increasingly named in demand letters, not accepted as protection against them.

When defects are found, WCAGDefender delivers copy-ready code fixes with platform-specific instructions for WordPress, Shopify, Wix, and Squarespace. Every fix goes through a multi-model accuracy review before delivery. The documentation package includes an accessibility statement, a good-faith remediation record, a VPAT, an IRS Form 8826 Disabled Access Credit worksheet (the credit is worth up to $5,000 for eligible small businesses), and a draft demand-letter response.

The initial scan is free, requires no account, and is available instantly at wcagdefender.com. Paid-tier details are at wcagdefender.com/pricing.

The Bottom Line

Accessibility is an ongoing practice, not a one-time certificate, and no tool — overlay or otherwise — makes a site permanently lawsuit-proof. What separates a legally defensible position from a vulnerable one is documented, good-faith effort to fix actual defects in actual code. Overlays do not meet that bar under current WCAG 2.2 AA criteria or under the legal standards courts apply to ADA Title III claims.

Frequently asked questions

Can an accessibility overlay get me sued even if I'm paying for it?

Yes. Courts have not accepted overlays as a complete ADA defense, and some demand letters specifically name overlay products as a barrier because they can interfere with users' own screen readers. Paying a subscription for an overlay does not pause the litigation clock.

What WCAG criteria does an overlay fail to fix?

Overlays cannot reliably satisfy structural criteria that depend on source HTML, including WCAG 2.2 AA success criteria 1.3.1 (Info and Relationships), 1.3.2 (Meaningful Sequence), 2.4.3 (Focus Order), and 4.1.2 (Name, Role, Value). These require correct markup decisions in the codebase, not runtime patches.

Is WCAG 2.2 legally required for private business websites in the U.S.?

No single technical standard is codified for private businesses under ADA Title III, but federal courts and the DOJ treat WCAG 2.1 and 2.2 Level AA as the accepted practical benchmark. The DOJ's 2024 rule formally adopted WCAG 2.1 AA for Title II (government) websites.

What happened with the FTC and accessiBe?

In 2025 the U.S. Federal Trade Commission reached a settlement with accessiBe that included a one-million-dollar penalty. The FTC cited concerns about how the company marketed automated accessibility compliance — the most direct federal signal yet that automated-only compliance claims face regulatory scrutiny.

How is WCAGDefender different from an overlay like UserWay or AudioEye?

WCAGDefender does not install an overlay or any widget on your site. It identifies real defects and delivers code fixes applied directly to your source files, with platform-specific steps for WordPress, Shopify, Wix, and Squarespace. It also detects overlays already on your site, because those products are increasingly named in demand letters rather than accepted as a defense.

Is real-code remediation practical for a small business with a limited budget?

Yes, particularly for sites under 100 pages. Smaller sites have manageable scope, and a one-time remediation produces permanent fixes. WCAGDefender's free scan gives you an immediate lawsuit-risk read with no signup, and its documentation includes an IRS Form 8826 worksheet for the Disabled Access Credit, which is worth up to $5,000 for eligible small businesses.