Replacing an Accessibility Overlay With Real Remediation

Why Overlays Fall Short

Overlays are often marketed as a quick fix for accessibility compliance. However, research by Alison Walden and Matt Vitale on U.S. state government websites reveals why this promise is misleading. In 2025, only seven states used overlays, and by October 2026, only five continued to do so. If your site still uses an overlay, it's likely ineffective.

The main issue is that overlays don't address core accessibility problems. Common failures include broken keyboard navigation, unclear link labels, missing form field labels, and inaccessible PDFs. Overlays didn't fix these issues and sometimes added new barriers, like breaking carousel controls or removing link functionality.

For programs with ADA Title II obligations under the DOJ Final Rule (2024), overlays don't demonstrate Accessibility Governance. This guide will help you replace them with effective remediation.

Preparing for Remediation

Before making changes, gather the following:

• Overlay script inventory. Check your tag manager, CMS templates, and CDN for third-party scripts that inject overlays. Review your Content Security Policy allowlist too.
• Contract details. Know when you can terminate the overlay service and who approved it.
• Testing tools. Use Axe DevTools or Lighthouse for automated scans, and NVDA with Firefox or Chrome, JAWS, and VoiceOver for screen reader testing.
• Designated owner. Assign someone with authority over design, engineering, and content. An accessibility specialist and input from people with disabilities are recommended.
• Target standard. Choose a standard, like WCAG 2.1 AA, and confirm it aligns with the DOJ Final Rule (2024).

Implementing Effective Remediation

Step 1: Baseline Testing Without the Overlay. Disable the overlay script in a test environment and assess your site's functionality. Many users rely on their own assistive tools and don't need overlays.

Step 2: Evaluate the Overlay. Document how the overlay affects your site before removing it. Check text contrast, keyboard navigation, and screen reader compatibility. This documentation supports the case for removal.

Step 3: Prioritize Key Failures. Focus on these common issues:

1. Keyboard operability. Ensure menus and dialogs work without a mouse, with visible focus (WCAG 2.4.7) and no traps (2.1.2).
2. Link purpose. Use descriptive text for links (2.4.4) or provide context with aria-labelledby or aria-describedby.
3. Form labels. Ensure every input has a programmatic label (1.3.1, 3.3.2, 4.1.2). Use native <label for> where possible.
4. PDFs. Convert PDFs to accessible formats or replace them with HTML.

Step 4: Fix Assistive Technology the Source. Update your design system and component library. Correcting patterns like buttons or forms fixes all pages using them. Proper heading structure is crucial, as overlays can't fix markup errors.

Step 5: Integrate Accessibility in Development. Add accessibility criteria to development tickets and automated checks to your CI pipeline. Combine automation with manual testing for comprehensive coverage.

Step 6: Remove the Overlay. Delete the overlay script from your systems, update your accessibility statement, and notify the vendor of termination.

Verifying Improvements

Removing the overlay is just the beginning. Verify improvements by:

• Re-testing the baseline. Use the same tools and tasks to compare defect counts.
• Testing user journeys. Ensure critical tasks can be completed with a keyboard and screen reader.
• Checking for residual code. Use developer tools to ensure no overlay code remains.
• Involving disabled users. Conduct task-based testing with users of Assistive Technology.
• Documenting results. Use an Accessibility Conformance Report to record findings accurately.

Ongoing Maintenance

• Quarterly: Re-scan key templates and test important user journeys. Review new PDFs.
• Every release: Run CI checks and manually verify new components.
• Annually: Audit third-party scripts to prevent reintroduction of overlays.
• Procurement: Require Accessibility Conformance Reports from vendors.
• Training: Keep your team updated with credentials like the Certified Professional in Accessibility Core Competencies.

Redirect resources from ineffective overlays to building skills and processes that ensure accessibility. This investment in people and practices leads to truly accessible sites.