13737 2011-08-10 03:40:25 +0000 the menu element and accessibility 2016-04-14 14:11:58 +0000 1 1 1 Unclassified HTML WG HTML a11y Task Force unspecified PC All RESOLVED INVALID http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov a11y P2 normal --- 13590 1 mike contributor chaals ian jackalmage laura.lee.carlson lwatson mike mjl000 public-html-a11y public-html-admin public-html-wg-issue-tracking dave.null oldest_to_newest 54574 0 mike 2011-08-10 03:40:25 +0000 http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov The Menu Element Although there is great potential usefulness in the menu element, a lot of careful work will need to be done to assure that the variety of children, options, list items, command elements, etc., it can support are consistently accessible to users with disabilities across all available browsers. [split out from bug 13590] 54597 1 jackalmage 2011-08-10 14:46:37 +0000 Yes, browsers will have to do thing correctly. Is there any problem with the HTML spec in this regard? 60236 2 mike 2011-11-20 18:16:15 +0000 This bug is waiting on a response from Mia Lipner or somebody else to to comment #1 > Yes, browsers will have to do thing correctly. Is there any problem with the > HTML spec in this regard? 60314 3 mike 2011-11-21 22:25:57 +0000 Sent MIa a message asking her to follow up here - http://lists.w3.org/Archives/Public/public-html-comments/2011Nov/0060.html 60358 4 mjl000 2011-11-22 23:29:52 +0000 At the time of writing my comments, I didn't see anything necessarily wrong with the HTML specification for the menu element. My comment was meant more as a caveat that even if an element is appropriately defined in the markup language specification that that is no guarantee that its accessibility will be supported in user agents. (So it was more a place to link issues for the User Agent Guidelines, I suppose.) I haven't kept close tabs on changes, so I don't know if there have been any issues raised with the menu element. If there have been, my above comment should not be an indication that I agree or disagree with others' comments. I apologize for any confusion. 60361 5 mike 2011-11-23 03:26:33 +0000 Mia, In reply to comment #4: Thanks for your comment. No problem about confusion -- we just needed to follow up on this to see if any further action might be required from the editor in response at this point. Based on your comment, it seems like there is not, so this bug will likely be moved to "resolved" status soon. The record for it here will remain of course. 60855 6 ian 2011-12-02 21:07:58 +0000 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: see comment 5 108378 7 lwatson 2014-06-26 11:32:16 +0000 Moved to HTML A11y TF component. 125845 8 chaals 2016-04-14 14:11:58 +0000 If there are specific problems, please file them as specific issues at http://github.com/w3c/html/issues