This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The accesskey on the <command> element provides nearly all the features of the XHTML access module, but missing role-based navigation. See the access key requirements for more information: http://esw.w3.org/topic/PF/XTech/HTML5/AccesskeyRequirements#head-f89f1a568780ea2fbe40a5995b02e3d36073cb47
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
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: Did Not Understand Request Change Description: no spec change Rationale: accesskey="" on <command> is the same as on any other element. I don't understand what is special about <command> here. Could you elaborate? If you could paste the relevant parts of the cited document that would be great, I read through it but couldn't work out the relevance to <command>. The summary of this bug doesn't mention <command>, just "role-based navigation". Is this a separate issue? Is the request here to add role-based navigation to HTML, independent of <command>?
http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq8 Assign to Gregory Rosmaita to work with Cynthia Shelly. This is related to an upcoming command discussion in the mapping group but is not assigned to that group.
the command element is no longer in HTML, so closing.