On Input
Changing the value of a UI component must not automatically cause a change of context unless the user has been advised of the behavior in advance.
What it requires
WCAG 2.0 SC 3.2.2 is the input-event sibling of 3.2.1. When a user types in a field or selects an option, the page must not auto-submit, navigate, or open a popup unless the behavior is clearly documented in advance — and even then, an explicit submit button is the safer pattern.
Common failure: a dropdown that auto-navigates to a new page on selection. The user expected "I am picking an option"; the page interprets it as "submit now". Keyboard and screen-reader users are particularly affected because they often dwell on options before committing.
Common Shopify failure
Currency selector that uses `onchange="window.location = ..."` to auto-navigate when a customer changes the currency. Sort-order dropdown on a collection page that re-sorts the URL on change without giving the user a chance to confirm.
How to fix it
AccessComply rewrites auto-navigating dropdowns to require an explicit "Apply" button. Where the merchant prefers to keep auto-navigation, the agent adds an `aria-describedby` warning so screen-reader users hear the behavior in advance.
Primary source: W3C — WCAG 2.0 Understanding 3.2.2