Check rendered storefront pages
Scan the experience customers actually receive, regardless of the commerce platform behind it.
For EU-facing stores
Find accessibility barriers in the shopping journey
Start with product, basket, checkout, and account pages. Fix what automation can prove, then use the manual checklist for what needs human judgement.
Work through the customer journey
Prioritize purchase blockers
Group issues by severity and page so teams can start with forms, controls, names, contrast, and navigation.
Document and monitor
Re-scan after theme or checkout changes and keep an accessibility statement aligned with current evidence.
Review the transaction, not just the storefront
Cart, checkout, login, and payment are connected customer jobs. Treat them as one testable journey while keeping the automation boundary visible.
Cart
Check product options, quantity controls, update messages, names, focus order, and rendered errors.
Checkout
Scan reachable checkout states and record guided keyboard, reflow, label, and error-prevention checks.
Login and account
Use a dedicated saved test account for configured authenticated scans and repeatable journeys.
Payment hand-off
Review the rendered transition and return states; third-party payment behavior still needs human testing.
What automation can support
Rendered markup, accessible names, labels, contrast, structure, selected-rule regressions, and reached-page evidence.
What still needs people
Keyboard flow, understandable errors, content meaning, assistive-technology behavior, and third-party payment states.
See the evidence before signing up
The sample is a real report view: severity, affected element, rule, and a practical direction for the fix. Automated coverage is clearly separated from manual review.
Common questions
Is this only for accessibility specialists?
No. The workflow is written for developers, product teams, operators, and delivery leads, with the underlying rule and evidence kept visible.
Does a clean scan mean the site conforms?
No. Automated checks cover only part of WCAG. Manual review is still required for a conformance assessment.
What can the team do after a scan?
Save the site, scan more pages, track recurring rules and regressions, follow the manual checklist, and draft an accessibility statement from the evidence.