Guides
Shopify accessibility for supplements and wellness stores.
Defensible WCAG 2.2 AA documentation for supplements and wellness Shopify storefronts. Choose your state for location-specific guidance.
Supplements and wellness storefronts carry a category of content almost no other Shopify vertical touches: structured regulatory information. Supplement Facts panels, serving-size tables, dosage instructions, and structure/function claims are all legally required disclosures, and they are routinely published in formats that are entirely opaque to assistive technology. An image of a label is not text. A table without headers is not navigable.
Paperfort scans your live storefront pages against WCAG 2.2 AA using axe-core, then delivers an audit report with a prioritized remediation list, a completed VPAT 2.5Rev, and a hosted accessibility statement on your domain. Because automated scans detect only a portion of WCAG issues (roughly a third to half), the report distinguishes machine-detectable findings from criteria that still need a qualified professional.
- California
- New York
- Texas
- Florida
- Illinois
- Pennsylvania
- Ohio
- Georgia
- North Carolina
- Michigan
- Virginia
- Washington
- Arizona
- Massachusetts
- New Jersey
- Tennessee
- Indiana
- Colorado
- Maryland
- Missouri
Common WCAG 2.2 AA failures in Supplements & Wellness Shopify stores
Supplement Facts panel rendered as a flat image
WCAG 1.1.1Many supplement brands upload a photo or PNG of the Supplement Facts label rather than marking it up as HTML. WCAG 1.1.1 (Non-text Content) requires a text alternative for any non-text content that conveys information. A flat image with alt="supplement facts panel" is technically present but conveys none of the per-nutrient data to screen reader users.
Dosage and serving-size tables missing row and column headers
WCAG 1.3.1Tables listing ingredients, amounts per serving, and percent daily values are common on product pages, but they are often built with <div> or plain <td> elements that carry no scope attribute or <th> markup. WCAG 1.3.1 (Info and Relationships) requires that table headers are programmatically associated with their cells so a screen reader can announce which column a value belongs to.
Structure/function claims conveyed by color or styling alone
WCAG 1.3.3, 1.4.1Product pages that highlight claims such as "supports immune health" using a colored badge, a bold green label, or a highlighted band rely on visual presentation to carry meaning. WCAG 1.3.3 (Sensory Characteristics) and 1.4.1 (Use of Color) require that information is not conveyed by color, shape, size, or visual location as the only differentiator.
Subscribe-and-save purchase option without an accessible label
WCAG 4.1.2Subscribe-and-save toggles or radio groups are often custom-built widgets where the visual label ("Subscribe & Save 15%") is not programmatically associated with the input control. WCAG 4.1.2 (Name, Role, Value) requires that the accessible name of the control can be determined by assistive technology, typically via aria-label or a proper <label for> association.
Supplements & Wellness accessibility: common questions
- Is an image of the Supplement Facts panel enough if it has alt text?
- Alt text on a Supplement Facts image satisfies the presence requirement in WCAG 1.1.1, but only if the alt text actually conveys the information in the panel. Saying
alt="supplement facts"does not communicate ingredient amounts or percent daily values. Full compliance requires either descriptive alt text covering all data or the panel marked up as an accessible HTML table. - Our dosage table looks fine visually. Why would it fail WCAG?
- WCAG 1.3.1 (Info and Relationships) requires that relationships conveyed visually, such as which column header applies to a given cell, are also programmatically determinable. A table can look correct on screen but still fail if the headers are built with
<td>instead of<th scope>, because a screen reader cannot associate values with their column labels. - We use a third-party subscription app for subscribe-and-save. Who is responsible for fixing the WCAG issues in it?
- From a WCAG conformance standpoint, the page that contains the non-conforming content is the page at risk, regardless of which app injected it. Paperfort's audit report documents which elements on your storefront fail and where they appear, so you have specific evidence to bring to the app vendor or your development team.
Other industries
Paperfort produces defensible WCAG 2.2 AA documentation — an audit report, a hosted accessibility statement page, and a VPAT 2.5. It is documentation, not an overlay widget, and it is not legal advice.