Support — Ally Store Audit
Help, answers and contact for Ally Store Audit — our web scanner and Chrome extension for ADA & WCAG store accessibility. If you can't find your answer below, email us — we read every message.
Quick start
- Open any store page you want to check.
- Click the extension icon in the Chrome toolbar.
- Press Scan to check the current page, or Scan store pages — up to 20 to check a sample of the store.
- Open the full report to see each issue, its severity, and how to fix it. You can print it or save it as a PDF.
Frequently asked questions
What does the extension check?
It runs the axe-core accessibility engine against the page to find common WCAG / ADA problems — missing image descriptions, low color contrast, unlabeled buttons and form fields, heading and landmark issues, and more. Each finding is explained in plain language with a suggested fix.
What is the difference between a single-page scan and a store scan?
A single-page scan checks only the page you are on. A store scan reads the store's robots.txt and sitemap and opens a sample of up to 20 pages in background tabs to check them together, giving you a broader view of the store.
What do the severities mean?
- Critical / Serious: issues most likely to block real shoppers who use assistive technology. Fix these first.
- Moderate / Minor: smaller problems that still affect usability.
- Inconclusive: checks that could not be decided automatically and need a human to review them.
Does a clean report mean my store is legally compliant?
No. Automated testing finds many issues but cannot catch everything, and no tool can guarantee legal compliance on its own. Use this as a strong starting point, and have important flows reviewed by a person.
Is my data safe?
Yes. The analysis runs entirely on your own device. Your pages and your reports are never sent to us. There are no analytics or trackers. See the Privacy Policy for full details.
How much does it cost?
The extension is currently free to use.
Troubleshooting
The scan button does nothing, or the report is empty
- Refresh the store page and try again.
- Some browser pages (such as
chrome://pages, the Chrome Web Store, or a blank tab) cannot be scanned — open a normal store page instead. - Make sure the page has finished loading before you scan.
"No issues found" — is that right?
It is possible, but remember that automated checks can't catch everything. Some checks may be marked inconclusive and still need a human review.
A store scan skipped some pages
Pages can be skipped if they time out or are blocked by the store's robots.txt. The report lists which pages were scanned and which failed, and why.
The multi-page scan asks for permission
That is expected. A store scan needs access to that specific store's pages so it can open and check them. Access is requested only for the store you are scanning, and you can remove it any time in Chrome's extension settings.
Contact
Questions, bugs or feature requests: thiago.990199@gmail.com
We aim to reply within a few business days.