WCAG 3.2.2: On Input
Level AQuick answer: Changing a field value should not trigger an unexpected context change unless users were warned first.
What This Means
On ecommerce sites, On Input usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like selecting a country in checkout immediately submits the form and resets fields. or choosing a size variant instantly adds the product to cart., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Selecting a country in checkout immediately submits the form and resets fields.
- Choosing a size variant instantly adds the product to cart.
- Newsletter dropdowns redirect users to a different site on selection.
- Changing sort order reloads the page without preserving focus or announcing it.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Use an explicit button for navigation or submission after input changes.
- Warn users before a field change will trigger a significant update.
- Preserve focus and state when updates are expected, like sorting results.
- Check product configurators and shipping calculators for surprise submissions.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
countrySelect.addEventListener('change', form.submit);
<!-- After -->
<button type="submit">Update shipping country</button>FAQ
What is WCAG 3.2.2?
Changing a field value should not trigger an unexpected context change unless users were warned first.
How does WCAG 3.2.2 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with selecting a country in checkout immediately submits the form and resets fields. and choosing a size variant instantly adds the product to cart. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.2.2 violations?
Start by auditing the live storefront, then Use an explicit button for navigation or submission after input changes.; Warn users before a field change will trigger a significant update.; Preserve focus and state when updates are expected, like sorting results.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.2.2 → Free ADA Compliance Scan