On Input makes sure that anytime a user’s input changes their context, like jumping to a new page or displaying a pop-up, it only happens after they confirm their choice – keeping control firmly in their hands.
Who this impacts
- Screen reader and keyboard-only users: Unexpected changes disrupt navigation and make it harder to keep track of location on the page.
- People with cognitive impairments: Predictable actions reduce confusion and help users feel more in control.
- Everyone: Preventing unintentional context changes improves usability for all by reducing frustration and confusion.
How to meet On Input
- Require user confirmation for context changes: Don’t initiate page loads or pop-ups without an action like clicking “Submit” or “Next.”
- Avoid automatic changes on input: Don’t trigger page reloads or new content just because a user selects an option in a dropdown or form field.
- Give users control: Let users decide when to proceed, giving them control over when new pages or pop-ups appear.
Practical example
Catbook’s “Favorite Treat Flavor” dropdown lets users pick “Tuna,” “Chicken,” or “Salmon” without jumping to another page. Any updates to their profile are made only after clicking “Save Changes,” ensuring users stay in control.
Exceptions
This requirement doesn’t apply to controls where users clearly expect immediate changes, such as a real-time search or filter function.
Top tips
- Use confirmation buttons: Let users confirm actions before triggering major context changes, reducing navigation disruptions.
- Focus on user-driven navigation: Make sure changes only happen after an intentional user action.
- Test for predictable interactions: Make sure users can go through forms and options without being surprised by changes.