EU Compliance & Accessibility Workspace
Use one workflow for GPSR product evidence and EAA accessibility readiness signals.
The combined workspace does not prove product safety, GPSR compliance, EAA compliance, or WCAG conformance.
Reviewed core collection
These 18 pages are the maintained public core. Each page has a distinct task, a fictional worked example, explicit decision boundaries and direct primary-source links.
workspace
Start with the complete product-evidence and accessibility workflow.
Use one workflow for GPSR product evidence and EAA accessibility readiness signals.
The combined workspace does not prove product safety, GPSR compliance, EAA compliance, or WCAG conformance.
gpsr-task
Review operator, traceability, warning, label, supplier and Evidence Pack jobs.
Paste a product URL and generate a product listing readiness workflow with evidence tasks.
Only visible page signals and supplied evidence are assessed; product-specific legislation still needs specialist review.
Run a product-page readiness check for common GPSR evidence and listing gaps.
A readiness score is a triage signal, not a certification or a legal conclusion.
Use a product page URL to find listing gaps and generate evidence-management outputs.
The checker cannot inspect unpublished marketplace dashboards or physical packaging.
Identify missing EU responsible person details and turn them into supplier evidence requests.
An address alone does not establish that an organization is the valid responsible person.
Find manufacturer information gaps and generate a supplier request email.
A brand, distributor or marketplace seller must not be relabelled as manufacturer without evidence.
Prepare source-warning and translation-review blocks without inventing generic safety instructions.
ComplyFolio does not create product-specific hazards or substitute generic wording for verified warnings.
Create a draft label structure from extracted product fields and missing supplier data.
A generated draft is not print approval and does not replace product-specific labelling rules.
Turn missing product compliance evidence into a supplier email and upload link workflow.
Supplier delivery does not prove validity; identity, scope, model match and document status need review.
Export a SKU-level evidence pack zip for manual compliance review and supplier follow-up.
An Evidence Pack improves traceability and response readiness; it cannot prevent complaints, takedowns, recalls or enforcement.
Do not classify every digital download as automatically covered or exempt; document the product, delivery model, software connection, and target market first.
The label 'digital product' alone is not enough to decide whether GPSR applies or does not apply.
GPSR distance-sale offers require postal and electronic contact details; whether a PO Box or service address is sufficient depends on the operator role and applicable rules.
ComplyFolio does not claim that every PO box, virtual office or service address satisfies GPSR duties.
Find missing traceability fields and generate supplier evidence tasks.
Which identifier is legally sufficient depends on the product and evidence; the checker only surfaces signals and conflicts.
platform-gpsr
Apply the same evidence boundary to Shopify and Etsy public listings.
Review Shopify product pages for GPSR readiness and generate platform-ready compliance fields.
The checker cannot see private Shopify admin fields, app settings or submission status.
Generate a review-ready CSV row for an existing Shopify product without inventing missing safety information.
Import behavior depends on the merchant's Shopify catalog and metafield definitions; review the preview before upload.
Use product links to organize Etsy GPSR readiness tasks and evidence.
Private Etsy account fields, platform moderation and handmade-product legal classification require separate review.
accessibility
Separate automated page signals from the manual testing needed for real journeys.
Check a single page for common accessibility issues and get a readiness-oriented report.
A single automated scan cannot establish EAA compliance or WCAG conformance.
Checkout requires scripted and manual journey testing; a public product-page scan cannot verify private payment and account steps.
Public URL automation cannot verify private account, fraud, third-party payment or assistive-technology behavior by itself.
Quality policy
Pages outside this reviewed core remain available for improvement but are temporarily excluded from indexing and the sitemap. New pages enter this hub only after they add distinct user value, evidence and source coverage.
Read the editorial and correction standard · See what changed