10776 2010-09-27 17:57:17 +0000 accesskey value token subsets 2013-10-23 19:59:21 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED WONTFIX a11y P2 normal LC 10888 23613 1 oedipus ian ian joshue.oconnor laura.lee.carlson mike oedipus public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 39594 0 oedipus 2010-09-27 17:57:17 +0000 For each value in keys in turn, in the order the tokens appeared in the attribute's value, run the following substeps 1. If the value is not a string exactly one Unicode code point in length, then skip the remainder of these steps for this value. 2. If the value does not correspond to a key on the system's keyboard, then skip the remainder of these steps for this value. 3. If the user agent can find a combination of modifier keys that, with the key that corresponds to the value given in the attribute, can be used as a shortcut key, then the user agent may assign that combination of keys as the element's assigned access key and abort these steps. PROBLEM with subsets 1 and 2: does this, in fact, mean: 1. If the value is not a string exactly one Unicode code point in length, procede to the fallback step for this value. 2. If the value does not correspond to a key on the system's keyboard, then procede to the fallback step for this value. if so, why not say so? subset 3 is event more problematic: for that i will submit a separate bug 39681 1 ian 2010-09-28 07:01:41 +0000 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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: No, it only means to skip the steps for the one bogus value, not for the whole attribute. There might be more values after this one. 41768 2 joshue.oconnor 2010-10-26 15:58:25 +0000 The HTML A11y Bug Triage Subteam decided that this not an issue and that Gregory should escalate this bug if he feels it is warranted.