8681 2010-01-08 10:29:38 +0000 Separator menu items 2010-10-04 14:46:19 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT VERIFIED WONTFIX http://www.w3.org/TR/html5/interactive-elements.html#building-menus-and-tool-bars a11y, a11ytf P2 normal --- 1 gez.lemon ian ian mike public-html-a11y public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 30757 0 gez.lemon 2010-01-08 10:29:38 +0000 The spec says: An option element that has a value attribute set to the empty string, and has a disabled attribute, and whose textContent consists of a string of one or more hyphens (U+002D HYPHEN-MINUS) will append a separator to the menu. As hr is supported, why is the special example required? 31535 1 ian 2010-02-05 23:03:50 +0000 This is intended to make it easy to port current <select> "menus" to <menu> without changing the menu code. Also, you can't put an <hr> in a <select>. 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: no spec change Rationale: no spec change suggested 31757 2 cooper 2010-02-11 17:01:07 +0000 HTML A11Y TF plans to provide further information to support this issue. 39007 3 w3c 2010-09-14 15:45:21 +0000 The specification says that an option with an empty value, disabled state and one or more hyphens as text creates a seperator node. Since the option is disabled it will not effect screen readers and is purely presentational. The HTML Accessibility TF Bug Triage Sub-team does not consider this as an accessibility issue and proposes to close the bug.