3.2.2 On Input

What does it mean?

Selecting an option in a drop-down, ticking a checkbox or typing in a field should not by itself load a new page, submit a form or move focus. Users must be able to change the value and then decide what happens next.

Such a change is allowed if the page clearly explains it before the user interacts, for example "Choosing a country will reload the page". Updating content nearby, such as showing extra fields, is not a change of context.

Who does it help?

• Keyboard users, who move through drop-down options with the arrow keys and trigger every option along the way
• Screen reader users, who may not notice that the page has changed
• People with motor or cognitive disabilities who need time to choose

Common failures

• A language or country drop-down jumps to another page as soon as the value changes
• A form is submitted automatically when a radio button is selected
• Typing the last digit of a code moves the user to the next page without warning

How we test it

• people only Manual only: nothing useful can be measured. The reviewer tests it directly.

Test question: Changing a setting (select, checkbox) does not change context unless announced beforehand.

A person decides every criterion. No criterion ever passes automatically.

How to fix it

<select onchange="location.href=this.value">
  <option value="/en/">English</option>
  <option value="/de/">Deutsch</option>
</select>

<form action="/language">
  <label for="lang">Language</label>
  <select id="lang" name="lang">
    <option value="en">English</option>
    <option value="de" lang="de">Deutsch</option>
  </select>
  <button type="submit">Change language</button>
</form>

The user selects a value first and confirms with a button, so nothing happens by surprise.

Practical tips

• Filters that update a result list without reloading are fine; announce the new count as a status message (4.1.3).

Official source

Understanding WCAG 2.2 at the W3C: 3.2.2 On Input