- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 8 Mar 2012 11:19:28 -0600
- To: WAI-ua <w3c-wai-ua@w3.org>
Delete 214 as per Jan 20 Minutes http://www.w3.org/2012/01/20-ua-minutes.html#action03 New Summary for GL 2.3 @@newstuff@@ Summary: Users can navigate directly (e.g. keyboard shortcuts) to important elements (2.3.1) with the option of immediate activation of the operable elements (2.3.3). Display commands with the elements to make it easier for users to discover the commands (2.3.2 & 2.3.4). The user can remap @@and save the user interface and content@@ direct commands to their needs (2.3.5). old summary Summary: Users can navigate directly (e.g. keyboard shortcuts) to important elements (2.3.1) with the option of immediate activation of the operable elements (2.3.3). Display commands with the elements to make it easier for users to discover the commands (2.3.2 & 2.3.4). The user can remap the direct commands to their needs (2.3.5). Complete new 2.3.5 2.3.5 Customize Keyboard Commands: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). The user must be able to save these settings beyond the current session. (Level AA) Intent of Success Criterion 2.3.5 Some users may be able to hit certain keys on the keyboard with greater ease than others. Assistive technology software typically has extensive keyboard commands as well. The goal of this SC is to enable the user to be in control of what happens when a given key is pressed and use the keyboard commands that meet his or her needs, and the ability to save the modifications.@@added from 214@@ Content authors may utilize the Accesskey attribute to define short cut keys which allow quick access to specific elements, actions, or parts of their Web content. The author-selected short cuts may utilize keystrokes that are unique to their site, differing from conventions used, and or familiar, to users of other similar sites, or sites offering similar functionality. Users of assistive technologies who rely upon keyboard input may wish to have a consistent mapping of shortcut keys to similar, or common actions or functions across the sites they visit. User agents should allow users to define a preferred key combination for specific instances of author defined accesskeys. The user should have the option to make any defined override to be persistent across browsing sessions. User agents may also offer the user the option to automatically apply preferred key combinations for content which has author supplied accesskey bindings, based upon the associated text, label, or ARIA role, and which override any author specified keybinding for that page content. Examples of Success Criterion 2.3.5: o A speech recognition user has defined standard commands to access commonly used parts of a Web site. For example, speaking the command "site search" will take the user to a Web site's search function. A site author may assign an access key to set focus to the search input field, basing the accesskey on the first letter of the search engine used (e.g. G for Google or B for Bing, rather than the mnemonic S for search). The speech user has specified an override key mapping of S, which is consistent with the keystroke issued by the speech recognizer they are using. o A mobile device user, whose primary keyboard interface is their phone's numeric keypad, maps common Web site actions to numeric shortcut keys. For example, the user prefers to have the 1 key to activate a site's "skip to content" function. An author of a site visited daily by this user defines "S" as the accesskey for the skip to content function. The user overrides the author defined accesskey of "S" with "1". o Laura types with one hand and finds keys on the left side of the keyboard easier to press. She browses to a web page and notices that the author has assigned access keys using keys from the right side of the keyboard. She opens a dialog in the user agent and reassigns the access keys from the web page to the left side of the keyboard home row. @@added from 214@@ o Elaine's screen magnification program uses alt+m to increase the size of the magnified area of the screen. She notices that in her web browser, alt+m is a hotkey for activating a home button that stops her from being able to control her magnification software. She opens a hotkey reassignment feature in the user agent, and sets alt+o to be the new hotkey for the home button. Her screen magnification software now works correctly.@@added from 214@@ o @@ Editors' Note: good place to add i18n example, accesskey - o umlaut, but not on local keyboard@@ Since 2.1.4 is deleted the summary for GL 2.1 needs to be rewritten and GL 2.1 will need to be RENUMBERED. Summary: Users can operate all functions (2.1.1), and move focus (2.1.2, 2.1.3) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.8), escape keyboard traps (2.1.5), specify that selecting an item in a dropdown list or menues not activate that item or move to that new web page (2.1.6) and use standard keys for that platform (2.1.7). @@removed section on 214@@ -- Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 8 March 2012 17:19:52 UTC