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

Re: Access Element is WRONG (was RE: Are we really still talking about Access Keys?)

From: Micah Dubinko <micah@dubinko.info>
Date: Fri, 03 Jun 2005 11:17:10 -0700
Message-ID: <42A09EA6.2060400@dubinko.info>
To: Al Gilman <Alfred.S.Gilman@IEEE.org>
CC: "John Foliot - WATS.ca" <foliot@wats.ca>, www-html@w3.org, w3c-wai-ig@w3.org

For the record, XForms' treatment of accesskey should not be viewed as 
any kind of a precedent.

The normative part states "a host language must provide a way to 
indicate overall navigation order among form controls and other elements 
included in the host language, as well as keyboard or direct access 
navigation to specific elements. One such proposal is to uses a pair of 
attributes named |navindex| and |accesskey|, defined as follows:"

The actual definitions are taken roughly from older specifications. My 
understanding is that things were specified this way specifically 
because of the inadequacy of navindex/accesskey, and to not forclose the 
development of better techniques in host languages.

No comments on the rest of the message. Thanks,

.micah

Al Gilman wrote:

>
> The precedent is set in the XForms specification.
>
> <quote>
>
> accesskey
>
> Optional attribute defines a shortcut for moving the input focus
> directly to a particular form control . The value of this is a
> single character which when pressed together with a platform specific
> modifier key (e.g., the alt key) results in the focus being set
> to this form control .
>
> The user agent must provide a means of identifying the accesskeys
> that can be used in a presentation. This may be accomplished in
> different ways by different implementations, for example through
> direct interaction with the application or via the user's
> guide. The accesskey requested by the author might not be made
> available by the player (for example it may not exist on the
> device used, or it may be used by the player itself). Therefore
> the user agent should make the specified key available, but may
> map the accesskey to a different interaction behavior.
>
> </quote>
>
> found by string searching 'accesskey' in:
> http://www.w3.org/TR/xforms/index-all.html

...

-- 
  Available for consulting. XForms, web forms, information overload.
  Micah Dubinko                           mailto:micah@dubinko.info
  Brain Attic, L.L.C.                        http://brainattic.info
  Yahoo IM: mdubinko                                +1 623 298 5172
  Learn XForms today: http://xformsinstitute.com
Received on Friday, 3 June 2005 18:17:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:21 GMT