Keyboard (No Exception)

Understanding WCAG2.0

There are no components that require specific timing for keyboard operation

Principle	Operable	User interface components and navigation must be operable.
Guideline	Keyboard Accessible	Make all functionality available from a keyboard.
Criterion	Keyboard (No Exception) (2.1.3 AAA)	All functions of the content can be operated through the keyboard interface without requiring specific timing for individual keystrokes.

URL of Techniques for WCAG 2.0

• G90: Providing keyboard-triggered event handlers
• G202: Ensuring keyboard control for all functionality
• H91: Using HTML form controls and links
• SCR2: Using redundant keyboard and mouse event handlers
• SCR20: Using both keyboard and other device-specific functions
• SCR29: Adding keyboard-accessible actions to static HTML elements
• SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons
• PDF3: Ensuring correct tab and reading order in PDF documents
• PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents
• PDF23: Providing interactive form controls in PDF documents
• F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links
• F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function
• F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received