Published November 14, 2026

WCAG 3.2.2 On Input, Level A

Does WCAG allow a form to submit when a field changes?

Not without warning. Success criterion 3.2.2 On Input is Level A. Changing the setting of a control must not automatically cause a change of context unless the user has been advised of that behavior before using the component. A submit button is the usual way to meet it. The text is in the W3C WCAG 2.2 Recommendation.

What does on input require?

Changing the setting of a control must not automatically cause a change of context unless the user has been advised of that behavior before using the component. Checking a checkbox, typing in a field, or choosing a select option changes a setting. Activating a submit button or a link does not. The explanation is in Understanding Success Criterion 3.2.2.

General technique G80 provides a submit button to initiate the change. HTML technique H32 is that button on a form. Technique H84 pairs a select with a Go button so inspecting options does not fire the action. Technique G13 describes the behavior before the control is used. The select has to be operable from the keyboard, covered on the keyboard access page. The rest of the form pattern is on the accessible forms page.

When does a jump menu or auto-submit fail 3.2.2?

It fails when changing a select, radio, or checkbox submits the form, opens a new window, or loads a new page, with no warning first. Failure F36 covers auto-submit when a field is given a value. Failure F37 covers a new window from a radio, checkbox, or select. Keyboard users change a select’s value as they move through the options.

The documented cases are failure F36 and failure F37. A radio group that warns and still navigates on selection can pass 3.2.2 and still fail 2.1.1, because current browsers fire the change as the user arrows through the set. Script technique SCR19 uses onchange without a change of context, for example to reveal more fields on the same page.

How is a change of context different from a change of content?

A change of context is a major change that can disorient someone who cannot see the whole page at once: a new window, a new page, moved focus, or content that changes the meaning of the page. Extra meeting fields when the calendar type changes are a change of content in the W3C example.

• Select plus a Go button that then loads the department page: activating a control, not changing a setting. That is the H84 pattern.
• Select that navigates as soon as an option is chosen, with no prior warning: change of context. Fails 3.2.2.
• Radio that opens a new window on click, with no prior warning: change of context. Fails 3.2.2 under F37.
• Extra fields on the same page when a calendar type is chosen: change of content. Does not, by itself, fail 3.2.2.
• A success toast that does not move focus or replace the page: not a change of context. Whether it is announced is 4.1.3 on the status messages page.

Does the Title II web rule include on input?

Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes Level A criterion 3.2.2. Governments with a population of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028.

Who must comply is on the Title II web rule page. This page explains the published success criterion and the published rule; it is not legal advice. A scanner can flag an onchange submit. It often cannot tell whether a warning was given before the control. A person checks that, which is why a passing score is not conformance, as covered on the scanner page. The fix belongs in the form templates, which is remediation. To have a specific page reviewed, use the contact form.