WCAG 3.2.2: On Input
Success Criterion 3.2.2 — Level A
Quick Answer
Changing the value of a UI component must not automatically trigger a context change.
Why It Matters
Select dropdowns that auto-navigate when changed are inaccessible to keyboard and screen reader users.
How to Audit
Run an automated accessibility scan to detect common On Input failures. Then manually verify with: keyboard-only navigation, a screen reader (VoiceOver on Mac, NVDA on Windows), and browser developer tools. Automated tools catch approximately 40% of On Input issues — manual testing is essential.
How to Fix
Add an explicit 'Go' button for any navigation triggered by input. Don't auto-submit on change.
Frequently Asked Questions
What is WCAG 3.2.2 On Input?
Changing the value of a UI component must not automatically trigger a context change.
Is WCAG 3.2.2 required for ADA compliance?
WCAG 2.1 Level A is the minimum baseline for ADA website compliance. Courts have upheld WCAG 2.1 AA as the standard for ADA Title III lawsuits.
How do I fix WCAG 3.2.2 violations?
Add an explicit 'Go' button for any navigation triggered by input. Don't auto-submit on change.
Scan Your Site for WCAG 3.2.2 Issues
Get a free automated accessibility report including all WCAG 2.1 AA violations.
Run Free Accessibility Scan