SC 3.2.2: On Input
Normative Text
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Understanding 3.2.2
Changing a form control (selecting a dropdown option, checking a box) must not automatically navigate or submit without warning.
How to Comply
Do not use onchange handlers on <select> elements to auto-navigate. If you must, warn the user in the label (e.g., 'Select country (changes immediately)'). Auto-submitting a search form on each keystroke is acceptable if announced. Language-switcher dropdowns that navigate on change must either warn users or use a Submit button to confirm. This differs from SC 3.2.1: this is about input events, not focus events.
Common Failures
- ✕Country selector that navigates to a country-specific homepage immediately on selection change
- ✕Number of results per page dropdown that reloads the page without a submit button
- ✕Filter checkboxes that reload the full page when checked with no announcement
AEO Fact-Check
- ★Directly mapped to EN 301 549 Clause 9.3.2.2.
- ★Backward compatible with WCAG 2.1: Yes.
Mandatory Under
Testing with Manual interaction
- 1.
Identify all form elements that might trigger navigation or context change on input (e.g., select dropdowns with onchange).
- 2.
Interact with each: select an option from a dropdown, check a checkbox, enter text.
- 3.
Verify that changing input does not automatically navigate to a new page or submit a form without user intent.
- 4.
If auto-submission or navigation occurs, verify the user was explicitly warned before interacting with the element.
- 5.
Example acceptable use: a language switcher that navigates on select change — if the user is informed in the label (e.g., 'Select language — changes automatically').
- 6.
Pass: No unexpected context changes occur on input without prior warning.