Success criterion 3.2.2
3.2.2 On Input
When forms become unpredictable.
1. What is the goal of this criterion?
A select menu works like a magic trick: you pick an option and suddenly you’re on a completely different page. Or a form vanishes the moment you click the first radio button. Surprise jumps like these are frustrating – especially for people who find it harder to orient themselves or don’t notice changes right away.
That’s why WCAG Success Criterion 3.2.2 aims to make input fields and controls respond predictably. Nobody should be catapulted into a new context just because they filled in a form field or made a selection.
In short: what happens when I type or select something should be expected – or announced beforehand.
2. What exactly does it require?
This is a Level A criterion and applies to every user interface component whose setting you can change – text fields, select menus, checkboxes, radio buttons, sliders and the like.
No automatic changes of context without prior notice:
- A select menu must not automatically redirect to a new page as soon as a value is chosen
- A form must not submit itself automatically when the last field is filled in
- Radio buttons or checkboxes must not open new windows without warning
Exception – advance notice: if an input does trigger a change of context automatically, users must be told about it before they use the control.
What counts as a change of context?
- Moving to a different page or website
- Opening a new window or tab
- Moving focus to another element or another part of the page
- A major change to the content that changes the meaning of the page
What doesn’t count as a change of context:
- Expanding and collapsing menus or sections
- Dynamically showing additional form fields on the same page – ideally right after the control that triggered them
- Updating content without moving focus or changing the page
3. Why does it matter for accessibility?
Imagine you’re using a screen reader and select “Germany” from a dropdown – and suddenly land on the German version of the website without noticing. Or you’re using a screen magnifier and the form jumps to an area you can’t currently see.
Predictable input behaviour supports accessibility because it:
- gives blind and visually impaired people orientation when they can’t visually pick up on a change of context right away
- helps people with cognitive disabilities who can be confused by unexpected changes
- protects people with motor impairments from the consequences of accidental selections
- supports people with attention disorders in keeping track of where they are
- gives everyone a reliable, intuitive experience
Predictability is a cornerstone of accessibility – especially for people who rely on assistive technologies.
4. How to meet the criterion
The good news: standard form controls behave predictably out of the box. Problems usually only appear once extra JavaScript is added. Here are the key tips:
Ground rules for form controls:
- Use submit buttons to send forms – no automatic submission
- Select menus are for choosing, not for navigating; use links or a “Go” button for page changes
- Announce unusual behaviour in advance, visibly and before the control: “Selecting an option takes you to the next page automatically.”
- For more complex interactions, short instructions help – see also Labels or Instructions
Do:
- Use clear action buttons: “Search”, “Submit”, “Next”
- Inform in advance: “More fields will appear after you make a selection.”
- Set expectations: “Click ‘Save’ to continue.”
- Reveal step by step: show additional content gradually without moving focus
Don’t:
- Auto-submit: don’t send forms on their own when the last field is filled
- Auto-navigate: a selection shouldn’t take people to new pages
- Unannounced pop-ups: don’t open windows without warning
- Hijack focus: don’t move focus without preparing people for it
Technical implementation:
- JavaScript: use
changeandinputevents to expand or filter content, not to change pages - HTML: use
<button type="submit">to submit forms - Hints: place explanations as visible text before the control and additionally connect them with
aria-describedby - CSS: make interactive elements clearly recognisable
If you want to go further, take a look at Change on Request. The counterpart for focus is On Focus.
5. Why this criterion matters for businesses
Predictable interaction design isn’t just an accessibility issue – it’s a real competitive advantage for your business.
1. Fewer drop-offs
People who feel confident and oriented are less likely to abandon a process. Predictable forms and inputs reduce frustration and make it more likely that sign-ups and purchases actually get completed.
2. Better usability
Nobody likes surprises while filling in a form. Clear, expected interactions improve the experience for everyone – from tech-savvy people to less experienced internet users.
3. Fewer support requests
When people understand what happens when they select something, confused support requests go down. “Why am I suddenly on a different page?” or “The form just disappeared” become much rarer.
And then there’s the legal side: since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to many consumer-facing digital services, such as online shops and banking services. Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). The technical benchmark is the harmonised standard EN 301 549, which refers to WCAG 2.1 Level AA for web content – and 3.2.2 is part of that. Public sector bodies are covered separately by the Web Accessibility Directive (EU) 2016/2102. This section is general information, not legal advice.
6. The success criterion in the W3C’s words
Success Criterion 3.2.2 On Input (Level A)
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.
In short: changing a setting on a control must not automatically drop you into a new context – unless you were told about it beforehand.
Official explanation from the W3C
The W3C explains every success criterion in depth – with intent, examples and techniques.
Understanding 3.2.2 (opens in a new tab)