Status Review 8/14/2008
Guideline 4.1 Ensure full keyboard access

<old>
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

</old>

<new>
4.1.3 No Keyboard Trap (Minimum): The user agent prevents keyboard traps as follows:

1. in the UI: if keyboard focus can be moved to a component using the keyboard, then focus can be moved away from that component using standard sequential keyboard commands (e.g., TAB key)
2. in the rendered content: provides a documented direct keyboard command that will always restore keyboard focus to a known location (e.g., the address bar). Level A

4.1.xx (Level AA) No Keyboard Trap (Enhanced): In the rendered content, if keyboard focus can be moved to a component using the keyboard, then focus can be moved away from that component using standard sequential keyboard commands (e.g., TAB key).

<http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0057.html>

</new>

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).

Unchanged!!! Also, no discussion.

<old>
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.
</old>

<new>
4.1.6 Standard Text Area Navigation 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.

approved <http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0016.html>

</new>

<old>
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.

Notes on SC 4.1.8

</old>

<new<
Proposed
4.1.8 Direct keyboard commands are provided to activate the following classes of functions (contingent on direct keyboard commands being available in the *operating environment*): (a) most commonly used functions (e.g., address bar, "back" button, etc.) (b) display-related functions (e.g., increase/decrease text size, volume, etc.)

Note: Change "operating environment" Def'n to add device restrictions:

operating environment
The environment that governs the user agent's operation, including both software (e.g., operating system, programming language environments such as Java) and hardware (e.g., mobile devices with a limited number of buttons).

<http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0068.html>

</new>

<old>
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.).
</old>

<new>
User can set configurations that persist between sessions for keyboard commands for both user interface and recognized content.

GJR friendly ammendment: Users SHOULD have the choice of applying specific configurations for a specific site, for the duration of a particular sesion, in the same manner that a user can control cookie collection
<http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0056.html>

ACTION: Gregory - wordsmith user configuration, persistence and override GL [recorded in http://www.w3.org/2008/07/31-ua-minutes.html#action03]

</new>

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.

NO DISCUSSION!!