The WCAG Explained

Summary:
WCAG 2.1, "Keyboard Accessible," ensures that all web and digital content functionalities are operable through keyboard inputs alone. This is crucial for users who can't use a mouse due to physical, visual, or technological constraints. The focus here is on universal keyboard navigation, empowering a wider range of users to interact with digital content seamlessly.

What:
This guideline mandates that all interactive elements on websites and applications must be accessible using a keyboard. This includes navigating through menus, activating buttons and links, filling out forms, and controlling media players, all without the necessity of a mouse.

1. 2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
2. 2.1.2 No Keyboard Trap: Users can navigate through and away from any element using a keyboard without getting "trapped" in any part of the content.
3. 2.1.3 Keyboard (No Exception): All content functionality is operable through a keyboard without any exceptions. This is a Level AAA criterion, indicating a higher standard of accessibility.
4. 2.1.4 Character Key Shortcuts: If a keyboard shortcut is implemented using only a letter, punctuation, number, or symbol characters, users have the ability to turn it off, remap it, or activate it only when the component has focus.

Why:
Many users rely on keyboards or keyboard-like devices due to physical disabilities, visual impairments, or simply due to preference or convenience. Keyboard accessibility is vital as it ensures that these users have equal access to web and digital services, promoting inclusivity and usability in the digital sphere.

Examples and Scenarios:

1. Navigating Menus: Users should be able to navigate a website's dropdown menus using arrow keys and select items with the Enter key.
2. Interactive Elements: Elements like buttons, form fields, and links should be focusable and activatable using the Tab and Enter keys.
3. Media Players: Keyboard users need to be able to control media players, including play, pause, and volume adjustment, using keyboard shortcuts.

How to Comply:

• Websites: Ensure that all interactive elements are accessible via keyboard. This can be achieved by using standard HTML elements and testing navigation with a keyboard.
• Mobile Apps: While primarily touch-based, ensure apps support external keyboard controls for their features.
• Software Applications: Design user interfaces such that all actions can be performed using a keyboard.

Exceptions:

• Complex Components: Certain complex components, like canvas-based games or advanced data grids, might pose challenges for keyboard-only navigation. In such cases, providing an alternative accessible solution is recommended.
• Time-based Testing: Activities where the timing of the user’s action is essential (like real-time games or tests) might not comply entirely but should be made as accessible as possible.