- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 23 Feb 2010 07:02:38 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8738
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |NEEDSINFO
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-02-23 07:02:38 ---
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>?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 23 February 2010 07:02:46 UTC