Return to list of success criteria

2.1.1 Keyboard [Level A]

Description

Keyboard:

2.1.1 All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)Understanding Success Criterion 2.1.1

Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

Back to top

Sufficent Techniques

Sufficient Techniques for 2.1.1 - Keyboard

Note: Other techniques may also be sufficient if they meet the success criterion.

  1. G202: Ensuring keyboard control for all functionality

  2. Ensuring keyboard control by using one of the following techniques.

  3. G90: Providing keyboard-triggered event handlers using one of the following techniques:

  4. FLASH17: Providing keyboard access to a Flash object and avoiding a keyboard trap (Flash) AND using the following techniques as applicable:

Advisory Techniques

Advisory Techniques for 2.1.1 - Keyboard
  • Using XHTML role, state, and value attributes if repurposing static elements as interactive user interface components (future link) AND SCR29: Adding keyboard-accessible actions to static HTML elements (Scripting)

  • Providing keyboard shortcuts to important links and form controls (future link)

  • Using unique letter combinations to begin each item of a list (future link)

  • Choosing the most abstract event handler (future link) (Scripting)

  • Using the onactivate event (future link) (Scripting)

  • Avoiding use of common user-agent keyboard commands for other purposes (future link)

Back to top

Failures

Back to top

Notes

Back to top