This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13737 - the menu element and accessibility
Summary: the menu element and accessibility
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y Task Force (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: contributor
QA Contact: This bug has no owner yet - up for the taking
Keywords: a11y
Depends on:
Blocks: 13590
  Show dependency treegraph
Reported: 2011-08-10 03:40 UTC by Michael[tm] Smith
Modified: 2016-04-14 14:11 UTC (History)
10 users (show)

See Also:


Description Michael[tm] Smith 2011-08-10 03:40:25 UTC

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]
Comment 1 Tab Atkins Jr. 2011-08-10 14:46:37 UTC
Yes, browsers will have to do thing correctly.  Is there any problem with the HTML spec in this regard?
Comment 2 Michael[tm] Smith 2011-11-20 18:16:15 UTC
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?
Comment 3 Michael[tm] Smith 2011-11-21 22:25:57 UTC
Sent MIa a message asking her to follow up here -
Comment 4 Mia Lipner 2011-11-22 23:29:52 UTC
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.
Comment 5 Michael[tm] Smith 2011-11-23 03:26:33 UTC
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.
Comment 6 Ian 'Hixie' Hickson 2011-12-02 21:07:58 UTC
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:

Status: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 5
Comment 7 LĂ©onie Watson 2014-06-26 11:32:16 UTC
Moved to HTML A11y TF component.
Comment 8 Charles McCathieNevile 2016-04-14 14:11:58 UTC
If there are specific problems, please file them as specific issues at