Re: PROPOSAL: Checkpoint for ACCESSKEY

I don't think that we should not have a checkpoint for ACCESSKEY. I do think
that a checkpoint requiring sequential access to elements which have an
ACCESSKEY is inappropriate - the purpose of the element is to provide access
to certain elements in a non-sequential manner.

Charles McCN

On Thu, 6 May 1999, Jon Gunderson wrote:

  ACCESSKEY is defined for the following HTML elements:
  A
  AREA
  BUTTON
  INPUT
  LABEL
  LEGEND
  TEXTAREA
  
  It is designed to move the focus to the next focusable element associated
  with the ACCESSKEY.  
  
  ACCESSKEY is not related to INDEXTAB except we could specify following
  INDEXTAB order if the author has defined an explicit order.
  
  The ACCESSKEY attribute is recommended for use in improving access to Web
  Content in the Web Content guidelines.
  
  IE already supports the ACCESSKEY feature.
  
  I think we need a checkpoint for navigating to items containing this
  attribute.
  
  Are there other people who think a checkpoint relating to using ACCESSKEY
  should not be part of the guidelines?
  
  It would be a priority 3 item, just like in the Web Content guidelines.
  
  Jon
  
  
  At 10:43 AM 5/6/99 -0400, you wrote:
  >I don't think this is a good idea. ACCESSKEY should indentify a unique
  >shortcut in the context of a page. If you want a special tabbing order there
  >is TABINDEX, although it seems counterintuitive to me. If it is only being
  >used for links or form controls we already have checkpoints to give access to
  >just those kinds of elements.
  >
  >Charles McCN
  >
  >On Thu, 6 May 1999, Jon Gunderson wrote:
  >
  >  Checkpoint: Allow the user to sequentially access elements with the
  >  ACCESSKEY attribute defined
  >  Sub-group: Both
  >  Priority: 1 or 2
  >  
  >  Technique
  >  The ACCESSKEY attribute allows authors to provide keyboard support for
  >  directly moving the focus to a link or form control.  When the access key
  >  combination is activated by the user, the focus moves to the next element
  >  in tab order with that ACCESSKEY.  Therefore multiple elements can use the
  >  same ACCESSKEY without conflicit.
  >  
  >  Please comment on this proposal
  >  Jon
  >  
  >  
  >  At 06:01 PM 5/5/99 -0400, you wrote:
  >  >We need a checkpoint on accesskeys, including 
  >  >assignment by an author (or by edict of an application),
  >  >and means for a user to find out what they are.
  >  >
  >  >Should a user personality profile be able to override 
  >  >assignments of authors?
  >  >
  >  >Regards/Harvey Bingham
  >  > 
  >  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
  >  
  >
  >--Charles McCathieNevile            mailto:charles@w3.org
  >phone: +1 617 258 0992   http://www.w3.org/People/Charles
  >W3C Web Accessibility Initiative    http://www.w3.org/WAI
  >MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA
  > 
  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
  

--Charles McCathieNevile            mailto:charles@w3.org
phone: +1 617 258 0992   http://www.w3.org/People/Charles
W3C Web Accessibility Initiative    http://www.w3.org/WAI
MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA

Received on Thursday, 6 May 1999 11:44:50 UTC