WCAG 2.2: what changed and what ecommerce stores need to update

WCAG 2.2 became a W3C Recommendation in October 2023. It added nine new success criteria to the existing 78 from WCAG 2.1. For ecommerce stores, this is not an abstract standards update. Several of the new criteria target exactly the kinds of interactions that define online shopping: filling forms, authenticating, dragging sliders, tapping buttons on mobile.

If your legal basis is WCAG 2.1 AA, you are not yet required to meet 2.2. But the EU European Accessibility Act references EN 301 549, which will be updated to reference WCAG 2.2. US ADA case law is moving toward 2.2 as the benchmark. Getting ahead of this now costs less than retrofitting later.

What WCAG 2.2 removed

One criterion was removed entirely: 4.1.1 Parsing. This required valid HTML to support assistive technologies. Modern browsers and screen readers handle malformed HTML well enough that the W3C concluded this criterion no longer adds value. If you were passing 4.1.1, nothing changes. If you were failing it, that failure is no longer tracked under 2.2.

The nine new success criteria and their levels

WCAG 2.2 added criteria across Levels A, AA and AAA. For ecommerce, the critical ones are at Level AA, since that is what most legal standards reference.

2.4.11 Focus Not Obscured (Minimum) - Level AA

When a user navigates to an element via keyboard, the focused element must not be entirely hidden by sticky headers, cookie banners, chat widgets or fixed footers. This is particularly critical for checkout accessibility. It can be partially obscured, but the focused element must be at least partially visible.

This matters enormously for ecommerce. Almost every major store has a sticky header with navigation and a cart icon. When keyboard users tab through a page, those sticky headers can completely cover form fields, buttons and links. The criterion does not require that the full element is visible, just that some part of it is. But "entirely hidden" failures are common.

The companion criterion 2.4.12 Focus Not Obscured (Enhanced) at Level AAA requires the focused element to be fully visible. That is a stricter bar most stores will not aim for immediately.

2.4.13 Focus Appearance - Level AA

Focus indicators must meet minimum contrast and size requirements. The focused component's outline must have a minimum area of the perimeter of the unfocused component multiplied by 2 CSS pixels. The focus indicator must have at least a 3:1 contrast ratio against adjacent colors.

As covered in our keyboard navigation guide, many ecommerce stores style away the default browser focus ring with outline: none and replace it with nothing, or with a thin 1px border that fails contrast. This criterion formalizes what good focus indicators look like. The calculation is technical: a 100x30px button has a perimeter of 260px, so the focus indicator area must be at least 520px squared. A 2px solid outline around that button gives an area of approximately 536px squared, which passes.

2.5.7 Dragging Movements - Level AA

Any functionality that requires a drag action must also be achievable with a single pointer action (click, tap) without dragging. This covers price range sliders in product filters, image carousels, and any sortable lists.

For ecommerce, the most common failure is the price range slider in faceted search. A user who cannot perform a precise drag (due to motor impairment, tremor or assistive technology limitations) needs to be able to enter price values directly in an input field, or use increment/decrement buttons. This does not mean you cannot have sliders. It means you must provide an alternative. The same principle applies to mobile ecommerce accessibility, where touch gestures must have tap-based alternatives.

2.5.8 Target Size (Minimum) - Level AA

Interactive targets must be at least 24x24 CSS pixels, or have sufficient spacing so the total area (target plus spacing to adjacent targets) reaches 24x24. This is a lower bar than the 44x44px recommendation in WCAG 2.5.5 (Level AAA).

In practice, the spacing offset calculation is complex. A 16x16px icon button with 4px on each side of empty space technically passes because the bounding box reaches 24x24. But tightly packed icon rows, like a row of social sharing icons, frequently fail when icons are 16px with no surrounding space.

For ecommerce: quantity increment/decrement buttons, wishlist heart icons, color swatch selectors, star rating inputs and "remove from cart" buttons are all common failures.

3.2.6 Consistent Help - Level A

If a help mechanism appears on multiple pages (a chat widget, phone number, FAQ link, or contact form), it must appear in the same relative order on each page. This is a Level A criterion, making it a baseline requirement.

For ecommerce, this typically means the chat widget position, the footer help links and any persistent customer service phone numbers must be consistently placed. The criterion is about order, not position. If your chat widget is the third item in a fixed right-side toolbar across all pages, that is consistent. If it jumps around depending on the page template, that is a failure.

3.3.7 Redundant Entry - Level A

Information already entered by the user must not be requested again in the same session unless the re-entry is essential (for security verification), required by law, or the information may no longer be valid.

This criterion directly targets checkout flows. A user who enters their shipping address should not be forced to re-enter it as the billing address. The classic "same as shipping address" checkbox is the right approach. If your checkout asks for name, email and phone on step one, then asks for name again on step two, that is a failure.

Account creation flows are also affected. If a user fills out a guest checkout and you then invite them to create an account, you should pre-populate the account form with data they already provided.

3.3.8 Accessible Authentication (Minimum) - Level AA

Authentication processes must not rely on a cognitive function test unless an alternative method is provided, the test is to recognize objects (rather than remember them), or the user can use an assistive mechanism (copy-paste, password manager autofill).

The practical implication: CAPTCHAs that require deciphering distorted text fail this criterion if no alternative is provided. Image-based CAPTCHAs where users must identify objects (traffic lights, crosswalks) pass at Level AA because they test object recognition, not memory or transcription.

Password fields must support paste. Blocking paste from password managers forces users to type passwords manually, which is both less secure and a direct failure of 3.3.8. Many ecommerce login forms and checkout "create account" fields block paste as a misguided security measure. For broader form accessibility guidance, see our guide on accessible forms for ecommerce.

