[Bug 21623] 7.5.2 The accesskey attribute: Comment regarding its usage on "All" HTML elements

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21623

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |robin@w3.org
         Resolution|---                         |WONTFIX
           Assignee|dave.null@w3.org            |robin@w3.org

--- Comment #1 from Robin Berjon <robin@w3.org> ---
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: none
Rationale:
The text is correct, you may put @accesskey on any HTML element - it's valid
content. But it won't always do something, as indicated a little bit below that
text:

"""
When the user presses the key combination corresponding to the assigned access
key for an element, if the element defines a command, the command's Hidden
State facet is false (visible), the command's Disabled State facet is also
false (enabled), the element is in a Document that has an associated browsing
context, and neither the element nor any of its ancestors has a hidden
attribute specified, then the user agent must trigger the Action of the
command.
"""

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 11 June 2013 10:57:11 UTC