Keyboard
Summary:
WCAG 2.1.1, "Keyboard," is all about ensuring web content is fully navigable and operable using a keyboard. This caters to users who can't or prefer not to use a mouse, making your digital content accessible to a broader audience, including those with physical disabilities or visual impairments.
What:
This guideline requires that all functionalities on a website or application, like navigating menus, activating links or buttons, and filling out forms, must be operable via keyboard commands. It aims to eliminate the need for a mouse to interact with digital content.
Why:
Keyboard accessibility is a cornerstone of web inclusivity. Many users rely solely on keyboards due to various reasons - maybe they have motor skill difficulties, are visually impaired, or just find keyboards more efficient. Ensuring your content is keyboard-friendly opens it up to everyone, not just those who can wield a mouse.
Examples and Scenarios:
- Navigating Menus: Users should be able to use the tab and arrow keys to navigate website menus and select items with the Enter key.
- Form Submission: All forms should be fillable using a keyboard, including selecting options, checking boxes, and submitting the form.
- Interactive Elements: Any interactive elements, like carousel sliders or modal windows, should be fully operable with keyboard shortcuts.
How to Comply:
- Websites: Use semantic HTML and ensure that all interactive elements are focusable and can be activated via keyboard commands. Regularly test your site's keyboard navigability.
- Mobile Apps: For apps, support external keyboards, especially for complex interactions or data entry.
- Software Applications: Design UIs to be keyboard-friendly, with clear focus indicators and logical navigation order.
Exceptions:
- Complex Tasks: Certain tasks that are inherently non-keyboard-based, like freehand drawing or complex gestures, may not fully comply. However, alternative options or support should be provided for these functionalities.