The Level AAA version (3.3.9 Accessible Authentication Enhanced) prohibits object recognition tests as well, requiring authentication to work entirely without cognitive function tests. That means magic links, passkeys or similar mechanisms.

3.3.9 Accessible Authentication (Enhanced) - Level AAA

As above but stricter: no cognitive function tests at all. This is AAA, so it is not required for most compliance targets. But passkey adoption (which meets this criterion by default) is growing and worth considering for customer accounts.

How WCAG 2.2 differs from 2.1 for ecommerce

WCAG 2.1 added 17 criteria to the original 2.0, focused heavily on mobile accessibility and cognitive accessibility. The additions that mattered most for ecommerce were pointer gestures (2.5.1), pointer cancellation (2.5.2) and reflow (1.4.10).

WCAG 2.2 builds on this. Where 2.1 addressed whether touch targets are usable (pointer gestures), 2.2 now sets a minimum size (2.5.8). Where 2.1 addressed whether drag interactions exist (pointer gestures), 2.2 now requires single-pointer alternatives (2.5.7). The trajectory is toward more specific, measurable requirements.

The new focus criteria (2.4.11, 2.4.13) are a direct response to the widespread practice of stripping focus indicators for aesthetic reasons. These criteria are now enforceable. Courts and regulators have something concrete to point to.

Implementation priority for ecommerce teams

Not all nine new criteria require equal effort. Here is a prioritization based on failure rate and implementation complexity.

• Highest priority, quickest fix: 3.3.7 Redundant Entry. Review your checkout flow for repeated data collection. Add "same as shipping" options. Pre-populate wherever you can. This is a logic change, not a UI rebuild.
• Highest priority, moderate effort: 3.3.8 Accessible Authentication. Enable paste on all password and confirmation fields. Audit your CAPTCHA implementation. If you use hCaptcha or reCAPTCHA v2 image challenge, verify an audio alternative exists.
• High priority, requires design review: 2.5.8 Target Size. Audit small interactive elements: quantity buttons, swatch selectors, icon-only buttons. Either increase size to 24x24px or add padding to reach the spacing threshold.
• High priority, requires CSS audit: 2.4.11 Focus Not Obscured. Test your sticky header height against the keyboard tab order. Add scroll-margin-top equal to the sticky header height on focusable elements. Test the cookie banner at its largest size.
• Medium priority, design system work: 2.4.13 Focus Appearance. Define a new focus ring style in your design system. Calculate minimum area for your most common component sizes. Aim for a 3px solid outline at full contrast as a starting point.
• Medium priority, component-specific: 2.5.7 Dragging Movements. Audit price range sliders and carousels. Add numeric input alternatives to sliders. Ensure carousels have previous/next buttons.
• Lower priority, easy to implement: 3.2.6 Consistent Help. Verify your chat widget and help links appear in consistent positions across page templates. Usually a template audit, not a code change.

What legal standards reference WCAG 2.2

As of 2026, the landscape is in transition. Here is what references what:

The EU European Accessibility Act (EAA) references EN 301 549 v3.2.1, which currently maps to WCAG 2.1 AA. ETSI is working on v4.1.1, which will map to WCAG 2.2 AA. Once that update publishes and is adopted, WCAG 2.2 becomes the EAA standard.

The US ADA does not specify a WCAG version in statute. DOJ guidance from March 2022 referenced WCAG 2.1 AA as the applicable standard for state and local governments (Title II). For Title III (private businesses), no specific version is mandated. But courts have used WCAG 2.1 as the benchmark in settlement agreements. Plaintiff attorneys are beginning to cite WCAG 2.2 in demand letters.

Section 508 (US federal) references WCAG 2.0 AA, but the Access Board has indicated an update to 2.2 is planned.

The practical answer: build to WCAG 2.2 AA now. The gap between 2.1 and 2.2 compliance is not large. The new criteria address real problems. And when legal standards catch up, you are already there.

Testing for WCAG 2.2 compliance

Automated scanners like axe-core have partial support for WCAG 2.2 criteria. As of axe-core 4.8+, the tool tests for 2.4.11 (focus not obscured) and 2.5.8 (target size) in experimental rules. These are not yet in the default ruleset but can be enabled.

Manual testing is essential for 2.5.7 (dragging), 3.2.6 (consistent help), 3.3.7 (redundant entry) and 3.3.8 (accessible authentication). These require human judgment about interaction patterns that automated tools cannot evaluate from the DOM alone.

Keyboard testing remains the fastest way to catch focus-related failures. Tab through your checkout flow from start to finish. If any focused element is invisible or covered by a sticky header, you have a failure. No tool required.

Frequently asked questions

What is new in WCAG 2.2 for ecommerce?

WCAG 2.2 adds nine new success criteria at Levels A, AA and AAA. The most impactful for ecommerce are 2.4.11 Focus Appearance (AA), 2.5.8 Target Size Minimum (AA), 3.2.6 Consistent Help (A) and 3.3.7 Redundant Entry (A).

Is WCAG 2.2 legally required for ecommerce stores?

US courts still reference WCAG 2.1 AA as the ADA standard. The EU EAA references EN 301 549, which maps to WCAG 2.1 AA. WCAG 2.2 is not yet a legal requirement but will likely become the reference standard as regulations update.

What is the WCAG 2.2 minimum target size requirement?

WCAG 2.2 criterion 2.5.8 (Level AA) requires interactive targets to be at least 24x24 CSS pixels, or have sufficient spacing so a 24px circle centered on the target does not intersect another target.