# WCAG 2.2 for Shopify stores: what changed and what to check Source: https://suitshieldhq.com/blog/2026-10-19-wcag-22-shopify-stores-what-changed.html Reviewed October 19, 2026 WCAG 2.2 added criteria that touch everyday store patterns: focus visibility, target size, dragging, and redundant entry. A merchant friendly tour of the new requirements and where Shopify stores commonly fail them. ## A short version of a long document The Web Content Accessibility Guidelines version 2.2 refined the widely adopted 2.1 standard, adding a small set of new success criteria and removing one obsolete one. For merchants, the significance is practical: accessibility expectations in procurement, platform requirements, and legal arguments increasingly reference the current version, and its new criteria target patterns that online stores use every day. Nothing in 2.2 overturns 2.1 fundamentals. Alt text, labels, contrast, keyboard access, and error handling remain the foundation where most store failures live. The 2.2 additions are best understood as precision strikes on newer interaction habits: tiny tap targets, focus hidden under sticky bars, drag only controls, and forms that make shoppers retype what the store already knows. ## Focus, visible and not obscured Two criteria concern focus. The indicator showing where keyboard focus sits must be clearly visible, and, new in 2.2, it must not be hidden by other content. Sticky headers, announcement bars, and cookie banners are the classic offenders in stores: the focused link sits perfectly correctly, underneath a fixed bar, invisible to the person tabbing toward it. Test by tabbing through your store slowly with every banner and popup in its natural state. If focus disappears behind furniture, the fix is usually scroll spacing and z order discipline rather than redesign. Enhanced levels of the guidelines ask for even stronger focus appearance, and designing toward them while you fix the basics costs little extra. ## Target size, dragging, and authentication A minimum target size criterion sets a floor of twenty four by twenty four pixels for interactive elements, with spacing exceptions, aiming at the cramped social icons, tiny close buttons, and dense pagination that punish shoppers with motor difficulties and everyone on a moving train. Audit your icon rows and footer links first; that is where sub floor targets cluster. Dragging movements must have a single pointer alternative, so a slider that only drags, for price filters or before and after images, needs buttons or inputs that achieve the same result. Accessible authentication requires that logging in not depend on a memory or puzzle test alone; object recognition and personal content recognition offer more humane paths, and modern passcode and passkey flows align well with the intent. ## Redundant entry and consistent help If your checkout or account flows ask for the same information twice in one process, the guidelines expect it to be auto filled or selectable from what was already given, with narrow security exceptions. Stores trip this in delivery forms, gift options, and account creation bolted awkwardly onto checkout. Map each field you ask for twice and ask the form, out loud, why. Consistent help requires that contact mechanisms, chat, help links, self service pages, appear in the same relative order across pages when repeated. Shoppers build spatial memory of where help lives; moving it per page template taxes exactly the users who need it most. A footer and header audit against this criterion takes an hour and usually finds a template that wandered from the pattern months ago. ## Related reading If this topic is useful, these earlier guides go deeper on connected questions: [Planning a Shopify accessibility audit: cost, timeline, and scope](https://suitshieldhq.com/blog/2026-10-18-shopify-accessibility-audit-cost-timeline-planning.md), [Writing an accessibility statement for your Shopify store](https://suitshieldhq.com/blog/2026-10-18-accessibility-statement-shopify-store-what-include.md), and [What a VPAT is, and when a Shopify store actually needs one](https://suitshieldhq.com/blog/2026-10-17-vpat-shopify-store-when-needed.md). ## Frequently asked questions ### Do I need to comply with WCAG 2.2 or is 2.1 enough? Most legal and platform expectations still reference 2.1 at AA level, while guidance and procurement increasingly point to 2.2, which is backward compatible in spirit. Working to 2.2 AA covers 2.1 in the areas that matter for stores, with one obsolete parsing criterion removed. Aim at 2.2; it future proofs the work and its additions fix real shopper pain. ### What is the fastest WCAG 2.2 win for a typical store? Unobscuring keyboard focus under sticky bars and banners, and enlarging the smallest tap targets in icon rows and mobile menus. Both are afternoon scale fixes once found, both are testable by hand, and both affect every page. A tab through your store and a thumb through your footer will locate most instances in an hour. ### Does WCAG 2.2 change anything about checkout? Hosted checkout remains the platform's responsibility, but your pre checkout steps, cart, account, and form flows are yours. Redundant entry and accessible authentication bite hardest there: review address re entry, repeated email asks, and any login or verification step your apps add. The criteria do not demand rebuilding checkout; they demand removing needless repetition and memory tests from your parts of the journey. ### How should I verify 2.2 issues without an auditor? Manual checks cover the new criteria surprisingly well: tab for focus visibility, measure a sample of targets, attempt every drag control with buttons alone, and submit your longest form watching for repeated questions. Automated tools catch little of 2.2. A structured manual pass, documented, is a legitimate first audit before professional testing of critical flows.