[wp-trac] [WordPress Trac] #23560: Keyboard Accessibility of Add Media Panel

[WordPress Trac]

#23560: Keyboard Accessibility of Add Media Panel
-------------------------------------+-----------------------------
 Reporter:  grahamarmfield           |       Owner:
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Future Release
Component:  Accessibility            |     Version:  3.5.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |
-------------------------------------+-----------------------------

Comment (by neil_pie):

 There appears to be an issue with the Featured Image view in this patch

 When selecting an image either via keyboard or mouseclick, the focus drops
 from the selected element and onto the Body element. This is a problem for
 users navigating the pane via the keyboard as it means that pressing tab/
 shit+tab does not transfer focus to the next / previous item in the list
 as one would expect.

 Steps to replicate:

 1. Click on 'Add Media' in the edit post screen
 2. Navigate to the 'Set Featured Image' view
 3. Select an image either by tab/space or by mouseclick
 4. Press tab

 This is happening for me in the latest Chrome, Safari and Firefox on OSX
 Mavericks.

 Note that in the two webkit browsers, the bug is far more apparent. This
 is because when the focus returns to the body, pressing tab moves focus
 onto the skiplinks in the main window. When replicating the bug in
 Firefox, pressing tab after selecting an item moves focus to the second
 media item in the list or the next focusable element when there is no
 second media item.

 Some debugging info:

 The focus dropoff happens when the media items collection is destroyed and
 rebuilt in backbone. This disposal doesn't seem to happen in the other two
 views which is why the issue is isolated to Set Featured Image.

 Possible solutions:
 1. Re-apply focus once the collection has been rebuilt
 2. Prevent disposal in the first place if it can be avoided

 I'm not sure which of the above two solutions is preferable or even
 possible, but should I figure it out I'll submit a patch

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