A keyboard can be used to interact with the interface
All functionalities must be operable using a keyboard without requiring specific timing for keystrokes, except for functions that inherently depend on user movement paths.
Acceptance Criteria
• Keyboard Accessibility: All features must be accessible through keyboard navigation.
• No Timing Restrictions: Keyboard actions should not require specific timing or sequences unless the function inherently needs user movement paths.
Examples
• A form should be fully navigable and operable using only the keyboard.
• A video player should allow play, pause, and volume adjustments via keyboard shortcuts.
• Interactive maps that require dragging to navigate must offer alternative keyboard controls.
Exceptions
• Functions that require input dependent on the path of movement, like drawing with a stylus, are exempt.
Tips
• Ensure all interactive elements are reachable and actionable via keyboard.
• Test keyboard navigation for accessibility to ensure all functions are operable.
How to test?
1. Keyboard Navigation: Use a keyboard to navigate all interactive elements and verify full functionality.
2. Functional Testing: Ensure that all actions can be performed without relying on mouse or touch inputs.
3. Path Dependency Check: Identify any features that inherently require movement paths and confirm their operation.