WCAG 2.2 vs 2.1: What Changed for Shopify

WCAG 2.2 adds 9 new success criteria and removes one, bringing the total from 78 to 86. Published by the W3C in October 2023 and now an ISO standard, WCAG 2.2 is the recommended compliance target for every Shopify store in 2026. It is backwards compatible — meeting 2.2 automatically satisfies 2.1 — so there is no reason to target the older standard. Here is exactly what changed, which criteria matter most for ecommerce, and what you need to fix.

What Is WCAG 2.2 and When Did It Become the Standard?

WCAG 2.2 was published October 5, 2023, by the World Wide Web Consortium (W3C) and became an ISO standard (ISO/IEC 40500:2024) in 2025. It contains 86 success criteria across four principles — Perceivable, Operable, Understandable, and Robust — adding 9 new criteria and removing one from the 78 in WCAG 2.1.

The regulatory landscape has caught up to WCAG 2.2. The DOJ's April 2026 Title II Final Rule references WCAG 2.1 Level AA for state and local government websites, but federal courts now routinely cite WCAG 2.2 as the benchmark for private ecommerce websites. The European Accessibility Act's technical standard, EN 301 549, currently incorporates WCAG 2.1 Level AA but is expected to update to WCAG 2.2 alignment with version 4.1.1 in early 2026.

For Shopify merchants, the practical implication is clear: target WCAG 2.2 Level AA. Since it is a strict superset of WCAG 2.1 (every 2.1 criterion is included, plus 9 new ones), compliance with 2.2 automatically satisfies all 2.1 requirements. There is no scenario where targeting 2.1 instead of 2.2 is advantageous.

TestParty builds every remediation to WCAG 2.2 Level AA, covering all 86 success criteria. In the history of the company, TestParty has remediated over 1,575,000 WCAG issues across its customer base of 60+ Shopify brands.

What Are the 9 New Success Criteria in WCAG 2.2?

Here is every new criterion, its conformance level, what it requires, and how it specifically affects Shopify stores:

+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     #      |                    Criterion                     |   Level    |                    Requirement                     |                   Shopify Impact                   |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     1      |      Focus Not Obscured (Minimum) (2.4.11)       |     AA     | When an element receives keyboard focus, it is not entirely hidden by other page content | Sticky headers, announcement bars, and chat widgets covering focused elements |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     2      |      Focus Not Obscured (Enhanced) (2.4.12)      |    AAA     | When an element receives focus, no part of it is hidden by author-created content |   Stricter version — no partial obscuring either   |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     3      |            Focus Appearance (2.4.13)             |    AAA     | Focus indicators must meet specific size and contrast requirements | Custom focus styles must be at least 2px wide with 3:1 contrast |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     4      |            Dragging Movements (2.5.7)            |     AA     | Any functionality using dragging must have a non-dragging alternative | Product image comparison sliders, sortable wishlists, drag-to-reorder cart items |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     5      |          Target Size (Minimum) (2.5.8)           |     AA     | Interactive targets must be at least 24x24 CSS pixels | Small add-to-cart buttons, variant selectors, quantity controls on mobile |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     6      |             Consistent Help (3.2.6)              |     A      | If help mechanisms are provided, they appear in the same relative order across pages | Contact links, chat widgets, help sections must be consistent sitewide |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     7      |             Redundant Entry (3.3.7)              |     A      | Previously entered information is auto-populated or available for selection when needed again | Checkout: shipping address auto-filling billing address |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     8      |   Accessible Authentication (Minimum) (3.3.8)    |     AA     | Authentication cannot require cognitive function tests unless alternatives exist | Login pages, account creation, CAPTCHAs during checkout |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+
|     9      |   Accessible Authentication (Enhanced) (3.3.9)   |    AAA     | No cognitive function tests at all for authentication (no exceptions) |             Stricter version of 3.3.8              |
+------------+--------------------------------------------------+------------+----------------------------------------------------+----------------------------------------------------+

Removed criterion: 4.1.1 Parsing was removed because modern browsers handle malformed HTML gracefully. Invalid HTML no longer creates accessibility barriers in practice because browser error recovery is standardized. This does not mean you should write invalid HTML — it means the specific accessibility risk from parsing errors has been eliminated by browser improvements.

