Section 2: Operable
The "Operable" principle ensures that users can navigate and interact with web content effectively. This involves making sure that all functionality is accessible via keyboard, giving users enough time to interact, and ensuring predictable navigation and input methods.
2.1 Keyboard Accessibility
Ensure all functionality is operable using only a keyboard, and avoid keyboard traps.
- Example: Interactive elements like buttons and menus must be accessible through keyboard navigation.
- Example: Include mechanisms to exit or cancel interactions if trapped in a modal dialog.
2.2 Enough Time
Provide users with enough time to read or interact with content, with options to pause, extend, or disable timing constraints.
- Example: Allow users to pause slideshows or extend session times.
- Example: Warn users before a session timeout occurs and provide an option to stay logged in.
2.3 Seizures and Physical Reactions
Avoid content that may trigger seizures or physical discomfort, such as flashing lights or rapid animations.
- Example: Limit flashing elements to less than three flashes per second.
- Example: Use safe transitions for animations to avoid discomfort for users with motion sensitivity.
2.4 Navigable
Provide clear navigation mechanisms to help users find and access content easily.
- Example: Include "Skip to Content" links to bypass repetitive elements like navigation menus.
- Example: Use meaningful link text for easier identification, such as "Learn more about accessibility" instead of "Click here."
2.5 Input Modalities
Ensure operability for various input methods, such as touch, voice, and motion-based gestures.
- Example: Provide alternatives for complex gestures, like using single taps or clicks instead of multi-finger swipes.
- Example: Enable motion-activated features to be operable through buttons or voice commands.