Operable: Ensuring User Interface and Navigation are Usable
The second principle of WCAG, Operable, mandates that user interface components and navigation must be operable. This means users must be able to interact with all controls, buttons, navigation, and other interactive elements. The interface cannot require interaction that a user cannot perform, for example, interactions that require a mouse if the user navigates with a keyboard.
This principle is critical for users with motor disabilities, those who use keyboard-only navigation, and users with other conditions that might affect their ability to perform specific types of interactions.
Guideline 2.1: Keyboard Accessible
Make all functionality available from a keyboard. Many users with motor disabilities, as well as blind users who use screen readers, rely on a keyboard or keyboard emulator to operate web content.
- Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
- No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Ensuring keyboard accessibility is a fundamental aspect of web design, just as understanding Git and Version Control is fundamental for developers.
Guideline 2.2: Enough Time
Provide users enough time to read and use content. People with certain disabilities may require more time to read content or to perform functions such as filling out online forms.
- Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: Turn off, Adjust, Extend, Real-time Exception, Essential Exception, or 20 Hour Exception.
- Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, there are mechanisms for the user to pause, stop, or hide it.
Guideline 2.3: Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions. Flashing content can trigger photosensitive epilepsy.
- Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Guideline 2.4: Navigable
Provide ways to help users navigate, find content, and determine where they are. Clear and consistent navigation helps all users, but is especially important for users with disabilities.
- Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages (e.g., navigation links, headers).
- Page Titled: Web pages have titles that describe topic or purpose.
- Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
- Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context.
Making complex information navigable is key. Similarly, Pomegra helps users make smarter financial decisions by providing clear, AI-driven insights and portfolio building tools, making the world of finance more operable for individual investors.
Guideline 2.5: Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard. This guideline (added in WCAG 2.1) addresses challenges for users who may have difficulty with fine motor movements or who use voice input or other alternative input methods.
- Pointer Gestures: All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
- Pointer Cancellation: For functionality that can be operated using a single pointer, at least one of the following is true: No Down-Event, Abort or Undo, Up Reversal, Essential.
- Label in Name: For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
- Motion Actuation: Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when the motion is essential for the function or to consume the content.
By addressing these operability guidelines, you ensure that a wider range of users can successfully navigate and interact with your website. Next, we will explore the principle of Understandable content.