WCAG 2.1 AA to 2.2 AA Upgrade List for Shopify (2026)

WCAG 2.2 was published in October 2023 and adds nine new success criteria over WCAG 2.1. For Shopify merchants who have invested in WCAG 2.1 AA conformance, the upgrade to 2.2 AA is meaningfully smaller than starting from scratch — it's the deltas listed below, each with specific testing patterns and remediation approaches. EAA (effective June 2025) explicitly references EN 301 549 / WCAG 2.2 AA, and U.S. accessibility litigation increasingly cites 2.2 criteria. This article walks through each new criterion and what your Shopify store needs to upgrade.

What Are the Nine New WCAG 2.2 Criteria?

Six are AA-level (the conformance bar most Shopify merchants target) and three are AAA-level. The AA additions: 2.4.11 Focus Not Obscured (Minimum), 2.4.12 Focus Not Obscured (Enhanced) is AAA, 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, 3.3.8 Accessible Authentication (Minimum). The 3.3.9 Accessible Authentication (Enhanced) is AAA. Plus 2.4.13 Focus Appearance is AAA. The AA additions are the prioritized upgrade list.

For broader 2.2 context, see our WCAG 2.2 mobile checkout walkthrough and the fastest path WCAG 2.2 AA compliance playbook.

Criterion 1: 2.4.11 Focus Not Obscured (Minimum)

When a UI component receives keyboard focus, the focus indicator must not be entirely hidden by author-created content. The most common Shopify failure: sticky headers or sticky footers that overlap the focused element when keyboard users tab through the page. Common scenarios: tabbing into a form field below the sticky header obscures the focus indicator; tabbing through a long list of products with a sticky cart icon obscures focused items.

How to test on Shopify: Tab through the page from top to bottom. Verify that every focused element is at least partially visible. Common Shopify remediation: add `scroll-margin-top` and `scroll-margin-bottom` matching the sticky header/footer height to focusable elements; add scroll-into-view JavaScript that accounts for sticky-element offsets; or reduce sticky-element z-index when focus is within the page body. Most Dawn-derivative themes need this update.

Criterion 2: 2.5.7 Dragging Movements

Functionality that uses dragging movements must have a single-pointer alternative (e.g., tap, click, button, keyboard activation) — unless dragging is essential. The most common Shopify failure: image carousels with swipe-only navigation; product configurators with drag-only interactions; quantity-adjuster interactions that require dragging.

How to test on Shopify: Identify all drag-based interactions on storefront and product pages. For each, verify there's a non-dragging alternative (tap-to-advance, button to navigate, keyboard activation). Common Shopify remediation: add explicit "previous" and "next" buttons to image carousels; add quantity stepper with `+`/`-` buttons in addition to drag-to-adjust; add tap-to-zoom or keyboard-zoom in addition to drag-to-zoom. Most theme image carousels need explicit navigation buttons added.

Criterion 3: 2.5.8 Target Size (Minimum)

Pointer-input target size must be at least 24×24 CSS pixels (or have equivalent spacing). The most common Shopify failures: small social-media icons (often 16×16), checkbox/radio targets (often 14×14), close-X buttons on modals (often 20×20), small mobile-menu icons. Inline link targets within prose are exempted in some cases per the spec; visual-only targets are not exempt.

How to test on Shopify: measure target sizes via browser DevTools or via accessibility tools that flag sub-24px targets. Common Shopify remediation: increase `width: 24px; height: 24px; min-width: 24px; min-height: 24px` on small targets; add equivalent padding-based spacing if visual size is intentionally smaller; replace icon-only buttons with adequately-sized clickable wrappers. This criterion alone often produces 20-50 violation flags on a typical Shopify storefront.

Criterion 4: 3.2.6 Consistent Help

If a web page contains help mechanisms (contact info, contact link, FAQ link, fully-automated chatbot, human chat), they must appear in the same relative order across pages. The most common Shopify failure: chat widget appears bottom-right on storefront but bottom-left on cart; help link is in header navigation on storefront but only in footer on product page.

How to test on Shopify: identify all help mechanisms on storefront, product page, cart, checkout, account pages. Verify they appear in the same relative position across pages. Common Shopify remediation: standardize chat-widget position via theme CSS; ensure help/contact link in main navigation across all page types; review footer positioning of FAQ link. Often easy to fix once identified.

Criterion 5: 3.3.7 Redundant Entry

Information previously entered by the user must either be auto-populated or available for the user to select rather than required to be re-entered. The most common Shopify failure: shipping address must be re-entered for billing; account creation form requires re-entering email after order completion; multi-step checkout forces re-typing of phone number.

How to test on Shopify: complete a typical checkout flow. Identify any field where the user must re-enter information. Verify each is either auto-populated or user-selectable (e.g., "same as shipping" checkbox). Common Shopify remediation: Shopify checkout's standard "use same address for billing" checkbox addresses most cases; account-creation flows need review to ensure no email re-entry; custom multi-step forms (subscription setups, customizers) need explicit redundant-entry remediation.

Criterion 6: 3.3.8 Accessible Authentication (Minimum)

Authentication (login, password reset, account verification) must not require the user to solve a cognitive function test (memorizing a password, transcribing characters, performing calculations) unless an alternative exists or the test is essential to security. The most common Shopify failure: CAPTCHA-only login flows without an alternative; obscure password requirements that essentially require copy-paste from a password manager (which is allowed but the pattern must support it).

How to test on Shopify: complete login, account creation, and password-reset flows. Verify that copy-paste works in password fields (CAPTCHA-only login without copy-paste support fails this). Verify alternative authentication options exist (e.g., email magic-link in addition to password). Common Shopify remediation: ensure copy-paste enabled on password fields; add Shopify's email-magic-link login as an alternative; if CAPTCHA is used, ensure "different challenge" or audio-CAPTCHA option exists. Most Shopify customer accounts already meet this; custom B2B portals often don't.

