This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
as part of the definition of Action the following is found: QUOTE element . accessKeyLabel Exposes the Access Key facet of the command. UNQUOTE the spec should explicitly state in http://dev.w3.org/html5/spec/editing.html#the-accesskey-attribute that user agents can use element.accessKeyLabel to generate list of available accesskeys PROPOSED SPEC TEXT REVISION: User agents may expose elements that have an accesskey attribute in other ways as well, e.g. in a menu displayed in response to a specific key combination. <ins>user agents can use <code>element.accessKeyLabel</code> to generate list of available accesskeys.</ins>
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: That doesn't make any sense. The user agents are the ones that generate accessKeyLabel, how would they use it to do anything?
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.
*** Bug 17092 has been marked as a duplicate of this bug. ***
This has been taken up as part of the proposal to make user interaction workable, currently divided between Web Platform github issues for HTML [1] and the WICG proposal [2] [1] https://github.com/w3c/html/issues [2] https://discourse.wicg.io/t/user-interaction-with-web-apps/1177/