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 10773 - accesskey should chosen from document's declared charset
Summary: accesskey should chosen from document's declared charset
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: LC
Assignee: Gregory J. Rosmaita
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on: 10775
Blocks:
  Show dependency tree / graph
 
Reported: 2010-09-27 17:46 UTC by Gregory J. Rosmaita
Modified: 2011-01-18 16:28 UTC (History)
9 users (show)

See Also:

Attachments

Description Gregory J. Rosmaita 2010-09-27 17:46:29 UTC 
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.
Comment 1 Ian 'Hixie' Hickson 2010-09-28 06:58:10 UTC 
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.
Comment 2 Martin Kliehm 2010-12-21 15:43:17 UTC 
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.
Comment 3 Michael Cooper 2011-01-18 16:28:10 UTC 
Bug triage sub-team does not think this needs to be a TF priority. Assigning to Gregory to address recommendation in comment 2.