Predictable
Summary:
WCAG 3.2, "Predictable," aims to make web interfaces more consistent and predictable in their operation. This principle is crucial for users with cognitive disabilities, vision impairments, and for those who rely on assistive technologies.
What:
This criterion focuses on ensuring that web pages operate in predictable ways. This includes consistent navigation elements across pages and predictable behavior when user interface components are activated.
- 3.2.1 On Focus: Any component that can be focused by a user should not initiate a change of context.
- 3.2.2 On Input: Changing the setting of any user interface component should not automatically cause a change of context unless the user has been informed.
- 3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple pages within a set of web pages should occur in the same relative order.
- 3.2.4 Consistent Identification: Components that have the same functionality within a set of web pages should be identified consistently.
- 3.2.5 Change on Request (AAA): Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Why:
Predictable navigation and functionality help users better understand and interact with a website, especially those with cognitive limitations or who use screen readers.
Examples and Scenarios:
- No Automatic Redirects: Avoid redirecting a user automatically when they select a dropdown option.
- Consistent Menu Placement: Keep menus in the same order across all pages.
- Uniform Button Identification: Use the same icons for similar functions on different pages.
How to Comply:
- Websites: Ensure that user actions do not lead to unexpected changes and maintain consistency in navigation and component identification.
- Mobile Apps: Follow similar principles in app design, keeping user interface elements and navigation consistent.
- Software Applications: Use uniform design patterns and behaviors across different parts of the application.