[wp-trac] [WordPress Trac] #43351: Themes page: consider to improve the hover and focus styling (was: Hover effect issue on themes.php page)

WordPress Trac noreply at wordpress.org
Tue Feb 20 17:01:35 UTC 2018


#43351: Themes page: consider to improve the hover and focus styling
-----------------------------+--------------------------------
 Reporter:  anilhada         |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  ui, accessibility
-----------------------------+--------------------------------
Changes (by afercia):

 * focuses:  ui, javascript, administration => ui, accessibility
 * component:  General => Themes
 * version:  4.9.4 =>
 * keywords:   => has-screenshots
 * type:  defect (bug) => enhancement


Comment:

 @anilhada thanks for your report. This behavior is by design and it's an
 accessibility feature. When closing a modal, it's important for keyboard
 users to move focus back to the control that originally opened the modal.

 So, when you close the modal, focus is set back to the first "theme
 details" and what you see is the `focus` style (which in this case is
 almost the same of the `hover` style). The first "theme details" is still
 focused when you hover with the mouse on the second "theme details", so
 two overlays are visible at the same time.

 There's a subtle styling difference: the first one (the focused one) has a
 blue box-shadow while the second one (the hovered one) hasn't.

 Worth noting this is a standard behavior for other controls too (links,
 buttons), where it is possible, for example, to have a button still
 "focused" while hovering on another button.

 Considering that focus must be moved back for accessibility reasons, the
 only improvement I can think of would be trying to differentiate a bit
 more the `focus` and `hover` styles. If you don't mind, I'd change this
 ticket to a proposed enhancement, and I'd update the ticket title to
 better describe the issue.

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


More information about the wp-trac mailing list