Keyboard Proposals for Guideline 4.1

4.1.1 Keyboard Operation: All functionality can be operated via the keyboard using sequential and/or direct keyboard commands that do not require 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 (e.g., free hand drawing). This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

Notes on SC 4.1.1

4.1.2 The user has the option to specify that keystrokes be processed in the following order: user agent user interface, user agent extensions, content keystroke operations administered by the user agent (e.g., access keys), and executable content (e.g., key press events in scripts, etc.).

Notes on SC 4.1.2 and Jan's email of 11 Jul 2008 with the merge of 4.1.2 and 4.1.9

4.1.3 No Keyboard Trap: If focus can be moved to a component with the keyboard, then at least one of the following is true:

(a) standard keys: focus can be moved away from the component with the keyboard using standard navigation keys (i.e., unmodified arrow or tab keys), or
(b) documented non-standard keys: focus can be moved away from the component with non-standard keys and the user is advised of the method

4.1.4 Separate Activation: The user has the option to have selection separate from activation (e.g., navigating through the items in a dropdown menu without activating any of the items).

4.1.5 User Agent Keyboard Commands: Direct keyboard commands for the user interface (excluding those derived from the content being rendered) are available:

(a) in context (e.g., keyboard shortcuts listed beside menu items) or via a centralized list that can be displayed by a simple keyboard action, and
(b) programmatically to assistive technology.

Notes on SC 4.1.5

4.1.X Content Derived Keyboard Commands: Direct keyboard commands that are *recognized* within the content are available:

(a) in context (e.g., a button labelled with its associated access key) or via a centralized list that can be displayed by a simple keyboard action (e.g., a list of access keys), and
(b) programmatically to assistive technology.

4.1.6 Standard Text Area Conventions: Views that render text support the standard text area conventions for the platform including, but not necessarily limited to: character keys, backspace/delete, insert, "arrow" key navigation (e.g., "caret" browsing), page up/page down, navigate to start/end, navigate by paragraph, shift-to-select mechanism, etc.

4.1.7 User Interface Navigation: The user can use the keyboard to traverse all of the controls forwards and backwards, including controls in floating toolbars, panels, and user agent extensions using the navigation conventions of the platform (e.g., via "tab", "shift-tab", etc. ")

Notes on SC 4.1.7

4.1.8 Keyboard Commands for Primary Functions: Functions that are primary to the operation of the user agent have an option to enable key-plus-modifier-key (or single-key) access to them. Examples of these primary functions include:

(a) move content focus to the next/previous enabled element in document order,
(b) activate the link designated by the content focus,
(c) open search function, search again
(d) increase/decrease the scale of rendered text,
(e) increase/decrease global volume,
(f) stop/pause/resume and navigate efficiently audio and animations, including video and animated images,
(g) next/previous history state (i.e., forward/back),
(h) enter a URI for a new resource,
(i) add a URI to favorites (i.e., bookmarked resources),
(j) view favorites,
(k) reload a resource,
(l) interrupt a request to load or reload a resource,
(m) navigate forward and backward through rendered content by approximately the height of the viewport, and
(n) for user agents that render content in lines of (at least) text: move the point of regard to the next and previous line.

4.1.9 Precedence of Keystroke Processing: Keystrokes are processed in the following order: user agent user interface, user agent extensions, content keystroke operations administered by the user agent (e.g., access keys), and executable content (e.g., key press events in scripts, etc.).

4.1.10 User Override of Keyboard Commands: The user can override any keyboard shortcut binding that is part of the user agent default input configuration except for conventional bindings for the operating environment (e.g., for access to help). The user can override any author supplied content keybinding (i.e. access key) that the user agent can recognize. The keyboard combinations offered for rebinding include single key and key plus modifier keys if these are available in the operating environment. The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session.

Notes on SC 4.1.10

4.1.11 Intergroup Navigation: If logical groups of focusable controls (e.g., toolbars, dialogs, labeled groups, panels) are present, the user can use the keyboard to navigate to a focusable control in the next and previous groups.

4.1.12 Group Navigation: If logical groups of focusable controls are present, the user can use the keyboard to navigate to the first, last, next and previous controls in the current group.

Notes on SC 4.1.12

Guideline 4.1 Ensure full keyboard access

Success Criterion 4.1.1 (Level A)

Success Criterion 4.1.2 (Level A)

Success Criterion 4.1.3 (Level A)

Success Criterion 4.1.4 (Level A)

Success Criterion 4.1.5 (Level A)

Success Criterion 4.1.x (Level A)

Success Criterion 4.1.6 (Level A)

Success Criterion 4.1.7 (Level A)

Success Criterion 4.1.8 (Level AA)

Success Criterion 4.1.9 (Level AA)

Success Criterion 4.1.10 (Level AA)

Success Criterion 4.1.11 (Level AAA)

Success Criterion 4.1.12 (Level AAA)