Methodology comparison
Overlay vs hybrid vs source-code fixes.
Plenty of tools now say “source-code, not overlay.” What actually matters is the mechanism — whether the fix is backed up, previewed, verified, reversible, and documented. Here is the honest breakdown.
| Overlay widget | Hybrid | AccessComply (source-code) | |
|---|---|---|---|
| Where the fix lives | Runtime JavaScript layer over your page | Some code, some runtime widget | Your actual theme source files |
| Survives after uninstall | No — fixes vanish when removed | Only the code-level part remains | Yes — the edits are yours to keep |
| Developer required to apply | No (but it doesn’t fix the source) | Often a GitHub PR to merge | No — one-click, no dev needed |
| Backup before every change | N/A — nothing is changed | Varies | Full theme backup first |
| Preview the exact diff first | Nothing to preview | Sometimes | Yes — approve the change before write |
| Post-fix re-scan verification | No | Varies | Yes — confirms the issue is resolved |
| Automatic rollback on regression | No | Rare | Yes — restores from backup |
| Date-stamped evidence record | Marketing certificate, not remediation proof | Varies | Per-fix remediation record, exportable |
| Regulatory-claim risk | High — overlays drew the FTC $1M accessiBe order | Depends on claims made | Lower — we make no compliance guarantee |
Comparison reflects approach categories, not any single named product, and AccessComply's own workflow. See the safety architecture for how each AccessComply step works.
Get Started
Fix it at the source.
Run a free scan to see your store's issues, then install to apply backed-up, reversible source-code fixes.