- From: Charles McCathieNevile <charles@w3.org>
- Date: Fri, 9 Jun 2000 23:28:48 -0400 (EDT)
- To: Jason White <jasonw@ariel.ucs.unimelb.edu.au>
- cc: Web Content Accessibility Guidelines <w3c-wai-gl@w3.org>
- Message-ID: <Pine.LNX.4.20.0006092327360.10416-100000@tux.w3.org>
The inherent problem is that if the K key is reassigned on me, then I can no longer find out what the commands available to me are in lynx. The alternative of specifying the ctrl-w key means that in netscape on linux my browser quits (or can no longer be quit). And so on. Charles McCN On 2000年6月10日, Jason White wrote: My understanding from the previous discussion of this point is that ACCESSKEY specifies a Unicode character, which the author should choose as a mnemonic (as in a good menu system). The key or key sequence to be used in entering the access character is (or should be) implementation-dependent, as should the highlighting, voice quality or other style property which serves to identify it in the user interface. I agree with Charles that there are dependencies here involving thg UA and PF, but that the relevant authoring technique is to choose a mnemonic character with which to identify the form control, link, etc., which should then be provided as the value of ACCESSKEY. Do not use the same value twice in a single document. I don't think ACCESSKEY is inherently problematic. It might better be called MNEMONICCHARACTER, a name which would undercut the implication that there exists (or should exist) a direct correspondence between the character and a keyboard. -- Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 Postal: GPO Box 2476V, Melbourne 3001, Australia
Received on Friday, 9 June 2000 23:28:54 UTC