How fixes stay safe
No blind AI edits. Recorded, reviewed, checked, restorable.
AccessComply can apply supported merchant-approved changes through protected Shopify theme and content workflows. Here is the workflow used when a supported change is applied.
Scan the underlying storefront
Scans evaluate the storefront states AccessComply can reach. The optional extension is excluded from follow-up checks so it cannot make an underlying issue appear fixed. Third-party behavior, unreachable states, and checks that need a person remain clear limitations.
Original saved before supported changes
Before changing a supported theme file or content value, AccessComply saves the original. Nothing changes until that saved original exists and your approval is checked again.
Review before any change
For an individual theme fix, you see and approve the exact Liquid or CSS change. Grouped fixes show the selected issues and changes before approval. A scan never changes a live theme on its own.
Follow-up scan after each fix
After a fix is applied, AccessComply re-scans affected pages to check whether the issue is no longer detected and whether the comparison surfaces new issues. Only confirmed fixes are marked resolved.
You control every restore
If the follow-up check finds a serious new issue, the fix is marked as needing attention and the matching saved original is shown. Restoring requires your approval so delayed work cannot overwrite later theme edits.
Activity record
Each fix produces a dated record with the page, WCAG criterion, change made, and follow-up result. You can export it for your team, agency, or counsel.
What we don't claim
AccessComply reports focused automated results and documents supported work — 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 hands-on review rather than fixed automatically. 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 issues and suggested fixes, then install when you are ready to approve a supported change with a saved original and follow-up check.