[wp-trac] [WordPress Trac] #24048: Code Editors: Increase the usability of Code Editor's files list

WordPress Trac noreply at wordpress.org
Tue Oct 10 03:19:04 UTC 2017


#24048: Code Editors: Increase the usability of Code Editor's files list
-----------------------------------------------+---------------------------
 Reporter:  Daedalon                           |       Owner:
     Type:  defect (bug)                       |      Status:  new
 Priority:  high                               |   Milestone:  4.9
Component:  Plugins                            |     Version:  3.5.1
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch ui-feedback ux-feedback  |     Focuses:  ui,
                                               |  accessibility
-----------------------------------------------+---------------------------

Comment (by WraithKenny):

 @afercia turns out the issue wasn't with `role="none"` (presentation
 seemed to have no effect that I noticed), but rather that it needed a root
 folder because of the way the w3c library was written. Rather than edit
 their script, I wrapped the files in a ul>li. This changed the design to
 have the folder lines encompass the whole tree, but I think it looks nice.
 (Thoughts on design @melchoyce?)

 Another thing removed was the "nonessential" span that shows the path of
 the file under the filename, as it's redundant with the tree structure. I
 do have a question about the accessibility of it. Would having the path
 read, i.e. `back-compat.php (inc/back-compat.php), list box` add useful
 info, or is it just noise? I figured it'd just be noise, but can add it
 back in if it's desirable.

 The patch is now equivalent in behavior to the w3c demo, as far as I can
 tell.

 I noticed that if a file (as opposed to folder) is the last highlighted
 item (or initial item), Safari won't tab into the tree (but will in
 reverse!)... This is a bug in Safari apparently, because it does it
 without VoiceOver, probably do to its treatment of `li`'s vs `a`'s
 Luckily, besides this issue, Safari/VoiceOver seems to be working as
 expected!

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


More information about the wp-trac mailing list