10773 2010-09-27 17:46:29 +0000 accesskey should chosen from document's declared charset 2011-01-18 16:28:10 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All VERIFIED WONTFIX a11y P2 normal LC 10775 1 oedipus oedipus cooper ian laura.lee.carlson mike oedipus public-html-a11y public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 39591 0 oedipus 2010-09-27 17:46:29 +0000 CURRENT QUOTE If specified, the value must be an [161]ordered set of unique space-separated tokens, each of which must be exactly one Unicode code point in length. UNQUOTE PROBLEMS: "the value must be an ordered set of unique space-separated tokens" 1. a single character may be used for an accesskey assignment; the spec should reflect this; 2. although the spec uses the defined term "ordered set of unique space-separated tokens" PROPOSED An accesskey attribute's value may be a single character or an ordered set of unique space-separated tokens. Each character must be exactly one Unicode code point in length and must be part of the document's declared character set. 39679 1 ian 2010-09-28 06:58:10 +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: A set can have just one (or even zero) items in it, there is no contradiction here. 43499 2 w3c 2010-12-21 15:43:17 +0000 Reviewing the bug for the Accessibility TF bug-triage sub-team I believe the fix for bug #10775 solved this issue. Changing the state to VERIFIED. @Gregory, if you concur please close the bug. 44438 3 cooper 2011-01-18 16:28:10 +0000 Bug triage sub-team does not think this needs to be a TF priority. Assigning to Gregory to address recommendation in comment 2.