This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung

Accessibility

What is an unexpected context change on input?

An unexpected context change on input occurs when the page changes already while typing or selecting — without the visitor having pressed "Submit". The classic example: a "Select country" dropdown loads a new page the moment something is selected. Anyone who mistypes or arrows through the list gets swept away mid-input. WCAG criterion 3.2.2 requires an explicit confirmation step.

What the criterion means for visitors in practice

Forms depend on the ability to reconsider and correct entries. Anyone operating a dropdown list with the keyboard goes through the entries one by one with the arrow keys — each entry is briefly selected in the process. If the page already reloads on this selection, a keyboard user only ever reaches the very first entry; every other country, branch, or category stays out of reach for them. People who type slowly or use voice control also lose their half-filled forms with such instant changes. The solution is simple and familiar: a separate button such as "Next" or "Apply" that the visitor deliberately activates once their input is complete.

How the audit service measures behaviour on input

The audit service runs a cautious input test in a real browser: it selects a text field on your page, types a character into it, and observes what happens. If the input triggers a real navigation — the page reloads without anything having been submitted — the criterion counts as violated. If the page stays calm, the test counts as passed. The measurement deliberately doesn't try out dropdown lists: an automatic selection could trigger orders or redirects on a live website. The report openly notes such cases for manual review, and at the Gold Standard level a human judges the behaviour of every dropdown list. A live search that rebuilds the results list while typing is also assessed by a human.

Examples

Selection sends immediately

Not met

<select name="land" onchange="this.form.submit()">…</select>

Passes

<select name="land">…</select>
<button type="submit">Anzeigen</button>

Who goes through the list with the arrow keys, triggers a send at every step. A button separates choice and effect.

Go through every dropdown list on your website with the arrow keys and check whether the page stays put.
Give every filter and country selector its own button such as "Apply", instead of letting the selection take effect immediately.
Type a character into every search field and watch whether the page stays calm.
Ask your agency to replace automatic redirects on form changes with confirmation steps as a general rule.

Deutsche Fassung dieser Seite

FAQ

May a dropdown list load a new page immediately?

An instant change on selection violates WCAG criterion 3.2.2 if the visitor gets no warning beforehand. Keyboard users arrow through dropdown lists and briefly select each entry along the way — they'd be swept away on the very first one. The accessible solution is a separate confirmation button such as "Next" or "Apply" next to the list.

Is a live search with instant results allowed?

A live search that, while typing, only updates the results list below the field is generally acceptable — the visitor stays on the same page and keeps their input field. A violation occurs if typing loads an entirely new page or pulls focus out of the field. Whether a specific live search stays reasonable is judged by a human at the Gold Standard level.

How does the audit service check the On Input criterion automatically?

The measurement engine types a character into a text field on your page in a real browser and observes the reaction. If the input triggers a real navigation, the report flags a violation. The measurement deliberately never triggers dropdown lists, because that could have consequences on a live website — these cases are openly noted for manual review.