[wp-trac] [WordPress Trac] #23119: UX Improvements to nav-menus.php

[WordPress Trac]

#23119: UX Improvements to nav-menus.php
-----------------------------------------------+------------------
 Reporter:  lessbloat                          |       Owner:
     Type:  enhancement                        |      Status:  new
 Priority:  normal                             |   Milestone:  3.6
Component:  Menus                              |     Version:
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch needs-testing 3.6-menus  |
-----------------------------------------------+------------------

Comment (by grahamarmfield):

 Replying to [comment:206 lessbloat]:
 > grahamarmfield, it seems like the redirect on change would only take
 place upon selection of a select option, not just in browsing the select
 options.  Can you please clarify which is the case for screen readers?

 For most keyboard only users, when encountering a dropdown they would use
 the up and down arrow keys to review the options. This (I believe) fires
 the onchange event whenever a new option is moved to. So hence my comment
 re context change triggered by onchange.

 There is a keystroke combination in Windows that allows the dropdown to be
 opened and the options to be reviewed without firing the onchange event
 until the enter key is pressed. But this keystroke combination is not
 widely known and is therefore likely to be hardly used.

 So if the change of context is not triggered by the onchange event, but
 instead by tabbing away from the dropdown (onblur?) then I guess we're
 into a bit of a grey area.

 The issue with not providing a 'Go' or 'Select' (or whatever) button is
 not just a problem for keyboard and screen reader users. Those using
 speech recognition software also need to be catered for.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23119#comment:207>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software