WCAG 3.2.2 — On Input — Context Changes Unexpectedly on Input

Who Is Affected

Screen reader users, users with cognitive disabilities, users with motor disabilities who may accidentally trigger controls, and users with attention disorders who become disoriented by unexpected changes.

What This Means

When users interact with form controls like dropdowns, radio buttons, or checkboxes, the page should not automatically submit forms, navigate to new pages, or drastically change the interface without explicit user action (like clicking a submit button).

Common violations include:

• Dropdown menus that automatically navigate to new pages when an option is selected
• Forms that auto-submit when the last field is filled
• Radio buttons that immediately change major page content
• File upload fields that start processing files without a submit button

Users need predictable behavior. They should be able to explore form options, correct mistakes, and consciously choose when to submit or navigate.

Fix: CMS / Theme

Many auto-submit behaviors are built into themes or CMS plugins. Look for these common patterns:

Search and Filter Forms

1. Locate dropdown filters or search forms that auto-submit on selection.
2. Remove onchange="this.form.submit()" or similar JavaScript from form elements.
3. Add a "Search" or "Filter" button to let users explicitly submit.
4. In WordPress, check if plugins like WooCommerce or search filters have "auto-submit" settings that can be disabled.
5. In Joomla, review module configurations for search or filtering components.

Navigation Menus

1. Find dropdown menus that auto-navigate when options are selected.
2. Replace onchange="location.href=this.value" with a button-triggered function.
3. Add a "Go" button next to the dropdown.

Language/Location Selectors

1. Review language switchers or location selectors that immediately redirect.
2. Add a submit button or make the selection a two-step process.

Fix: Content Editor

For forms created through your content editor:

1. Identify auto-submitting elements: Look for forms that change or submit without clicking a button.
2. Add explicit submit controls: Insert "Submit," "Go," or "Apply" buttons for all form actions.
3. Test interaction patterns: Tab through form controls to ensure nothing triggers unexpectedly.
4. Provide clear instructions: Tell users what will happen before they interact with controls.

WordPress Gutenberg Blocks

• Review any custom form blocks or third-party form plugins
• Disable auto-submit features in contact form plugins like Contact Form 7 or Gravity Forms
• Add submit buttons to all interactive elements

Joomla Content

• Check any forms created with RSForm or BreezingForms for auto-submit settings
• Review menu item configurations that might auto-redirect on selection

Standard Reference

WCAG 2.1 Success Criterion 3.2.2 — On Input, Level A

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.

• W3C Understanding SC 3.2.2
• WCAG Technique G80 — Submit button for context changes
• WCAG Technique G13 — Describe automatic context changes
• WCAG Failure F36 — Auto-submitting forms
• WCAG Failure F37 — Auto-redirecting on selection