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


From: Denis Anson <danson@miseri.edu>
Date: Mon, 10 May 1999 08:40:59 -0400
To: "Jon Gunderson" <jongund@staff.uiuc.edu>, "Charles McCathieNevile" <charles@w3.org>
Cc: "WAI UA group" <w3c-wai-ua@w3.org>
I think that Alan Cantor's message shows how crucial it is that the
AccessKey be implemented in a way that makes sense to the user.

While the author can install markup to indicate the AccessKey, it should
also be possible for the user agent to indicate that the key exists.  User
Agents provide a default indication of links, which may be over-ridden by
the author with markup.  That default indication should include a default
indication of the existence of an AccessKey, which also may be overridden by
the author.  (It might also be overridden by the user, with a User Style

I don't think that we should specify what the markup should be, or what the
navigation procedure should be, since there probably isn't one, best method.
But there must be some way to reach multiple links with the same AccessKey
definition, and you must have some clue about what the definition is.

Denis Anson, MS, OTR
Assistant Professor
College Misericordia
301 Lake St.
Dallas, PA 18612

Member since 1989:
RESNA: An International Association of Assistive Techology Professionals

-----Original Message-----
From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On Behalf
Of Jon Gunderson
Sent: Friday, May 07, 1999 1:50 PM
To: Charles McCathieNevile
Cc: WAI UA group
Subject: RE: PROPOSAL: Checkpoint for ACCESSKEY

So you are saying that we don't need to say much at all about the
funcationality of  how the user interface would support the use of
ACCESSKEY attribute.  Just say to implment the ACCESSKEY as per the HTML

Other respones in JRG:

At 01:26 PM 5/7/99 -0400, Charles McCathieNevile wrote:
>I don't want the guidelines document to say "ACCESSKEY". I want the
>guidelines to make reference to a defined set of elements and attributes
>which should be implemented in HTML. There is currently a priority 1
>checkpoint which does precisely that, and I think that is sufficient.

JRG: It already does.

>I think that referenced document should say Accessky is one of the
>which must be implemented by a User Agent which claims to render HTML and
>be accessible.

JRG: I think what we want to make sure is that people understand what it
means to implement the accesskey attribute.  There are two issues:
navigation and visibility.

Some may think just including the attribute in the document object model is
sufficient, others may wonder what to do with multiple definitions of the
same accesskey and not provide access to any element but the first element
of the collection of elements with the same accesskey.

Do we want the user agent to do something to make elements with the
accesskey defined more visible.  Right now only the author can do that with
proper markup.  A recommendatino could be included to have user agents
render the element with the accesskey differently than other elements?

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, 10 May 1999 08:41:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:22 UTC