How to Remove Your Overlay and Get Real Compliance
Compliapoint works on WordPress (including WooCommerce) and Shopify sites.
The Right Order of Operations
The mistake to avoid when removing an overlay is removing it before implementing source-level fixes. This creates a window where you have neither the overlay (cosmetic as it was) nor real remediation. Here is the correct sequence:
Do not remove your overlay before starting remediation. While the overlay provides minimal actual accessibility benefit, removing it without a plan creates unnecessary risk. Follow the steps below in order. Why the overlay was never fixing anything is set out in why overlays fail.
Get Audited First
Before touching the overlay, complete a professional WCAG 2.2 audit of your site. This establishes a baseline of the issues your overlay was never fixing. The audit report becomes the roadmap for source remediation.
The audit should be performed with the overlay active so the auditor can document what it does and does not address. This creates a powerful before/after comparison.
Begin Source Remediation
With audit results in hand, start fixing violations at the source code level. Priority order:
- Critical: keyboard navigation, form labels, page structure
- High: image alt text, color contrast, heading hierarchy
- Medium: ARIA attributes, link purpose, error identification
- Low: redundant links, decorative images, minor contrast
The overlay remains active during this phase. You are layering real fixes underneath it.
Remove the Overlay
Once source remediation is substantially complete (critical and high items resolved), remove the overlay. The process varies by platform:
WordPress
Deactivate and delete the overlay plugin from Plugins in your admin panel. If installed via theme, remove the <script> tag from header.php or your child theme's functions file.
Shopify
Uninstall the overlay app from Settings > Apps. If added as a script, remove it from Online Store > Themes > Edit Code > theme.liquid (look for the overlay's <script> tag).
After removal: Clear your CDN cache, browser cache, and any page caching plugins. Test the site to confirm the overlay icon and scripts are completely gone. Check both desktop and mobile.
Verify and Document
After removal, perform a verification scan to confirm that all source-level fixes are intact and the overlay's removal did not introduce any issues. Generate your final deliverables:
- WCAG 2.2 audit report (baseline + findings)
- Remediation documentation (what was fixed, how, when)
- Accessibility test record (dated attestation of standard met)
- Accessibility statement (public-facing commitment)
These documents replace the overlay subscription as your compliance evidence. Unlike the overlay, they document actual fixes to actual code.
Cancel Your Overlay Subscription
Once the overlay is removed and verification is complete, cancel your subscription with the overlay vendor. You will no longer need it. Retain your cancellation confirmation for your records.
If your overlay contract has a term commitment, continue with the migration anyway: the barriers stay in your code for as long as the overlay runs, and the early-termination cost is a one-off.
What Changes After Removal
With source-level remediation replacing the overlay, here is what changes:
- Fixes in your code. Your remediation is in the source code. It does not depend on a JavaScript subscription. On WordPress it survives parent-theme updates (via child theme architecture). It works even if scripts are blocked.
- Real documentation. Your audit report, remediation record, and accessibility test record are the artifacts courts, procurement officers, and regulators recognize.
- No subscription cost. Source remediation is a one-time project. Ongoing monitoring (optional) catches new violations from content updates, but the core fixes stay in your code.
- Nothing left to cite. The overlay is no longer present to be cited against you, and a dated record shows what was tested and changed. How much weight that carries is your attorney’s judgment.
Cost Comparison
Businesses often choose overlays because they appear cheaper. Over a 3-year period, the math tells a different story:
- Overlay: published accessiBe, UserWay and EqualWeb plans run $390–$3,990/year, so $1,170–$11,970 over 3 years — with no change to your code
- Source remediation: from $4,750 one-time — fixes written into your own code, with a dated record of every change. Some eligible small businesses may also qualify for the federal Disabled Access Credit
After the tax credit, source remediation often costs less than a single year of overlay subscription — and the fixes stay in your code.
Ready to Make the Switch?
We handle the full migration: audit with overlay active, source remediation, overlay removal guidance, and a dated record of every change. Start with a five-minute assessment.