Find accessibility issues and know when they return

It opens your public Shopify storefront in a real browser and checks the rendered pages against WCAG 2.1 Level AA. It reports what it found, where, and what it means for a shopper, and it keeps that result. On the paid tiers it also gives you the steps for fixing each issue, sets each scan beside the one before it, and on Pro+ tells you when something you resolved has come back.

AccessIIQ loads your storefront in a real browser, waits for the page to finish settling rather than for a fixed number of seconds, and then runs the checks against the page as rendered. You watch the stage it has reached while it runs, and you can stop it at any point.

Your homepage, and a selection of the pages discovered from the links on it: 4 pages in total on Free, and 15 on Pro and Pro+. AccessIIQ picks which ones rather than taking them at random. It covers one of each kind of page it has found, returns to pages where it already knows something is failing, retries any it could not load last time, and otherwise goes to whatever it has not looked at for longest. A scan is a sample of your storefront rather than all of it, and the samples build into a history of your store over time.

Three in total, for as long as you have the app. It is not three a month and it does not reset. Free is there so you can see what AccessIIQ finds on your own storefront before deciding anything.

Pro is 60 scans a month and Pro+ is 150 scans a month. The count resets at the start of each calendar month, UTC, rather than on the day you subscribed. In the month you subscribe, only scans run after you subscribed count. A scan that fails does not use your allowance. A scan you cancel before it starts does not either. One you cancel after it has started does, and so does running a scan again.

On Pro+ you can have AccessIIQ run a scan once a week, on a day and hour you choose. It uses your monthly allowance like any other scan. It runs weekly, and nothing about it runs more often than that.

Findings are identified by what the issue is and where it occurs, rather than by counting how many there were. So a scan can say that a specific issue you had resolved is present again, which a total moving up and down could never tell you. This is part of Pro+.

No. AccessIIQ requests read only access to your theme files and no write access, so it cannot alter your store. It tells you which file an issue comes from and what needs correcting there. The change itself is made outside AccessIIQ, through whatever development or theme workflow you already use.

No, and it does not try. AccessIIQ changes nothing at all: for a small, growing set of checks it can trace the problem to a file in your theme and say what needs correcting there. For everything else it reports what it found and explains what needs deciding. It never invents alternative text, never picks a colour for you, and never proposes a change when it is not confident which file the problem came from.

No, and no automated tool can. AccessIIQ reports what its checks found on the pages it scanned. Automated checks cover only part of WCAG, so a scan that finds nothing means no machine detectable failures were found on those pages, not that your storefront is fully accessible. AccessIIQ gives no legal advice and issues no document of standing.

Shopify serves its own lock screen instead of your theme, so a scan would describe Shopify's markup rather than yours. AccessIIQ detects this and stops with an explanation rather than reporting a misleading result. Turn the password off under Online Store then Preferences, run the scan, and switch it back afterwards if you need to.