WCAG 3.2.2 On Input

Success criterion 3.2.2 protects people from unexpected jumps while they fill in a form. Screen reader users, keyboard users and people with cognitive disabilities may explore a select list option by option or tick a box to see what it does. If that alone reloads the page or submits the form, they lose their place or send something they did not mean to. It is level A and appears in EN 301 549 as clause 9.3.2.2.

What the criterion requires

Changing the setting of any user interface component must not automatically cause a change of context, unless the user has been advised of the behaviour before using the component.

"Changing the setting" means changing a value: typing in a field, ticking a checkbox, choosing a radio button or an option in a select. A change of context is a new page, a new window, focus moving elsewhere, or content changing the meaning of the page. A plain change of content — showing an extra field, updating a price — is allowed.

Typical failures on an online shop

• a "Sort by" or currency select reloads the page as soon as an option is chosen, with no warning;
• a country select in checkout moves focus or reloads the whole form;
• choosing a variant (size, colour) navigates to a different product URL;
• a coupon or quantity field submits the form automatically when the value changes;
• ticking a checkbox opens a new window, such as the terms page.

How to check it

Automated: our checker has no rule for this criterion. Whether a change of value triggers navigation depends on scripts, so it needs a manual check.

By hand: with the keyboard only, go to each select, checkbox, radio group and text field. Change the value with the arrow keys or by typing, without pressing Enter or a button. Watch for page reloads, new windows or tabs, form submission, or focus moving away. If it happens, look for text before the control that warns about it.

How to fix it

• Add an "Apply", "Go" or "Update" button and act only when it is pressed.
• If the instant behaviour must stay, say so before the control, for example "Choosing a currency reloads the page".
• Update content in place (price, stock, filter results) without moving focus, and announce the change as a status message.
• Never open new windows from checkboxes or radio buttons.

Related criteria

• 3.2.1 On Focus — focus alone must not change the context.
• 4.1.3 Status Messages — announce updated results without moving focus.
• 3.3.2 Labels or Instructions — instructions that warn about behaviour.

Frequently asked questions

Can a select menu navigate on change?

Only if users are told before they use it, for example with text explaining that choosing an option opens the page. The more usable solution is a separate "Go" or "Apply" button.

Are filters that update the product list on change allowed?

Updating the list is usually a change of content, not of context, and is allowed. Loading a new page, opening a window or moving focus on change is a change of context.

Does 3.2.2 cover buttons and links?

No. Activating a button or link is not changing a setting. 3.2.2 is about changing the value of controls such as text fields, checkboxes, radio buttons and select lists.