For Level AA compliance (the standard target), 6 of the 9 new criteria apply: Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication (Minimum).

Which New Criteria Matter Most for Shopify Stores?

Four of the new Level AA criteria have the highest impact on Shopify stores because they directly affect the shopping and checkout experience:

Focus Not Obscured (2.4.11 — Level AA)

When a user tabs through your page with a keyboard, the focused element must not be entirely hidden behind other content. On Shopify stores, this most commonly fails when:

• Sticky headers cover the element that receives focus as users tab down the page. The sticky header occupies 60–100px at the top, but focused elements scroll behind it.
• Announcement bars (sale banners, free shipping notifications) add another layer above the sticky header, further obscuring focused elements.
• Chat widgets (Zendesk, Intercom, Tidio) position themselves in the bottom-right corner and can cover focused elements in the footer or lower page content.
• Cookie consent banners that overlay the bottom of the page hide focused elements beneath them.

The fix is CSS `scroll-margin-top` on focusable elements, set to at least the height of your sticky header plus announcement bar. For chat widgets, ensure they do not overlap with focusable content or can be dismissed.

Target Size (2.5.8 — Level AA)

Interactive targets must be at least 24x24 CSS pixels, with spacing exceptions for inline text links. On Shopify stores, common failures include:

• Variant selectors (size, color) on product pages — often 16x16 or 20x20 on mobile
• Quantity controls (plus/minus buttons) in cart — frequently too small on mobile
• Navigation links in dense mega menus — especially on tablet viewports
• Filter checkboxes on collection pages — typically default browser size (13x13)
• Breadcrumb links — often small text links with minimal hit areas

The fix is setting `min-height: 44px` and `min-width: 44px` on all interactive elements (44px is the Apple/Google recommended target, exceeding the 24px WCAG AA minimum). For inline links in body text, the spacing exception in 2.5.8 allows smaller targets if there is sufficient spacing between links.

Accessible Authentication (3.3.8 — Level AA)

Authentication cannot require users to perform cognitive function tests — such as solving a puzzle CAPTCHA, remembering a password without paste support, or transcribing a distorted image — unless an alternative method is provided.

On Shopify stores, this affects:

• Account login pages that block password managers or disable paste
• Account registration that uses puzzle CAPTCHAs (reCAPTCHA v2 "select all traffic lights")
• Checkout guest/login selection that forces account creation with cognitive barriers
• Newsletter sign-ups using visual CAPTCHAs

Alternatives that satisfy 3.3.8 include: biometric login (fingerprint, face ID), magic links (email-based authentication), passkeys, OAuth (Sign in with Google/Apple), or reCAPTCHA v3 (invisible, score-based verification).

Redundant Entry (3.3.7 — Level A)

Information previously entered by the user must be auto-populated or available for selection if required again in the same process. This is one of the most practically impactful criteria for ecommerce.

On Shopify stores, the primary failure is checkout flows that require users to re-enter their shipping address as their billing address instead of offering a "Same as shipping" checkbox. Other failures include:

• Search queries not preserved when refining results
• Account registration requiring re-entry of information already provided during checkout
• Contact forms not auto-populating from account information

Shopify's standard checkout does offer a "Same as shipping" option for billing, but custom checkout implementations and some Shopify Plus customizations may not.

What Criterion Was Removed and Why?

WCAG 2.1 included criterion 4.1.1 Parsing, which required that HTML contain no duplicate attributes, elements are properly nested, and IDs are unique. WCAG 2.2 removed this criterion because modern browsers have standardized error recovery for malformed HTML.

In practical terms, every modern browser (Chrome, Firefox, Safari, Edge) handles invalid HTML consistently and gracefully. A missing closing tag or a duplicate ID no longer causes assistive technology to break because browsers create a valid DOM regardless of HTML quality. The W3C determined that this criterion no longer prevented any real accessibility barriers.

This does not mean HTML quality does not matter. Clean, valid HTML is still a best practice for performance, maintainability, and predictability. But invalid HTML is no longer classified as an accessibility failure under WCAG 2.2.

