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 menu example includes scripting that causes a change of context [1] when the select element is changed: <select id="goto" onchange="if (this.options[this.selectedIndex].value) window.location = this.options[this.selectedIndex].value"> This is a violation of WCAG 2.0 3.2.2 [2]: Changing the setting of any user interface component does not automatically cause a change of context. Suggest removing the onchange event handler from this example. [1] http://www.w3.org/TR/2008/REC-WCAG20-20081211/#context-changedef [2] http://www.w3.org/TR/2008/REC-WCAG20-20081211/#consistent-behavior-unpredictable-change
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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r4663. Check-in comment: Comment out the onchange='' handler since it's poor practice. http://html5.org/tools/web-apps-tracker?from=4662&to=4663
Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future.