Safety architecture
No blind AI edits. Backed up, previewed, verified, reversible.
AccessComply changes your real theme source code — the durable kind of fix — but only through a workflow built to be safe at every step. Here is exactly what happens when a fix is applied.
Source-truth scan (overlay off)
Every scan measures your real theme source, not a runtime-patched DOM. We disable our own storefront overlay during scanning so a fix has to exist in your code to count — you never get a falsely-clean result.
Full theme backup before any write
Before a single file is changed, AccessComply takes a versioned backup of the files it will touch. Nothing is modified until that backup is recorded.
Preview the exact diff
You see the precise before/after code change for each fix — the actual Liquid/CSS/content edit — and approve it before it is written. No blind AI edits.
Post-fix re-scan verification
After a fix is applied, AccessComply re-scans the affected pages to confirm the issue is actually resolved and that no new violations were introduced.
Automatic rollback on regression
If the re-scan attributes a new violation to a fix and crosses the regression threshold, the change is rolled back from the backup automatically — including AI fixes like alt text and ARIA labels.
Evidence record
Each fix produces a date-stamped record — page, WCAG criterion, the change made, and the re-scan result — exportable as a remediation report for your team, agency, or counsel.
What we don't claim
AccessComply reduces accessibility risk and documents your remediation — it does not provide legal advice or guarantee compliance with ADA, EAA, WCAG, or any other standard. Some issues (complex keyboard traps, third-party app widgets, semantic content judgment, checkout constraints) are flagged for manual review rather than auto-fixed. Honest scope is part of the safety model.
See the overlay vs source-code comparison for how this differs from widget-based tools.
Get Started
See it on your own store.
Run a free scan, review the findings and the proposed fixes, then install when you are ready to apply backed-up, reversible changes.