Understanding SC 3.2.2 on Input

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. (Level A)

This success criterion conveys that change of context should not occur while user is trying to input data. For example, if the user is filling a form & if the page refreshes while selecting an option in <select> element or if the form submits after the user fills in the last form field, it fails this checkpoint. User should be provided with an option to submit the form by providing a submit button or hint/instruction should be provided for all users informing that form will submit once the form fields are filled

Exceptions

There are some exceptions to this success criterion. Change of content is not change of context. For example if a radio button is selected & if it triggers more form controls it is not change of context. Here content is updating. Activating links, buttons or tab controls doesn’t fall into on input category. Here is user is taking deliberate action to trigger these form controls…

Points to Remember

• Make sure that forms don’t submit on input of data.
• Make sure that focus doesn’t move to next form control once a form field is populated with data.
• Provide a submit button for all forms.
• Make sure that control of how data is populated is in the hands of your users.
• If there is a change of context, then provide an instruction that is available for all user groups.

References

Understanding Success Criterion 3.2.2