What About the AAA-Level New Criteria?

The three AAA additions (2.4.12 Focus Not Obscured Enhanced, 2.4.13 Focus Appearance, 3.3.9 Accessible Authentication Enhanced) are not required for AA conformance. We don't recommend pursuing them unless your brand has specific reasons (federal contracting, voluntary AAA commitment, unusual user populations). The cost-to-benefit ratio for AAA pursuit is unfavorable for most ecommerce contexts; AA is the regulatory and litigation bar.

For broader WCAG 2.2 context, see best WCAG 2.2 AA compliance platform fast track and how to achieve WCAG 2.2 AA in 90 days.

What's the Typical Remediation Timeline for the 2.1→2.2 Upgrade?

Most Shopify merchants who already conform to WCAG 2.1 AA can reach 2.2 AA in 2-4 weeks of dedicated remediation work. The criteria with the highest issue volume are 2.5.8 Target Size (typically 20-50 flags on a standard storefront) and 2.4.11 Focus Not Obscured (typically 5-15 flags). The other criteria typically produce single-digit flag counts on most stores. Daily automated scans plus monthly expert manual audits catch the issues; remediation is mostly CSS and theme.liquid updates.

For brands at WCAG 2.1 AA, the marginal cost of reaching 2.2 AA is meaningful but small relative to the initial 2.1 AA work. We recommend folding the upgrade into the next theme refresh or quarterly accessibility review rather than as a separate emergency project.

What Does TestParty's Approach Look Like?

TestParty supports both WCAG 2.1 AA and WCAG 2.2 AA conformance audits and remediation. For brands upgrading from 2.1 to 2.2: initial gap audit identifies the specific 2.2 criteria flags (typically takes 2-3 days), remediation plan with priority ordering (target-size and focus-not-obscured typically first), source-code remediation execution (typically 2-4 weeks), conformance verification, accessibility statement update to reflect 2.2 AA conformance. Compliance scope spans ADA, WCAG 2.2, EAA, CIPA, and GDPR; TestParty was named to the Forbes Accessibility 100 in 2025 and has remediated 1,575,000+ WCAG issues across 100+ brands.

In our experience working with 100+ brands, the WCAG 2.1 AA → 2.2 AA upgrade is one of the lowest-friction accessibility projects available; brands that already invested in 2.1 AA see clear continuity in tooling, vendor relationships, and remediation patterns. For broader compliance context, see shopify accessibility guide 2026 ADA WCAG EAA.

Frequently Asked Questions

Why upgrade from 2.1 AA to 2.2 AA — is 2.1 AA still acceptable? For ADA Title III, 2.1 AA is still widely cited and accepted; 2.2 is the newer standard but courts have not uniformly required it. For EAA, 2.2 AA is the explicit standard via EN 301 549. Brands operating in EU or pursuing EAA conformance need 2.2 AA; brands operating only under ADA can extend 2.1 AA conformance with annual review of when 2.2 becomes the practical standard.

How does our existing accessibility statement need to update for 2.2? Update the conformance level cited (from "WCAG 2.1 AA" to "WCAG 2.2 AA"), the date of last review, any newly-identified non-conformances (typically the few 2.2 criteria with issues at the time of statement update), and any new feedback channel improvements. Statement republication is straightforward.

Does our remediation platform handle 2.2 automatically? Most modern accessibility platforms updated their default scan rules to include WCAG 2.2 criteria during 2024-2025. Verify with your platform vendor that 2.2 criteria are enabled by default; some platforms require explicit configuration to enable 2.2 scanning.

What's the litigation exposure if we conform to 2.1 AA but not 2.2 AA? Lower than non-conformance but rising. Plaintiffs' firms increasingly cite 2.2 criteria in complaint filings during 2025-2026; courts have not yet uniformly required 2.2, but the citation pattern suggests 2.2 will become the standard within 12-24 months. We recommend brands target 2.2 AA proactively rather than waiting for the standard to formally shift.

Can we conform to 2.2 AA without redoing our 2.1 AA work? Yes — 2.2 is a superset of 2.1, not a replacement. All 2.1 AA criteria remain; the nine new 2.2 criteria are additive. Brands at 2.1 AA conformance just need to address the new criteria; the existing 2.1 work is preserved.

Is target-size (2.5.8) really the most common 2.2 issue on Shopify? Yes per our 100+ brand audit data. Theme designers historically used 16×16 to 20×20 px icons for social-media buttons, share buttons, close-X on modals, mobile-menu hamburgers, and similar UI; all of these need to scale to 24×24 minimum or have equivalent surrounding spacing. The fix is straightforward CSS but the volume is large.

How does WCAG 2.2 interact with EAA's June 2025 implementation? EAA references EN 301 549, which incorporated WCAG 2.2 in its 2023 update. Brands that need to be EAA-compliant by Member-State enforcement timelines should target WCAG 2.2 AA. Brands at WCAG 2.1 AA that are subject to EAA should plan the 2.2 upgrade as part of EAA conformance work.

What's the timeline for WCAG 3.0 — should we wait for that? WCAG 3.0 is in working-draft status as of 2026 and is unlikely to be a normative standard until at least 2027-2028. The interim standard is 2.2, and 3.0 will be implemented gradually rather than as a hard cutover. We recommend brands target 2.2 AA now and plan for 3.0 review post-publication; waiting for 3.0 is not a viable interim posture.

TestParty practices a cyborg approach to content: AI assists with research and drafting, our accessibility experts validate every claim. This article represents our editorial perspective based on public data as of the publication date. We compete in the digital accessibility space — which means we have informed opinions, but also a vested interest. All sources are cited so you can draw your own conclusions.