- From: <schwer@us.ibm.com>
- Date: Tue, 12 Oct 1999 19:08:56 -0500
- To: ij@w3.org
- cc: w3c-wai-ua@w3.org
Ian, Here are some techniques for checkpoints 2.1 through 2.6. Technique 2.1 Use the techniques in section 1.1 as they pertain to a keyboard input device. Technique 2.2 - Documentation for default keyboard commands should be provided in electronic format for direct access as defined in Technique 1.5. Keyboard commands should include but not be limited to shortcuts, accelerators, tab keys, and element activation keys. Technique 2.3 - Documentation for the current keyboard commands should be provided in electronic format for direct access as defined in Technique 1.5. Keyboard commands could change as a result of the addition of navigation bar tasks, addition of document defined accesskeys, and/or changing the default keyboard actions through a keyboard mapping facility. When constructing a keyboard mapping facility it is important to provide associated descriptions for the task being mapped. Technique 2.4 A mechanism for allowing the user to configure the mapping of key strokes to user agent functionalities is to implement a keyboard mapping facility. Technique 2.5 A mechanism to allow the user to turn on and off author-specified keyboard configurations is to add a checkbox in the keyboard mapping dialog to that would toggle the support for author-specified keyboard configurations. An example of author-specified keyboard configurations is the use of the HTML 4.0 accesskeys. Technique 2.6 Platform conventions used to indicate which keys activate which user agent functionalities are using the shortcut key (mnemonics), and keyboard accelerators defined in standard controls. These are visually rendered using an underscore under a character in a menu item or button corresponding to the shortcut key activated with an ALT+character. For menu accelerators the text in the menu item is often followed by a CNTRL+function key. These are conventions used by the Sun Java Foundations Classes and Microsoft Foundations Classes for Windows. Rich Provide information to the user about the current keyboard configuration Provide documentation on default keyboard commands and include with user agent documentation and/or user help system Rich Schwerdtfeger Lead Architect, IBM Special Needs Systems EMail/web: schwer@us.ibm.com http://www.austin.ibm.com/sns/rich.htm "Two roads diverged in a wood, and I - I took the one less traveled by, and that has made all the difference.", Frost
Received on Tuesday, 12 October 1999 20:21:58 UTC