Step 1
Record the installed version, host page and configuration needed to trigger the issue.
Practical review guide · Free worksheet
Reviewed by ComplyFolio. Store owners, accessibility reviewers and developers testing real ecommerce journeys.
Get the working templateThese are suggested operational checks to apply to your own evidence. They are not additional legal requirements or claims that the workspace automates this entire task.
Record the installed version, host page and configuration needed to trigger the issue.
Reduce the reproduction while retaining the interaction that causes the barrier.
Describe expected and actual behavior with keyboard or assistive-technology evidence.
Agree an owner and retest condition, then verify the fix in the original store integration.
An embedded review widget steals focus after loading, but the vendor cannot reproduce it on its standalone demo.
A vendor defect handoff with integration-specific reproduction and acceptance checks.
Boundary: A vendor acknowledgement or patch note is not evidence that the store integration is fixed.
This scenario is fictional. It illustrates a review decision, not a customer outcome or a compliance determination.
The Markdown worksheet includes the procedure, the fields below, and space for findings, evidence, owners and retests. It contains no pre-approved findings. Edit it locally without an account.
Record what you observed, including unknowns. Link each decision to a source and keep unresolved questions assigned to an owner. Share completed records only through an appropriate authorized route.
The references provide the legal or technical context. The procedure and worksheet are ComplyFolio working suggestions, not official forms or a certification standard.
A vendor acknowledgement or patch note is not evidence that the store integration is fixed.
Use the free workspace for an initial public product-page review, then add the manual evidence and decisions this guide requires. A page scan cannot inspect private supplier files or complete every user journey.
Start with a public product page