2026-05-17 · 6 min read

Accessibility Overlays and the DOJ Title II Rule: Why They Don't Satisfy Compliance

# Accessibility Overlays and the DOJ Title II Rule: Why They Don't Satisfy Compliance

If your government website has an accessibility overlay installed — AudioEye, accessiBe, UserWay, or another widget — you almost certainly have a compliance gap heading into April 2027.

This is not a minority position from critics of the overlay industry. It is the practical reality of what the DOJ Title II Final Rule requires and what overlay products can and cannot do. Understanding the distinction matters because government IT directors are making procurement decisions right now based on vendor claims that do not hold up under the rule.

What accessibility overlays actually do

An accessibility overlay is a JavaScript widget that loads on top of your existing website and attempts to modify how the page is presented to users, particularly users of assistive technology. Common modifications include adjusting contrast ratios, enlarging text, changing font families, and applying runtime ARIA attribute patches to elements that are missing them.

The pitch is straightforward: install one script tag, get a compliance claim. Vendors typically offer a dashboard where administrators can toggle accessibility features, and many include an auto-scanning component that attempts to detect and fix common issues on the fly.

The limitations are less visible from the vendor's marketing materials.

Why overlays cannot satisfy WCAG 2.1 AA

The rule requires the content to conform, not the presentation layer. WCAG 2.1 is a standard for how web content is authored and structured. Success criteria apply to the underlying HTML, CSS, and JavaScript of the site itself. A runtime script that modifies a page's rendered output does not change what the content is — it changes how one layer of the browser renders it, in ways that may or may not reach the assistive technology.

Screen readers, for example, primarily interact with the accessibility tree, which is built from the DOM. A widget that modifies computed CSS properties after page load may not affect the accessibility tree at all. An image without an alt attribute in the source HTML will typically be presented to a screen reader without the alt text even if an overlay script has attempted to add one — because the timing of when ARIA patches are applied relative to when the accessibility tree is built is not guaranteed.

Overlay vendors cannot fix what they cannot see. Overlays scan pages and apply fixes based on pattern matching. They cannot evaluate whether the purpose of a button is communicated to a screen reader user in context. They cannot assess whether the focus order makes sense for a user navigating a complex form. They cannot determine whether error messages are properly associated with the inputs that generated them. These are the classes of issues that require human evaluation, and they account for a substantial portion of WCAG's Level AA criteria.

The DOJ rule contains no overlay safe harbor. The Final Rule specifically requires WCAG 2.1 Level AA conformance. It does not acknowledge overlays as a compliance mechanism, does not create an exception for sites using overlay products, and does not define "reasonable efforts" in a way that overlay use would satisfy. A covered entity that relies on an overlay and faces a complaint or investigation cannot point to the overlay subscription as a defense.

Overlay vendors have faced litigation despite their compliance claims. Several companies have been named in ADA website accessibility lawsuits while actively using overlay products. The existence of a widget claiming compliance does not insulate a site from liability, and plaintiffs' attorneys have tested this argument in court.

What the accessibility community has concluded

More than 400 accessibility professionals and organizations — including signatories from disability rights advocacy groups, academic researchers, and independent accessibility auditors — signed the Overlay Fact Sheet, an open statement urging organizations to avoid overlay products as a compliance strategy. The statement documents specific technical failures, user experience harms, and legal risks associated with overlay use.

This is not a niche disagreement. The National Association of the Deaf and other major disability organizations have publicly stated that overlays do not constitute accessible design and do not satisfy ADA requirements. Independent accessibility research has documented cases where overlay widgets actively impede screen reader users by intercepting keyboard events, adding redundant or conflicting ARIA attributes, and interfering with users' own assistive technology settings.

What government agencies should do instead

First: verify what you have. If your site has an overlay installed, run an independent scan using WAVE or axe-core to assess the underlying content before the overlay applies its modifications. Most browser developer tools allow you to disable JavaScript. What remains is closer to what a screen reader encounters when the overlay's timing is imperfect or when a user has JavaScript disabled or delayed by a slow connection.

Second: get a realistic compliance picture. Automated tools assess approximately 57% of WCAG success criteria. The remaining 43% require manual testing: keyboard navigation testing, screen reader testing, and evaluation of cognitive accessibility factors. An overlay vendor's scan covers only the automated portion, and the automated portion of the criteria, and does so with the overlay's own modifications in place — which is not the same as the underlying content conforming.

Third: plan your actual remediation path. WCAG 2.1 AA conformance is achieved by making your content conform — remediating the issues in the source HTML, CSS, and JavaScript, not masking them with a runtime layer. A professional audit generates the findings inventory your development team needs to remediate. An overlay subscription does not produce that inventory.

For government agencies evaluating where to start, the self-assessment in How to Do a Quick Accessibility Self-Assessment of Your Government Website covers the tools and 10-item checklist that provide an honest baseline before engaging a professional auditor.

The audit-first approach

The most defensible compliance path for a covered entity is: audit the site, document the findings, remediate the findings, publish an accurate accessibility statement that reflects where you are, and update that statement as you make progress.

An overlay does not audit your site. It does not document findings. It does not remediate the underlying code. And it does not produce an accessibility statement that accurately describes your conformance status — because it is not producing conformance, it is producing a modified presentation layer that does not satisfy the rule.

If your agency is approaching April 2027 with an overlay as your compliance strategy, the gap is larger than the overlay is closing.

The Parallax WCAG Audit is Morton Technology Consulting's professional WCAG 2.1 AA audit service for Florida government agencies. It delivers a findings inventory, a prioritized remediation roadmap, and a completed accessibility statement draft that names the auditor and can be published immediately. If you have an overlay installed, the audit identifies both the overlay's known failure modes on your specific site and the underlying issues the overlay is not addressing.

The WCAG Pre-Audit Readiness Kit ($149) is the right starting point if you want to understand your exposure before commissioning a full audit. It includes a 47-point testing checklist, an accessibility statement template, a WCAG remediation tracker, and a procurement guide for Florida agencies evaluating audit vendors.

---

*Morton Technology Consulting LLC, Tallahassee, FL. Questions about accessibility overlays or Title II compliance: [email protected].*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →