- From: Walter Ian Kaye <boo@best.com>
- Date: Wed, 10 Jul 1996 20:37:17 -0700
- To: www-html@w3.org
At 5:37p -0400 07/10/96, Daniel W. Connolly wrote:
>While the recent proposal seems at odds with traditional
>HTML design goals, we have been messing around with keyboard
>"shortcut" stuff at W3C.
>
>For example, see:
>
>http://www.w3.org/pub/WWW/MarkUp/Cougar/HTML.dtd
>
><!ELEMENT LABEL - - (%text)* -(LABEL) -- field label text -->
><!ATTLIST LABEL
> %attrs; -- id, class, style, lang, dir --
> for IDREF #IMPLIED -- matches field ID value --
> accesskey CDATA #IMPLIED -- accessibility key character --
> title CDATA #IMPLIED -- advisory title string --
> onClick %script #IMPLIED -- intrinsic event --
> >
>
>The way this is used is, for example:
>
> <FORM>
> <LABEL ACCESSKEY="U">User Name<INPUT
> TYPE="INPUT" NAME=USER></LABEL>
> </FORM>
>
>which might, for example, underline the U in "User Name".
What about conflicts with existing shortcuts? If it's already defined in
the browser (or the Operating System), do the document keys override the
browser/OS keys, or do the browser/OS keys override the document keys? Or
do you instead go into a special "mode" in order to enable the shortcuts,
and then end that mode?
__________________________________________________________________________
Walter Ian Kaye <boo@best.com> Programmer - Excel, AppleScript,
Mountain View, CA ProTERM, FoxPro, HTML
http://www.natural-innovations.com/ Musician - Guitarist, Songwriter
Received on Wednesday, 10 July 1996 23:54:07 UTC