WCAG 2.1 AA Compliance Checklist for Shopify Store Owners

WCAG 2.1 Level A and AA success criteria are a useful technical baseline for reviewing a Shopify storefront. Legal and contractual requirements vary, and a checklist or automated scan does not establish conformance. The handling notes below distinguish automated-rule candidates from manual or specialist evaluation; any source change still depends on safe mapping, merchant approval, supported Shopify paths, and post-change testing.

Images & Non-Text Content

WCAG Success Criterion 1.1.1 requires that all non-text content has a text alternative that serves an equivalent purpose.

• Product images have equivalent text alternatives. Review the purpose and surrounding context; generated candidates require merchant review. Handling: automated rule candidate plus human content review.
• Decorative images use empty alt attributes. Background graphics, spacers, and decorative icons may need alt="" so screen readers skip them. Handling: automated candidate only when decorative intent is unambiguous.
• Icon buttons have accessible names. Test the computed name of cart, search, menu, and other icon-only controls. Handling: automated detection candidate; labels need contextual review.
• Complex images have adequate alternatives. Charts, infographics, and sizing guides may need detailed adjacent descriptions. Handling: manual content review.

Color & Contrast

WCAG Success Criteria 1.4.3 and 1.4.11 set minimum contrast ratios for text and UI components.

• Body text meets the applicable 4.5:1 contrast ratio. Measure rendered foreground and background colors. Handling: automated candidate; verify actual states and imagery.
• Qualifying large text meets 3:1. WCAG defines large text in points (18pt regular or 14pt bold, with equivalent CSS sizes). Handling: automated candidate with rendered-style verification.
• Required visual boundaries and states meet non-text contrast rules. Handling: automated candidates plus manual state review.
• Color is not the only means of conveying information. Error, required, and status cues need another perceivable signal. Handling: manual review.

Forms & Inputs

Form accessibility is critical for checkout flows, account creation, and newsletter signups.

• Inputs have appropriate programmatic labels. Handling: automated detection candidate; label purpose and quality require review.
• Error messages are descriptive and associated with the relevant fields. Handling: automated structure checks plus manual task-flow testing.
• Required fields are indicated programmatically. Do not rely only on a color or symbol. Handling: manual review.
• Instructions appear where users need them. Handling: manual content and task-flow review.

Navigation & Keyboard

All functionality must be operable through a keyboard interface (WCAG 2.1.1).

• A working bypass mechanism is available. A skip link is one common technique. Handling: automated structure candidate plus keyboard verification.
• Interactive elements are keyboard operable with the expected keys. Handling: manual testing across representative states.
• Focus indicators are visible and usable. Handling: automated CSS candidate plus manual visual checks.
• No keyboard traps occur. Handling: manual keyboard testing.
• Focus order is logical. Handling: manual keyboard and screen-reader review.

Headings & Structure

• Page headings identify and organize content. One clear page-level heading is a common pattern, but WCAG does not impose a universal one-h1 rule. Handling: automated structure candidate plus manual meaning review.
• Heading levels communicate a coherent hierarchy. Handling: automated candidate plus manual context review.
• Heading elements are not empty or used only for styling. Handling: automated candidate with source review.

ARIA & Landmarks

• Landmark regions help identify page areas. Handling: automated structure candidate plus screen-reader review.
• ARIA roles and properties match actual behavior. Handling: automated syntax candidates plus manual interaction testing.
• Interactive widgets expose current names, roles, values, and states. Handling: manual testing; some missing attributes may be automated candidates.

Mobile & Touch

• Pointer targets meet the applicable target-size criterion. WCAG 2.1 SC 2.5.5 is a Level AAA 44×44 criterion; WCAG 2.2 adds the Level AA 24×24-or-spacing criterion in SC 2.5.8, with exceptions. Handling: automated candidates plus manual spacing/state review.
• Content can be resized and reflowed as required. Do not treat a viewport meta check as a complete zoom/reflow test. Handling: manual responsive testing supported by automated checks.
• Orientation is not unnecessarily locked. Handling: manual device review.

Language & Internationalization

• The page language is programmatically identified. Handling: automated attribute candidate plus verification of the actual locale.
• Language changes within content are identified where required. Handling: manual content review.

Video & Multimedia

• Prerecorded media has the alternatives required for its content and scope. Handling: manual media review and content creation.
• Important visual information has an appropriate alternative. Handling: manual media review.
• Moving or auto-playing content provides the required controls. Handling: automated candidates plus manual interaction testing.

Using This Checklist

This checklist highlights practical review areas rather than reproducing every normative requirement and exception. An AccessComply scan can map eligible automated findings from public pages and states it reaches to relevant WCAG criteria; it cannot establish full site coverage or WCAG conformance.

Plan manual review around material theme, content, and app changes and at a cadence appropriate to your release process. Include representative keyboard, screen-reader, zoom/reflow, media, document, and purchase-flow testing.

Further Reading

• How to Fix Common Accessibility Issues on Shopify: A Technical Guide
• WCAG 2.2 for Shopify Merchants: What's New and What You Need to Fix
• How to Fix Shopify Accessibility Issues Without Hiring a Developer
• European Accessibility Act 2025: What Shopify Merchants Selling to the EU Must Do Now