Keyboard (No Exception)

About

Version:	WCAG 2.0 and up
Number:	2.1.3
Level:	AAA
Applicability:	Buttons Custom Controls Forms Inputs
Requirement:	All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Guidance:	Understanding Success Criterion 2.1.3 How to meet Success Criterion 2.1.3
Techniques:	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 SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons

Purpose

The purpose of this success criterion is to ensure that user that require a keyboard to access a publication have access to all functionality in the content without exception.

How to Meet

The requirements for this success criterion are the same as for 2.4.1 Keyboard.

The only difference is that this success criterion does not allow any exceptions (i.e., any functionality that cannot be replicated by keyboard fails).

Additional Information

The following knowledge base pages provide more information about how to address this success criterion for publishing content:

Keyboard Control