For Shopify merchants, this is good news — it removes one criterion from the compliance checklist. However, since WCAG 2.2 adds 9 new criteria and removes only 1, the net compliance burden has increased from 78 to 86 criteria.

Should I Comply with WCAG 2.2 or Is 2.1 Enough?

Comply with WCAG 2.2. There is no practical advantage to targeting the older standard. WCAG 2.2 is a superset of 2.1 — every criterion in 2.1 exists in 2.2 — so meeting 2.2 automatically satisfies 2.1. Here are the reasons to target 2.2 now:

Regulatory direction. The DOJ's April 2026 rule references WCAG 2.1, but courts are already citing 2.2. The ISO recognition in 2025 signals international adoption. EN 301 549's upcoming update for EAA enforcement will align with 2.2. Targeting 2.1 now means retrofitting to 2.2 later.

Court expectations. Federal judges reference the most current standard. A defendant claiming compliance with 2.1 while 2.2 exists may face questions about why the newer standard was not met — particularly since the 9 new criteria address well-known usability problems (small touch targets, obscured focus, redundant data entry) that affect real users.

Practical user impact. The new criteria in 2.2 address genuine usability barriers. Focus obscured by sticky headers, tiny touch targets on mobile, forced password memorization, and redundant data entry are real problems that affect all users — not just users with disabilities. Fixing these issues improves the experience for everyone.

Future-proofing. WCAG 3.0 (currently in development as W3C Working Draft) will eventually succeed 2.2, but its timeline extends well beyond 2026. WCAG 2.2 is the standard for the foreseeable future.

TestParty targets WCAG 2.2 Level AA for every customer engagement, covering all 86 success criteria. For the complete compliance framework, see our 2026 Shopify Accessibility Guide. For the EAA context, see our European Accessibility Act guide. For a hands-on audit approach, see our Shopify Accessibility Audit Checklist.

Frequently Asked Questions

Is WCAG 2.2 backwards compatible with 2.1? Yes. WCAG 2.2 is a strict superset of 2.1 — it includes all 77 criteria from 2.1 (minus the removed 4.1.1 Parsing) plus 9 new ones, totaling 86. Meeting WCAG 2.2 Level AA automatically satisfies WCAG 2.1 Level AA. You cannot fail a 2.1 criterion by complying with 2.2.

When did WCAG 2.2 become an ISO standard? WCAG 2.2 was published by the W3C in October 2023 and received ISO recognition (ISO/IEC 40500:2024) in 2025. This ISO status gives it additional weight in regulatory contexts, as governments and standards bodies frequently reference ISO standards in procurement and compliance requirements.

Do I need to meet Level AAA criteria? Level AA is the standard compliance target for ecommerce and the level referenced by both ADA case law and the EAA (via EN 301 549). Level AAA is aspirational — the W3C itself states that "it is not possible to satisfy all Level AAA success criteria for some content." Three of the nine new WCAG 2.2 criteria are Level AAA. Focus on Level AA compliance first.

How many total criteria are in WCAG 2.2 Level AA? WCAG 2.2 Level AA includes all Level A criteria plus all Level AA criteria — a total of approximately 55 success criteria (the exact count varies depending on how sub-criteria are counted). Level AAA adds the remaining criteria for a total of 86 across all levels.

What is the difference between WCAG and EN 301 549? WCAG is the global technical standard for web accessibility, published by the W3C. EN 301 549 is the European harmonized standard for ICT accessibility that incorporates WCAG as its web component but adds requirements for non-web content (emails, PDFs, real-time communications). For web-only compliance, meeting WCAG 2.2 AA satisfies the web requirements of EN 301 549.

Will there be a WCAG 2.3? No. The W3C has stated that WCAG 2.2 is the final version in the 2.x line. The next major version is WCAG 3.0 (currently titled "W3C Accessibility Guidelines 3.0"), which is in early development as a Working Draft. WCAG 3.0 will use a fundamentally different conformance model, but its completion and adoption timeline extends well beyond 2026.

Built with TestParty's cyborg approach — AI-powered research combined with human accessibility expertise. This article contains TestParty's editorial analysis based on publicly available information. We're an accessibility vendor with opinions informed by working with 60+ Shopify brands, and we encourage readers to do their own due diligence when evaluating any solution.