This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
1. the unicode expression of the latin capital letter x is U+0058 2. the unicode expression of the latin lowercase letter x is U+0078 so, since HTML5 states that, "If specified, the [accesskey] value must be an ordered set of unique space-separated tokens, each of which must be exactly one Unicode code point in length, does this mean that accesskeys are case sensitive? if so, it must be explicitly stated; if not, it also must be explicitly stated that accesskeys are case insensitive.
I should also fix this for <form accept-charset> (which should be case-insensitive, unlike accesskey).
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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r5571. Check-in comment: Better define how sets of unique space-separated tokens are handled in terms of case-sensitivity. http://html5.org/tools/web-apps-tracker?from=5570&to=5571
Confirming the changes made it into the spec, concerning <code>accesskey</code> in http://www.w3.org/TR/html5/editing.html#the-accesskey-attribute
Bug triage sub-team does not think this needs to be a TF priority. Assigning to Gregory to confirm changes and close.