WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #23560, comment 47


Ignore:
Timestamp:
02/26/2014 01:43:00 PM (6 years ago)
Author:
sharonaustin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23560, comment 47

    initial v1  
    1 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.
    2 
    3 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+)
    4 
    5 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]
    6 
    7 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.
    8 
    9 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.
    10 
    11 To all the developers, thank you so much for what you've done here.
     1Sorry, another relevant link to above:
     2[http://community.nvda-project.org/ticket/3145]