This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
in the definition of accesskey, HTML5 states: QUOTE cite="http://dev.w3.org/html5/spec/editing.html#the-accesskey-attribute" All HTML elements may have the accesskey content attribute set. The accesskey attribute's value is used by the user agent as a guide for creating a keyboard shortcut that activates or focuses the element. If specified, the value must be an ordered set of unique space-separated tokens, each of which must be exactly one Unicode code point in length. UNQUOTE and yet, at: http://dev.w3.org/html5/spec/common-microsyntaxes.html#ordered-set-of-unique-space-separated-tokens HTML5 defines an ordered set of unique space-separated tokens as "a set of space-separated tokens where none of the words are duplicated but where the order of the tokens is meaningful." this is an incomplete definition, as accesskeys are characters, not words. PROPOSED CLARIFICATION: An ordered set of unique space-separated tokens is a set of space-separated tokens where none of the characters or words are duplicated, but where the order of the tokens is meaningful.
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: A "word" is just used to mean the same as token -- a string of characters with no whitespace (no word separators). This is pretty common practice in the industry.
The Bug Triage Sub Team don't think this is a priority. Gregory can escalate this bug if he so chooses.
There is a more serious bug here, that in most major browsers putting more than one character actually causes the browser to *stop* recognising the attribute. However this has been taken up in the HTML github tracker: https://github.com/w3c/html/issues/20