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

[WordPress Trac]

#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):

 Replying to [comment:19 joedolson]:
 > Tabbing directly from the title field to the content field doesn't just
 save a few clicks; it can actually save literally dozens of tab
 keypresses. If the user is using the HTML editor and has just the basic
 set of quicktags enabled, it's only about a dozen of keypresses; but if
 they're using the visual editor and have additional buttons enabled,
 tabbing through could easily take 40 or 50 additional keypresses.
 That's true for the HTML (Text) editor with quicktags buttons enabled, as
 I said there are 14 key presses in the default configuration. Not true for
 the Visual editor because the buttons toolbar is not focusable by default,
 it's completely skipped and to give focus to that toolbar you have to
 press Alt + F10 once you're in the TinyMCE editing area. As far as I know
 that's the only way to give focus to the TinyMCE buttons toolbar, unless
 I'm missing something. Thus, in a default configuration there would be
 just 5 key presses and making the toggle tabs focusable there would be 7
 key presses.

 > ... we need a better solution
 There was a project aimed to review this area
 https://make.wordpress.org/ui/tag/ceux/ but it's been put "on hold" and
 it's currently inactive. I noticed some interesting ideas there.
 I tend to think that moving focus without informing users '''why''' and
 '''where''' the focus is moved and '''what has been skipped''' it's
 usually a bad idea. A natural tab order is a better option in most of the
 cases and if there are problems, they usually come from a
 [http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140902/G59 lack of a
 logical sequence in the markup]. CEUX project noticed this and you can see
 in some mockups attached in the project page they proposed to unify the
 Title field and the editor, removing anything in between.

 > There's already a keyboard trigger for entering the toolbar for the
 visual editor, it would be helpful if that also worked to enter the
 toolbar in HTML mode.
 I agree the "tabbing experience" in the Visual and Text editors should
 match as much as possible. Not sure forcing the quicktags toolbar out of
 the natural tab order would be the right solution. Giving the option of
 skipping as proposed by @sharonaustin would be probably a better choice.

 > However, this should really be raised as a separate ticket; it's well
 out of scope for this ticket.
 I agree. Will create a new ticket depending on the feedback received by
 the a11y mailing list group.

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