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 10779 - triggering the Action of the command via accesskey
Summary: triggering the Action of the command via accesskey
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: Charles McCathieNevile
QA Contact: HTML WG Bugzilla archive list
Depends on:
Blocks: 10888 23613
  Show dependency treegraph
Reported: 2010-09-27 18:04 UTC by Gregory J. Rosmaita
Modified: 2014-02-10 10:01 UTC (History)
10 users (show)

See Also:


Description Gregory J. Rosmaita 2010-09-27 18:04:45 UTC
QUOTE cite=""
When the user presses the key combination corresponding to the assigned 
access key for an element, if the element defines a command, and the 
command's Hidden State facet is false (visible), and the command's 
Disabled State facet is also false (enabled), then the user agent must 
trigger the Action of the command.

note: the term "defines a command" is defined at:

this should be stated less obliquely:

When the user presses the key combination corresponding to the assigned 
access key for an element, if the element defines a command

    1. check if the command's Hidden state facet is false (visible)

    2. check if the command's Disabled state facet is false (enabled)

    3. if the command's Hidden and Disabled state facets are false, 
       trigger the Action of the command.


The above prose should be followed DIRECTLY by a note denoting that 
accesskey activation response MUST be controlled, storable and shareable 
by the user through a user agent setting. If an author defines a 
specific action to a command, users MUST be able to override the author's
suggested action, in observance of a persistent user setting. This 
allows the user to use a "safety" to avoid firing an event defined for
an element when the accesskey defined for that element is invoked, so
that a user may make an informed decision as to whether or not to 
activate the element or to move focus to that element in order to 
inspect it for pre-set triggers.
Comment 1 Ian 'Hixie' Hickson 2010-09-28 07:06:53 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:

Status: Rejected
Change Description: no spec change
Rationale: I don't understand why the proposed text is any less "oblique". It seems to just say the exact same thing but with some additional meaningless fluff (e.g. "check if the command's Hidden state facet is false (visible)").

Regarding the additional consideration, I don't understand what is being requested. Also, please file just one issue per bug.
Comment 2 Joshue O Connor 2010-11-09 16:22:35 UTC
The HTML a11y bug triage sub-team thinks Gregory should provide more information. 10888 would be the master bug for all accesskey related issues.
Comment 3 Martin Kliehm 2010-12-21 16:18:42 UTC
The accessibility TF bug-triage sub-team thinks this bug is handled well by Gregory and it doesn't require the attention of the whole TF.
Comment 4 steve faulkner 2014-02-10 10:01:44 UTC
closing as the resolution is sound and there has been no follow up.