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

Re: ACCESSKEY on FORM controls

From: Josh Krieger <jkrieger@cast.org>
Date: Mon, 22 Jun 1998 07:40:24 -0400
Message-ID: <358E42A8.EE1A9CF3@cast.org>
To: w3c-wai-gl@w3.org
I think people misunderstood some of what I was talking
about. The first 2 points below are technical questions
about how we use the ACCESSKEY, LABEL, and FORM controls
together. The last point, a more general comment, was
about the praticality of many different web pages having
different sets of command keys making them hard to learn
and use. It would seem to me that while having author 
customized access keys on a web page/site may be useful
in particular instances, it is not generally so. Further,
it is not nearly as useful as a user-agent standardized set 
of keyboard commands that would guarantee that all web
browsers allow movement through forms, links, image maps,
etc. in the same manner using the same keys. 

Josh Krieger 

Josh Krieger wrote:
> > 8.9. Furnish keyboard shortcuts for form elements
> This guideline's example places the ACCESSKEY attribute on the
> LABEL associated with the form control.
> 1. If this is the preferred method of doing this sort of
> thing, then why do all the form controls have ACCESSKEY
> attributes themselves?
> 2. <BUTTON> and <INPUT TYPE=BUTTON> don't have
> labels associated with them and the ACCESSKEY should
> be directly specified on these controls.
> 3. I don't quite understand why we even have access keys
> for forms at all. It seems to me that for any practical
> web-based form it isn't really usefull not to mention
> kind of crazy if the keys change on every web page.
> On some forms, because of their size, using accesskeys
> would be impossible. Does someone have a comprehensive
> vision of how this is supposed to be used?
> Josh Krieger
Received on Monday, 22 June 1998 07:40:46 UTC

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