Web users have certain expectations about what will happen when they tab onto a button, click in a form field, or select an item from a combo box. These behaviors are historically one step in a process where the user first gives focus to an element and then takes action. When interfaces behave unpredictably – changing context automatically on focus or input – it can be disorienting, especially for users of assistive technology. Predictable behavior is essential for all users, especially those with cognitive disabilities or using screen readers.
Why this matters
Predictable behavior helps all users understand what will happen when they interact with a page. Unexpected changes in context—such as automatic form submission, opening new windows, or redirecting to different pages—confuse users and can be particularly disorienting for those using screen readers who may not immediately notice visual changes. Users with cognitive disabilities depend on consistent, predictable patterns to navigate confidently. When a website behaves in unexpected ways, it creates friction that may prevent users from completing tasks or accessing content.
Key Principles
Two key principles guide accessible web design:
- No unexpected change of context on focus
- No unexpected change of context on input
Users should always be in control of when context changes occur.
Avoid Changes on Focus
Do not trigger changes in context when an element receives focus. Examples of problematic changes on focus include:
- Opening a new window
- Moving focus to a different component
- Going to a new page
- Significantly rearranging page content
A change should happen only at the user’s explicit request.
Avoid Changes on Input
Do not trigger changes in context when a user changes a form input value. Examples of problematic changes on input include:
- Auto-submitting a form when a radio button is selected
- Navigating to a new page when a dropdown selection changes
- Changing other form fields unexpectedly based on input
If a change is needed on input, inform users in advance what will happen.
Consistent Navigation
Navigation mechanisms that appear on multiple pages should be in the same relative order each time. Users who rely on spatial memory or screen reader navigation patterns depend on consistency.
Consistent Identification
Components with the same functionality should be identified consistently across pages. For example, a search function should be labeled Search consistently, not Search on one page and Find on another.
Providing Advance Notice
If an action will trigger a change of context, inform users beforehand. Use submit buttons rather than auto-submit, and describe what will happen before the user takes action. For example: Selecting a category will reload the page with filtered results.
Common Mistakes to Avoid
- Auto-submitting forms on input change: When selecting a radio button or dropdown option automatically submits a form, users cannot review or correct their selection before submission.
- Opening new windows without warning: Links that open in new windows or tabs without warning disorient users, especially those using screen readers who may not notice the change.
- Changing context on focus: Moving focus to a different element or navigating to a new page when an element receives focus is confusing and violates WCAG requirements.
- Inconsistent component behavior: If a dropdown on one page submits a form but on another page it doesn’t, users become confused about what to expect.
- Automatic redirects without user control: Redirecting users to a different page automatically prevents them from choosing their own destination and breaks browser back button expectations.
- Select menus that navigate on change: Select menus that change location or content without a submit button violate predictability requirements and surprise users.
WCAG 2.1 Success Criteria
- 3.2.1 On Focus (Level A) – No change of context when any UI component receives focus
- 3.2.2 On Input (Level A) – No change of context when user changes setting of any UI component unless user has been advised beforehand
- 3.2.3 Consistent Navigation (Level AA) – Navigation mechanisms repeated across pages occur in the same relative order
- 3.2.4 Consistent Identification (Level AA) – Components with the same functionality identified consistently
Getting help
If you have questions or need assistance, the Digital Accessibility Services Hub (DASH) is available to support colleges, schools, and administrative units as they build sustainable accessibility practices.
- Contact DASH at [email protected] for consultations, training, or technical assistance.
- Visit the DASH training page for resources and learning opportunities.
Accessibility is a shared responsibility, and every step you take makes UGA’s digital environment more inclusive.