[wp-trac] [WordPress Trac] #21283: Keyboard focus in the theme customizer should be on left options panel

[WordPress Trac]

#21283: Keyboard focus in the theme customizer should be on left options panel
---------------------------+------------------------
 Reporter:  pjad           |       Owner:  lessbloat
     Type:  defect (bug)   |      Status:  reopened
 Priority:  normal         |   Milestone:  3.5
Component:  Accessibility  |     Version:  3.4.1
 Severity:  major          |  Resolution:
 Keywords:                 |
---------------------------+------------------------

Comment (by grahamarmfield):

 Replying to [comment:67 koopersmith]:
 > 2) We could track the link that was used to open the customizer in
 customize-loader and restore focus on close.
 >
 That would be good.

 > 3) This was the biggest thing during the accessibility testing nacin and
 I saw — Dragon picks up everything on the page, and inserts its labels
 *below* the customizer on the page. Honestly, the best solution is
 probably to bump to customize.php if they're using dragon. That said, I
 have no idea how to detect Dragon.
 >
 I'd doubt that it's possible on the browser to detect that Dragon is
 running, and I also doubt that there's be anything in the HTML headers. I
 could be wrong though so it'd be worth having a look. Many people have
 asked the same question about screen readers such as NVDA and JAWS but no-
 one has come up with a robust solution.
 > ----
 >
 > At the end of the day, I think fixing the second point (link tracking)
 the best we're going to do for 3.5. The other two aren't really feasible
 at this point.
 I acknowledge that the cut-off for 3.5 must be very close. I'm a
 pragmatist, and believe that retrofitting accessibility to something
 complex like the WP admin screens is always going to be done by a series
 of steps in the right direction - rather than all at once.

 That said, the scope of the a11y changes in 3.5 is impressive and I hope
 the pace can continue in 3.6.

 If there's going to be a 'ground-up' rebuild of WP UI (for WP4 maybe) then
 there is a golden opportunity to bake all the accessibility in from the
 start.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21283#comment:68>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software