current working draft: http://www.w3.org/TR/UAAG20/#principle-operable
previous rewrite http://www.w3.org/WAI/UA/2008/keyboardProposals20080714.html
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 approved provisionally http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0038.html, but then discussion...
ACTION: KF to Look at how 4.1.1 and 4.1.7 might fit together [recorded in http://www.w3.org/2008/07/17-ua-minutes.html#action04]
<old>
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
</old>
<new>
Heavily discussed - http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0056.html
- no decision.
ACTION: Kelly - draft more definitive fact-based opinion from IE developers [recorded in http://www.w3.org/2008/07/31-ua-minutes.html#action02]
</new>
</old>
<new>
4.1.3 No Keyboard Trap (Minimum): The user agent prevents keyboard traps as
follows:
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.5 User Agent Keyboard Commands: Direct keyboard commands for the
user interface (excluding those derived from the content being rendered) are
available:
Notes on SC 4.1.5
</old>
<new>
4.1.5 User has the option to have the keyboard commands for currently
available UI and interactive CONTENT controls be presented in close proximity
to the control in the modality of presentation, easily discoverable without
AT, and able to be activated with a single keystroke. with NOTE:For a visual
browser, this needs to be a visual mode, for an auditory browser, it must be
an auditory mode.
<http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0093.html>
</new>
4.1.X Content Derived Keyboard Commands: Direct keyboard commands that are *recognized* within the content are available:
incorporated into 4.1.5
<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>
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. ")
Proposed: REMOVE <http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JulSep/0036.html>
</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>
<old>
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.
<old>
<new>
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 keyboard combinations offered for
rebinding include single key and key plus modifier keys if these are
available in the operating environment.
ADD
4.1.xx
The user can override any author supplied content keybinding (i.e. access
key) that the user agent can *recognize*. The user must have an option to
save the override of user interface keyboard shortcuts so that the rebinding
persists beyond the current session.
from <http://lists.w3.org/Archives/Public/w3c-wai-ua/2008AprJun/0155.html>
</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!!
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.
NO DISCUSSION!!