Should a Shopify brand publish an accessibility conformance report?
Publishing an accessibility conformance report, usually a VPAT, is a strong trust signal for B2B buyers and enterprise partners, and a reasonable transparency move for any brand. But a stale or inflated report is worse than none: it becomes evidence against you. Publish only if the report is honest, dated, and maintained.
What a conformance report actually is
An accessibility conformance report (ACR) documents how a product or site measures against an accessibility standard, most commonly WCAG 2.2. The VPAT (Voluntary Product Accessibility Template) is the standard format: a table where each success criterion gets a conformance level of Supports, Partially Supports, or Does Not Support, with remarks explaining the basis.
VPATs come from enterprise software procurement, where buyers require them before signing. Ecommerce brands encounter them when selling to enterprise customers, working with large retail partners, or responding to RFPs. Publishing one voluntarily puts the brand ahead of that conversation.
When publishing helps
If the brand sells to other businesses, runs a wholesale or enterprise channel, or courts large partners, a public ACR answers the accessibility question before it is asked. Procurement teams know the format, and a current, credible report shortens their review.
It also helps with customers directly. A brand that publishes its conformance level, including the gaps, reads as serious about accessibility in a way that a vague "we care about accessibility" statement never does. Honesty about partial support is more credible than a claim of perfection that falls apart on the first scan.
When publishing hurts
A conformance report is a dated claim about a moving target. If the store's theme updates, apps change, or content shifts after the report date, the report quietly goes stale. A plaintiff's attorney comparing a two-year-old "Supports" claim against today's broken checkout will not treat the discrepancy kindly.
The other failure mode is inflation. Marking criteria as "Supports" based on a quick automated scan, without manual testing, produces a report that does not survive scrutiny. Every inflated line is a promise the store cannot keep. If the report is not built on real testing, do not publish it.
What a credible report contains
Use the current VPAT format from the Information Technology Industry Council, and fill it against WCAG 2.2 Level AA. For each criterion, state the conformance level plainly and write remarks that reference actual testing: which pages were tested, what methods were used, and when. Name the evaluation date prominently, and list known limitations rather than hiding them.
Keep the scope honest. A report that covers the storefront templates but not the checkout, or the desktop experience but not mobile, should say so. Partial scope, clearly stated, is credible. Implied full coverage that is not real is a liability.
Maintain it or remove it
Treat the report like any other compliance document: review it on a schedule, at least annually and after any major theme change, migration, or redesign. Each review gets a new date and a new version. Archive old versions rather than deleting them, since the history shows continuous attention.
If the brand cannot commit to maintenance, do not publish. An accessibility statement with a feedback contact is a lighter commitment that still shows good faith. The conformance report is for brands ready to stand behind a specific, dated claim and keep it true.