In this WCAG Fix It guide, we’re looking at a common usability issue: unexpected changes that occur when a user enters information into a field.
When users interact with form controls, they expect the page to remain stable, but sometimes websites trigger automatic actions such as submitting a form, redirecting to a new page, or changing content unexpectedly. When that happens without warning, users can quickly lose context and control.
What Is WCAG 3.2.2?
WCAG 3.2.2 – On Input requires that changing the setting of any user interface component does not automatically cause a change of context unless the user has been informed beforehand.
In simple terms, when you are entering data or selecting an option, the page should not change unexpectedly.
A change of context includes:
- Navigating to a new page
- Submitting a form automatically
- Opening a new window or modal
- Rearranging large sections of content
If a change of context will occur, the user must be clearly informed before the action happens.
What Is a Change of Context?
A change of context refers to a major change in how the page behaves or what content is presented.
Examples include:
- Redirecting to a different page
- Automatically submitting a form
- Opening a new window
- Loading new content that shifts the page structure
Small changes, such as displaying validation feedback, are usually acceptable, but actions that interrupt the user’s workflow can be disorienting if they happen unexpectedly.
The Human Impact of Unexpected Page Changes
Imagine filling out a form and selecting a dropdown option.
Suddenly, the page refreshes and you lose your place in the form or imagine selecting an option in a settings menu and being redirected immediately to another page without warning.
For users who rely on screen readers or keyboard navigation, unexpected changes can be confusing and disorienting.
They may not understand:
- Why the page changed
- Where they are now
- How to return to where they were
Predictable behaviour is essential for accessible interfaces.
Common WCAG 3.2.2 Failures
Here’s what we typically see when scanning websites:
- Dropdown menus that automatically redirect to another page
- Forms that submit automatically when a field changes
- Filters that refresh the page immediately when selected
- Controls that open new windows without warning
- Content updates that shift the page unexpectedly
All of these can fail WCAG 3.2.2 if users are not warned beforehand.
How to Fix Unexpected Input Behaviour
Avoid Automatic Page Changes
User input should not trigger major actions automatically.
Bad example:
Selecting a dropdown option immediately redirects the user to another page.
Better approach:
Allow users to select their option and then click a Submit or Apply button.
Example:
<select id=”region”>
<option>Select a region</option>
<option>Europe</option>
<option>North America</option>
</select>
<button>Apply</button>
This gives users control over when the action occurs.
Inform Users Before a Change Happens
If a change of context is necessary, inform users clearly.
Example:
“Selecting a region will load a new page.”
Providing this information helps users understand what will happen next.
Avoid Auto-Submitting Forms
Forms should generally submit only when users press a button such as:
- Submit
- Continue
- Apply
Auto-submission can interrupt workflows and cause confusion. Giving users explicit control improves accessibility and usability.
If You’re Using a CMS or Website Builder
Unexpected input behaviour often occurs when:
- Dropdown navigation menus automatically redirect
- Filter controls auto-refresh pages
- Plugins trigger automatic form submissions
- Scripts dynamically reload content
To fix:
- Add a submit or apply button
- Warn users when a change of context will occur
- Test forms using keyboard navigation
- Review plugin behaviour
Predictable interaction should always be the goal.
How to Test WCAG 3.2.2
After making changes:
Interact with the page using forms and controls.
Ask:
- Does selecting an option trigger a page change?
- Does entering information cause a redirect?
- Are users warned before a change occurs?
Users should always understand what will happen before it happens. After updates, re-run your accessibility scan to confirm the issue is resolved.
Why WCAG 3.2.2 Matters Beyond Compliance
Predictable input behaviour:
- Reduces user confusion
- Improves form usability
- Supports screen reader users
- Improves keyboard navigation
- Prevents accidental page changes
- Reduces legal risk
Users should always feel in control of their interactions. Unexpected behaviour creates frustration and disorientation. Predictable interfaces create better experiences for everyone.
WCAG 3.2.2 Quick Fix Checklist
Input fields do not trigger unexpected page changes
Dropdowns do not auto-redirect without warning
Forms do not auto-submit on input
Users are informed before a change of context occurs
Controls provide clear submit or apply buttons
Interactions tested using keyboard navigation
Issues re-tested after updates
WCAG 3.2.2 On Input Frequently Asked Questions
What is WCAG 3.2.2 On Input?
WCAG 3.2.2 requires that changing the value of a form control does not automatically cause unexpected changes to the page unless the user has been informed beforehand.
What counts as a change of context?
Changes such as navigating to a new page, submitting a form automatically, or opening a new window are considered changes of context.
Are dropdown navigation menus allowed?
Yes, but users should be informed that selecting an option will navigate to another page.
Why is predictable behaviour important?
Predictable interfaces help users maintain orientation and control, especially when using assistive technologies.