Skip to main content
Il tuo browser è troppo vecchio per visualizzare correttamente questo sito. Aggiorna all'ultima versione di Chrome, Edge, Firefox o Safari.
Back to WCAG Database
Level AWCAG 2.0

3.2.2 On Input

Changing the setting of any user interface component does not automatically cause a change of context, unless the user is advised of the behavior before using the component.

Last reviewed: September 9, 2026

Understanding 3.2.2

This criterion protects users, especially those with cognitive or visual disabilities, from unexpected behavior triggered simply by interacting with a form control. If selecting an option in a dropdown or checking a box silently navigates away or submits a form, users can become confused or trigger actions they did not intend, particularly since they may not be able to see the whole page and notice the change happening.

How to Meet It

Avoid auto-submitting forms or navigating away purely from a control's onchange event without warning. If an immediate change is genuinely needed, either require an explicit follow-up action (a visible submit button) or clearly tell the user in advance, in text, that interacting with the control will cause an immediate change (for example, "Selecting a language will reload the page").

Code Examples

INCORRECT
<select onchange="location = this.value;">
  <option value="/en">English</option>
  <option value="/fr">French</option>
</select>
<!-- Automatically navigates on selection with no warning -->
CORRECT
<label for="lang">Language</label>
<select id="lang">
  <option value="/en">English</option>
  <option value="/fr">French</option>
</select>
<button type="submit">Change language</button>
<!-- Change of context only happens after explicit submission -->

Frequently Asked Questions

Does a live search-as-you-type field that updates results violate this criterion?

Generally no. Filtering or updating a results list in place, without moving focus or navigating away, is not a change of context. This criterion is about navigation, new windows, or form submission being triggered unexpectedly by input, not in-place content updates.

Related Success Criteria

3.2.1 On Focus3.2.3 Consistent Navigation3.2.4 Consistent Identification3.2.5 Change on Request

Quick Facts

  • Criterion3.2.2
  • LevelA
  • IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 3.2.2 issues in your codebase.

Try Scanner Free