W3C home > Mailing lists > Public > public-html@w3.org > September 2010

[Bug 10775] New: how is user to decide which set of access keys to use?

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Sep 2010 06:54:42 +0000
To: public-html@w3.org
Message-ID: <bug-10775-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775

           Summary: how is user to decide which set of access keys to use?
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: RESOLVED
          Keywords: a11y
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: oedipus@hicom.net
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, oedipus@hicom.net, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |INVALID

QUOTE cite="http://dev.w3.org/html5/spec/editing.html#the-accesskey-attribute"
   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

PROBLEM 1: how does the user know that more than one set of access keys
is available?

PROBLEM 2: how does the user select the set of access keys to use?

PROBLEM 3: can the use switch from one set of access keys to another
should the first set be too complicated to use?  if so, how?

PROBLEM 4: when using more than one token to assign an accesskey to 
a unique element, must all the accesskey values contain the same number 
of tokens in order for the accesskey values to validate?  

PROBLEM 5: why use the phrase "unique space-separated tokens"? 
"unique space-seperated characters, each of which must be exactly
one unicode point in length"

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-28 06:54:42 UTC ---
Please file one problem per bug.

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: Invalid use of bug system.

Looking at the specific problems:

PROBLEM 1: There is no set of access keys, just one key per accesskey'ed
element.

PROBLEM 2: The user agent selects the access key, not the user.

PROBLEM 3: There are no "sets" of access keys.

PROBLEM 4: no

PROBLEM 5: the phrase "unique space-separated tokens" implies certain
conformance requirements described in the infrastructure section.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 28 September 2010 06:54:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:19 UTC