SC 3.2.2: On Input

SC 3.2.2 On Input
Ensure that changing the setting of a user interface component does not cause an unexpected change of context.

• Predictability: Input interactions (entering text, selecting checkboxes/radio buttons, choosing from lists) must not trigger automatic actions like page reloads, new window launches, or focus shifts.
• Exceptions: Context changes are permissible only if the user is explicitly advised of this behavior before they interact with the component (e.g., clear instructions stating, “Selecting this option will automatically submit the form”).
• Best Practice: Use dedicated control buttons (e.g., “Submit,” “Search Now”) to initiate actions, giving users control over when a change of context occurs.
• Scope: Focuses on form fields and similar input components; does not apply to non-context-shifting content changes like opening an expandable menu.

3.2.2 On Input: 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.

SC 3.2.1 On Focus is similar to this SC. The difference is that SC 3.2.1 On Focus requires that a user’s context must not change when an element receives focus (such as when a keyboard user navigates to a form field using the TAB key); SC 3.2.2 On Input requires that a user’s context must not change when an element receives input (such as entering text into a form field)

For this SC, user interface components generally refer to form field elements, such as text input fields, selection lists, radio buttons, and checkboxes. When a user interacts with a form element and changes a setting, such as selecting a checkbox/radio button or inputting text into a form field, it should not cause an automatic change of context unless the user has prior warning.

A change of context is a significant change in page content such that a user may become confused because the Web page meaning has been altered or because the user’s focus has been moved to an unexpected location. Examples of changes in context as a result of an On Input event could include:

• Forms submitted automatically after completing the last text input field in a form.
• New windows launched when checking a checkbox or changing a radio button selection.
• Focus moved to another component of the page when the user a selects an option in a list control or combo box.

If a change in context is going to occur automatically upon interaction with an element, the application must provide advanced notice of that change. One way to meet this SC is for the application to provide an onscreen explanation of what will happen when controls are modified.

For example, a feedback form displays one question at a time. At the beginning of the form, the application includes the following text: “Please read the question and select the best answer. When a checkbox is selected, you will be taken to the next question.”

An alternative is that the application could provide a clearly labeled button for the user to initiate a change in context. This provides the user an option to confirm the action and activate the change in context. For example, the application could include:

• A Subscribe button to sign up for company email. The button must be activated after inputting the user email address.
• A Submit button to submit a form.
• A text input field has a Search Now button. To perform the search action, a user must press the Search Now button.

It is important to note that changes of content are not always the same as changes of context. This SC applies if there is a change in context, as unexpected changes can confuse a reader. Content may be changed and still make sense, such as an expandable menu appearing after selecting the More button. This would not be considered a change in context; the content changed in a logical sequence as the user interacted with the Web page.

Impact of Nonconformance with SC 3.2.2 On Input

Applicability of Success Criteria 3.2.2 On Input