This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10251 - Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element
Summary: Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, a11ytf, a11y_focus
Depends on:
Reported: 2010-07-28 20:48 UTC by Gregory J. Rosmaita
Modified: 2010-10-04 14:32 UTC (History)
6 users (show)

See Also:


Description Gregory J. Rosmaita 2010-07-28 20:48:19 UTC
one can provide a "cascade" of accesskeys for an individual element 
using a space delimited list; to take the example currently in the HTML5 

QUOTE src-""

... the search field is given two possible access keys, "s" and "0" (in 
that order). A user agent on a device with a full keyboard might pick 
Ctrl+Alt+S as the shortcut key, while a user agent on a small device 
with just a numeric keypad might pick just the plain unadorned key 0:

<form action="/search">
<label>Search: <input type="search" name="q" accesskey="s 0"></label>
<input type="submit">

ISSUE 1. cascade order is a very "weak" rather than a strong binding 
-- how does the user know what accesskey to use when multiple accesskeys 
are assigned to an individual element?

ISSUE 2. "limited group of characters" -- there are a very finite 
number of characters that one can use as an accesskey; is the cascade of 
keys set using a space delimited list global?  (that is, does every first 
item listed belong to accesskey-scheme A, the second to 
accesskey-scheme-B, etc.

<form action="/search">
<label>Search: <input type="search" name="q" accesskey="s 0"></label>
<input type="submit" accesskey="= 1">

in the preceding code sample, is the first accesskey theme:

 1. accesskey for input type="search" = s
 2. accesskey for input type="submit" = =

(for fellow speech users, the first acesskey is the character s while 
the second is the equals-sign)

and the second:

 A. accesskey for input type="search" = 0
 B. accesskey for input type="submit" = 1

(for fellow speech users, the first acesskey is the character 0 while 
the second is the character 1)

SOLUTION: if the above is true, it needs to be explicitly stated in the 
HTML5 spec.
Comment 1 Ian 'Hixie' Hickson 2010-08-18 18:02:20 UTC
Please file separate bugs for separate issues.

For your "ISSUE 1", the answer is that either the author exposes it with accessKeyLabel, or the user agent exposes it in a menu, or (ideally) both.

For your "ISSUE 2", the spec already seems abundantly clear about this; see the definition of "assigned access key". Each accesskey="" attribute is processed independently.

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Accepted
Change Description: no spec change
Rationale: The spec seems to already handle these cases.
Comment 2 Michael Cooper 2010-08-31 13:31:22 UTC

The bug triage sub-team recommends the accessibility task force follow this.