[wp-trac] [WordPress Trac] #34957: #a11y-focus: Standardizing the handling of :focus and :hover

[WordPress Trac]

#34957: #a11y-focus: Standardizing the handling of :focus and :hover
-------------------------------+-----------------------------
 Reporter:  adamsoucie         |      Owner:
     Type:  enhancement        |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Administration     |    Version:  trunk
 Severity:  normal             |   Keywords:
  Focuses:  ui, accessibility  |
-------------------------------+-----------------------------
 After the discussion of [ticket:34876] with @mor10 and @michaelarestad,
 we've realized there are two main cases:
 * Times when the :focus and :hover states can be the same
 * Times when they need to be different

 In order to tackle the general :focus problem we'll need to:
 1. Define which elements fall into which category
 1. Establish a standard implementation for each category
 1. Implement the new standards

 This could quickly evolve into a larger project, but we want to start
 resolve the :focus/:hover to make sure that gets addressed.  This ticket
 is intended to start the conversation and put the attention on :focus.

 This is an important a11y issue, as [ticket:34876] shows there are still
 elements that lack a :focus state completely.  As part of this plan, we'll
 identify those elements lacking :focus and address both the lack of :focus
 and the correct implementation at the same time.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34957>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform