[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:  reopened
 Priority:  normal                               |   Milestone:  Future
Component:  Media                                |  Release
 Severity:  normal                               |     Version:  3.5.1
 Keywords:  has-patch needs-testing needs-       |  Resolution:
  refresh                                        |     Focuses:
                                                 |  accessibility
-------------------------------------------------+-------------------------

Comment (by sharonaustin):

 By way of follow-up to the promised review from last week's meeting
 [https://irclogs.wordpress.org/chanlog.php?channel=wordpress-
 ui&day=2014-02-19&sort=asc#m159871]and Graham Armfield's recommendation to
 try using NVDA 2013.3, I again tested on a 3.8.1 test site, on a Windows
 machine, going out of my way to test on Firefox, which has had known
 issues.

 Using NVDA 2013.3 in browse mode, I found no accessibility blockers, even
 in the rich text area using Firefox.  Version 2013.3 included a new fix
 that allowed me to escape out of keyboard traps. (Shift+)

 From the "What's new" file in NVDA. In browse mode documents (Internet
 Explorer, Firefox, etc.), you can now jump to the start and past the end
 of certain containing elements (such as lists and tables) with shift+, and
 , respectively. (#123) [http://community.nvda-project.org/ticket/123]

 Bottom line, I found absolutely no blockers because of WordPress, at least
 when using NVDA 2013.3.   Some accessibility blockers (keyboard traps)
 still exist with 2013.1, but even those disappear with testing in my 3.9
 test site, I assume because of the upgraded TinyMCE.

 The only problems I REALLY had is that NVDA 2013.3 kept crashing my
 station; for that reason, I did not test on Rian's site, I tested my own.
 It was all I could do to make it through a complete session.  2013.3 is in
 beta (as I understand it) so I expect even those "bugs" to be worked out
 soon.  But again, I found no issues because of WordPress.

 To all the developers, thank you so much for what you've done here.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/23560#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform