- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Sep 2010 14:23:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775 Gregory J. Rosmaita <oedipus@hicom.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Gregory J. Rosmaita <oedipus@hicom.net> 2010-09-30 14:23:20 UTC --- (In reply to comment #1) in response to comment #0 >>PROBLEM 1: how does the user know that more than one set of access keys >>is available? the editor replied: > 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. 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 are you saying that a single element may have multiple accesskeys that act as synonyms? -- in other words, accesskey="S @ 1" assigned to an element would be triggered by either the character capital-S the at-sign or the numeral 1? is the user agent or assistive technology supposed to inform the user of all of the options available as an accesskey for an element? if so, how precisely does the cascade work? first token, second token, third token? if i use the first token for one element and the second for another, both will cause the expected action for the individual elements for which they have been assigned when the accesskey is invoked? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 30 September 2010 14:23:27 UTC