[wp-trac] [WordPress Trac] #40738: Customizer: Additional CSS

[WordPress Trac]

#40738: Customizer: Additional CSS
-------------------------------+--------------------------------------
 Reporter:  mizejewski         |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Customize          |     Version:  4.7
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui, accessibility, docs
-------------------------------+--------------------------------------

Comment (by joedolson):

 It's a difficult issue to convey, but I'm not sure there's an easy way to
 reduce that text. The issue is that the normal mode of moving from one
 field to the next when using a screen reader or a keyboard is to hit
 'Tab'. Since the 'Tab' key is needed in the CSS editor to enter the tab
 character, it can't be used for navigation. There isn't any standard for
 how to navigate using an alternate key, so we need to be able to explain
 how somebody can get out of the CSS editor if they need to use a keyboard.

 On reading the text several times, I think it's going to be unclear for
 non-keyboard dependent users because they won't understand why it's
 needed, so they would need sufficient background information to understand
 that this instruction is not pertinent to their usage. However, it's
 perfectly clear for somebody who is keyboard dependent and needs the
 instruction.

 One thing I'd suggest as a possibility is if each panel had an optional
 toggle to enable notes on keyboard functions if they are available. This
 would have three advantages that I can see:

 1) The keyboard notes wouldn't be visible by default, so would make the
 default design and layout cleaner.
 2) There would be a system in place for communicating any needed keyboard-
 specific information (such as shortcuts) that were relevant to a specific
 panel. This would constitute context-specific help, so people wouldn't
 generally need to comb through a large quantity of information to find
 what was relevant to them.
 3) Because the keyboard information toggle would itself be a tab stop,
 somebody who needs keyboard information would have the presence of
 additional keyboard information brought to their attention while
 navigating. Right now, it's only available while reading. While this is a
 minor distinction, if somebody was navigating quickly using a screen
 reader, it would be easy to tab into the CSS editor without having read
 the instructions on how to escape it.

 Any way, those are some thoughts on this.

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