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
specification?
Jon

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 attributes
>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
	http://www.als.uiuc.edu/InfoTechAccess

Received on Friday, 7 May 1999 13:44:18 UTC