SHOPIFY ACCESSIBILITY EVIDENCE

Turn an axe scan into a record you can review.

Paste an axe-core JSON export to get a dated summary of violations, passes, and items needing review. Nothing leaves this browser. Need a price? Estimate remediation hours and a quote range from the same scan. Need to know which Liquid file to open? Route the scan to likely theme areas. Need to see what a fix changed? Compare before and after scans. Wondering how this differs from a paid widget? See this tool vs. accessiBe. Formatting a government website scan for ADA Title II? The ADA Title II evidence report turns the same kind of axe-core JSON into a dated Title II record with a WCAG 2.1 AA split.

Paste axe JSON

Evidence record

No report generated yet.
Your report will appear here.

Common questions

Does this evidence record prove my Shopify store is ADA/WCAG compliant?

No. It formats whatever axe-core found into a dated, readable record — it does not run a scan itself, does not check anything axe-core cannot detect (like actual screen-reader usability or keyboard-trap edge cases), and does not determine legal compliance. Treat it as documentation of one automated test at one point in time, not a compliance certificate.

Where do I get the axe JSON to paste in?

Run axe-core (the axe DevTools browser extension, axe-core CLI, or a similar tool) against your storefront and export its JSON results — this page only formats output you already generated elsewhere, it does not crawl or scan your site itself.

Does my scan data get uploaded anywhere?

No. The JSON you paste is parsed and formatted entirely in your browser; nothing is sent to a server. Usage counting only tallies anonymous feature events in localStorage, with an opt-out checkbox above.

What's the difference between this and the quote or theme-areas tools?

This page turns a scan into a readable evidence record; the quote tool estimates remediation hours and a price range from the same JSON; theme-areas maps violations to likely Liquid template files to open; and the comparison tool diffs two scans to show what a fix actually changed. They all run on the same axe export, just answering different questions about it.