W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > January 2000

RE: new technique: Technique 9.5.1 [priority 3] Check for "accesskey" attribute

From: Michael Cooper <mcooper@cast.org>
Date: Fri, 28 Jan 2000 13:33:42 -0500
To: "Wendy A Chisholm" <wendy@w3.org>, <w3c-wai-er-ig@w3.org>
Message-ID: <NCBBJOMIELMIDGCAPFCICEFFCOAA.mcooper@cast.org>
The HTML spec actually doesn't define the ACCESSKEY attribute for the SELECT
element. I'm not sure why since it does have it for INPUT, but I assume it's
because an INPUT whose TYPE is not "text" will not have an associated LABEL
element to receive the ACCESSKEY, whereas any SELECT element will. But
anyway the spec isn't clear so I don't know if we should keep SELECT in the
list, or add those provisions for INPUT, or what. Michael

> -----Original Message-----
> From: w3c-wai-er-ig-request@w3.org
> [mailto:w3c-wai-er-ig-request@w3.org]On Behalf Of Wendy A Chisholm
> Sent: Friday, January 28, 2000 12:40 PM
> To: w3c-wai-er-ig@w3.org
> Subject: new technique: Technique 9.5.1 [priority 3] Check for
> "accesskey" attribute
>
>
> Technique 9.5.1 [priority 3] Check for "accesskey" attribute
> Discussion Status:
> awaiting discussion
> Evaluation:
> Check the following elements for an "accesskey" attribute:
> A
> AREA
> BUTTON
> INPUT
> LABEL
> LEGEND
> SELECT
> TEXTAREA
> Example Language:
> Create short keys to important active elements on this page.
> Repair Technique:
> none
> Test Files and Discussion Files:
> --
> wendy a chisholm
> world wide web consortium
> web accessibility initiative
> madison, wi usa
> tel: +1 608 663 6346
> /--
Received on Friday, 28 January 2000 13:42:04 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:10:34 GMT