[wp-trac] [WordPress Trac] #27553: Make WP editor toggle focusable

WordPress Trac noreply at wordpress.org
Fri Sep 26 14:56:41 UTC 2014


#27553: Make WP editor toggle focusable
--------------------------+-----------------------------
 Reporter:  joedolson     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Editor        |     Version:  3.3
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  accessibility
--------------------------+-----------------------------

Comment (by afercia):

 In `/wp-admin/js/post.js` there's some code commented with "This code is
 meant to allow tabbing from Title to Post content" which basically does
 one thing:
 when you're in the "Title" field and then you tab forwards, focus is moved
 directly inside the editor area, whether it's TinyMCE or the Text editor,
 skipping all what's in between the "Title" field and the editor.

 While this *may* be useful for sighted keyboard users (they save a few key
 presses, say 1 second?), it's a very critical experience for screen reader
 users: when they tab forwards, they get that right after the title there's
 the editor. But when they tab backwards, they get many more elements that
 "weren't there before".

 Moreover, TinyMCE and the Text editor differ in the number of focusable
 elements you have to tab through while tabbing backwards from the editor
 to the "Add media" button:
 - with TinyMCE you have to press Shift + Tab just once
 - with the Text editor you have to press Shift + Tab 14 times to skip all
 the quicktags buttons and the "toggle fullscreen" button

 No information is provided anywhere to screen reader users about this
 difference. Plugins and themes may add additional buttons too.

 I guess this is one of the most confusing and frustrating experiences for
 screen reader users. Quoting a post by @sharonaustin will help to
 understand this far better than trying to explain with my poor English:
  We don’t know why this happens.
  ...
  Certain elements aren’t available by keyboard when tabbing forward, and
 by extension, aren’t available to assistive technology – the strange thing
 is, they’re accessible if you tab backwards….WHY?
 [http://reddhoundhowling.wordpress.com/]

 Attached patch is for testing purposes and it just removes the javascript
 part responsible for moving the focus, thus restoring a natural tab flow
 and order.
 It would be really helpful to have as much people as possible testing
 this, especially accessibility experts and users.
 Any feedback more than welcome.

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


More information about the wp-trac mailing list