W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 1998

RE: ACCESSKEY on FORM controls

From: T. V. Raman <raman@Adobe.COM>
Date: Fri, 19 Jun 1998 20:35:42 -0700 (PDT)
Message-ID: <13707.11790.729511.724910@labrador>
To: "Charles (Chuck) Oppermann" <chuckop@microsoft.com>
Cc: "'jkrieger@cast.org'" <jkrieger@cast.org>, w3c-wai-gl@w3.org
The access key is especially needed when using 
browsers like IE that are broken with respect 
to what "next link" as per the tab key means--
for instance you can search through a page in IE, and then
hit tab,
and you will find that you wont necessarily jump to the link
closest to where you stoped searching.

you get better behavior purely because emacs does the right
thing with incremental search.On real browsers like Emacs/W3 
Charles (Chuck) Oppermann writes:
 > The Microsoft Enable web site uses ACCESSKEY=Q to get to the QuickLink list
 > box of choices.  A experienced user of the site can go in, press ALT+Q,
 > arrow to the correct link and press Enter to get to it.  If using Tab
 > navigation, they would have to wade through a long series of links.  
 > Large forms will have difficulty with assigning unique identifiers.
 > ACCESSKEY comes in handy for HTML dialogs and smaller forms.  I would say
 > that if your form is so large that you cannot come up with unique
 > ACCESSKEY's, then it's a usability problem and suggestion that the page be
 > broken up.
 > -----Original Message-----
 > From: Josh Krieger [mailto:jkrieger@cast.org]
 > Sent: Thursday, June 18, 1998 8:31 AM
 > To: w3c-wai-gl@w3.org
 > Subject: ACCESSKEY on FORM controls
 > > 8.9. Furnish keyboard shortcuts for form elements
 > This guideline's example places the ACCESSKEY attribute on the
 > LABEL associated with the form control. 
 > 1. If this is the preferred method of doing this sort of 
 > thing, then why do all the form controls have ACCESSKEY 
 > attributes themselves?
 > 2. <BUTTON> and <INPUT TYPE=BUTTON> don't have
 > labels associated with them and the ACCESSKEY should
 > be directly specified on these controls. 
 > 3. I don't quite understand why we even have access keys
 > for forms at all. It seems to me that for any practical
 > web-based form it isn't really usefull not to mention
 > kind of crazy if the keys change on every web page.
 > On some forms, because of their size, using accesskeys
 > would be impossible. Does someone have a comprehensive 
 > vision of how this is supposed to be used?
 > Josh Krieger

Best Regards,

      Adobe Systems                 Tel: 1 (408) 536 3945   (W14-612)
      Advanced Technology Group     Fax: 1 (408) 537 4042 
      (W14 129) 345 Park Avenue     Email: raman@adobe.com 
      San Jose , CA 95110 -2704     Email:  raman@cs.cornell.edu
      http://labrador.corp.adobe.com/~raman/        (Adobe Intranet)
      http://cs.cornell.edu/home/raman/raman.html    (Cornell)
    Disclaimer: The opinions expressed are my own and in no way should be taken
as representative of my employer, Adobe Systems Inc.
Received on Friday, 19 June 1998 23:35:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:27 UTC