[wp-trac] [WordPress Trac] #31575: Press This: post options toggle accessibility improvements

WordPress Trac noreply at wordpress.org
Fri Mar 27 14:55:10 UTC 2015

#31575: Press This: post options toggle accessibility improvements
 Reporter:  afercia           |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Press This        |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch dev-    |     Focuses:  ui, accessibility, javascript
  feedback                    |

Comment (by afercia):

 Things have changed a bit now that the Post Options panel automatically
 closes when it loses focus but still there are issues I would recommend to
 take into consideration. Using a screen reader you can do things you
 usually can't with just a browser. For example, you can leave focus "in
 place" and make the screen reader read out other parts of the screen.
 - Tab to the Post Options button, press Enter, the panel opens and focus
 is moved to the panel
 - do your things in the panel
 - now you can keep focus on the panel (it will still be open) and explore
 other parts of the page, for example you can make the screen reader start
 reading out from the beginning of the page
 - you stop on the Post Options button which now says just "Done", you have
 no idea what "Done" refers to
 - activate the button, the button "disappears" and at this point there's a
 focus loss, which is one of the most annoying things for screen reader

 This is the main reason why there should be just one button: focus would
 still be on the button, then we should make the button change state and
 I would still recommend to have just one button, if possible :)

 > two buttons to control open/close is pretty standard
 I'm not sure in WordPress there are two buttons for close/open in any
 place, but I may be wrong. Worth noting that in Press This itself, the
 "Add Category" button is just one "toggle" button and maybe having 2
 different design paradigms in the same interface is not the best choice?

 About the JS part, I just tried to make it work :) happy to see different,
 better, simpler, implementations :)

Ticket URL: <https://core.trac.wordpress.org/ticket/31575#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list