Guides
Shopify accessibility for apparel and fashion stores.
Defensible WCAG 2.2 AA documentation for apparel and fashion Shopify storefronts. Choose your state for location-specific guidance.
Apparel storefronts live and die on product selection UI: color swatches, size pickers, style variant grids. These are almost always custom components built on top of Shopify's variant API, and custom components are where WCAG failures concentrate. A shopper who navigates by keyboard or uses a screen reader encounters the same product page as everyone else, but the interactive layer is frequently invisible to them.
Paperfort's automated axe-core scan runs against your live storefront pages, including collection grids and product detail pages, and produces three documents: a timestamped WCAG 2.2 AA audit report with a prioritized remediation list, a completed VPAT 2.5Rev, and a hosted accessibility statement for your domain. Automated scans detect only a portion of WCAG issues (roughly a third to half by industry estimates), so the report also flags where manual review is still needed.
- 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 Apparel & Fashion Shopify stores
Color and size variant swatches with no accessible name
WCAG 1.4.1, 4.1.2Swatch buttons rendered as styled <button> or <span> elements with only a background color and no visible text, aria-label, or title attribute give screen readers nothing to announce beyond "button." WCAG 1.4.1 (Use of Color) is also at risk when the only indicator that "Cobalt" is selected is a colored ring with no text confirmation.
Size guide modal that traps keyboard focus
WCAG 2.1.2Size guide overlays that open as a modal but do not implement focus trapping correctly leave keyboard users stranded: Tab stops at the last interactive element inside the modal and wraps to the browser chrome rather than cycling within the dialog. WCAG 2.1.2 (No Keyboard Trap) requires that focus can be moved away using standard keys alone.
Product gallery thumbnails with empty or filename alt text
WCAG 1.1.1Thumbnails in product image carousels are often uploaded with auto-generated names like IMG_3042.jpg or shipped with alt="" on images that are not decorative. WCAG 1.1.1 (Non-text Content) requires a text alternative that conveys the same information the image conveys, such as the colorway or angle being shown.
Low-contrast "Sold Out" and sale price badges
WCAG 1.4.3"Sold Out" overlays and red sale-price badges are frequently styled with light text on a medium-toned background that passes a visual glance but fails the 4.5:1 contrast ratio required by WCAG 1.4.3 (Contrast Minimum) for text under 18pt. Collection grid pages can have dozens of these badges firing the same violation.
Apparel & Fashion accessibility: common questions
- Do color swatch buttons count as interactive elements that need accessible names?
- Yes. Any element a shopper activates to select a variant, whether built as a
<button>, a radio input, or a styled<div>with a click handler, is an interactive control under WCAG 4.1.2. It needs a programmatically determinable name: anaria-labelwith the color name, an associated visible label, or atitleattribute at minimum. - Our size guide is a pop-up, not a full modal. Does the same focus-trap rule apply?
- WCAG 2.1.2 (No Keyboard Trap) applies whenever keyboard focus enters a component and cannot leave using Tab, Shift+Tab, Escape, or another standard key. Whether you call it a pop-up, a drawer, or a flyout, if Tab gets stuck inside, the criterion is at risk. The WAI-ARIA dialog pattern specifies exactly how to manage focus correctly.
- We added alt text in Shopify's admin. Is that enough to pass WCAG 1.1.1?
- Adding alt text is the right step, but the automated scan also checks whether the text is empty (
alt="") on non-decorative images and flags filename-style values. WCAG 1.1.1 requires the alternative to convey the purpose of the image. Whether the text is meaningful is a judgment call that only manual review can verify, not an automated scanner.
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.