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

RE: ACCESSKEY attribute

From: M. T. Hakkinen <hakkinen@dev.prodworks.com>
Date: Mon, 16 Feb 1998 15:06:54 -0500
Message-ID: <01BD3AEC.8ABD5A40.hakkinen@dev.prodworks.com>
To: "'Jon Gunderson'" <jongund@staff.uiuc.edu>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
I'm not sure if I understand your comment.

What we are looking at is to announce, for example, the button caption, 
followed by the access key (including modifier).

 For example:  [Search] is announced as "Search Button, Alt S" in the least 
verbose mode.

Also,  in the post by Dave Bolnick, an author specificaiton of available 
short cut keys is also a good approach for use by the screen 
reader/browser, yet this can also be generated by the browser if not 


-----Original Message-----
From:	Jon Gunderson [SMTP:jongund@staff.uiuc.edu]
Sent:	Monday, February 16, 1998 2:47 PM
To:	M. T. Hakkinen; w3c-wai-gl@w3.org; w3c-wai-ig@w3.org
Subject:	RE: ACCESSKEY attribute

Thanks for the information on ACCESSKEY.  But isn't the browser
implementation kind of a big deal.  If I put a statement like "Press S to
submit the form", the user has to press more than S in most browsers.  So
many people will think it doesn't work.  But if I put the "Access key for
the submit button is S".  Most people won't know what an access key is.
There must be a better way to use the access key for authors to adopt it's

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
University of Illinois at Urbana/Champaign
1207 S. Oak Street
Champaign, IL 61820

Voice: 217-244-5870
Fax: 217-333-0248
E-mail: jongund@uiuc.edu
WWW:	http://www.staff.uiuc.edu/~jongund
Received on Monday, 16 February 1998 15:11:29 UTC

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