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.
| Capability | 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 | Supported written changes remain in the modified theme or Shopify resource; extension behavior stops and theme edits do not transfer to another theme |
| Developer required to apply | No (but it doesn’t fix the source) | Often a GitHub PR to merge | Supported suggestions can be approved in the app; complex or risky work still needs a developer or specialist |
| Saved original for supported changes | N/A — nothing is changed | Varies | Affected theme source or prior resource value recorded |
| Review each change first | Nothing to preview | Sometimes | Yes — approve before the change is made |
| Follow-up check after a fix | No | Varies | Runs a check; only confirmed fixes are marked resolved |
| Merchant-confirmed restore | No | Rare | When a trustworthy earlier result supports it; otherwise you choose whether to restore |
| Date-stamped evidence record | Varies by product and service | Varies | A record for each fix and report downloads on paid plans |
| Regulatory-claim risk | Depends on product behavior and claims; an FTC order addressed unsupported accessiBe claims | Depends on claims made | Depends on actual results and claims; AccessComply makes 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 automated scan, then install to review supported suggestions. Supported changes save the original; restoring an older value requires your confirmation and can overwrite later edits.