[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:  has-patch      |
---------------------------+------------------------

Comment (by grahamarmfield):

 Testing the Theme Customizer using Dragon Naturally Speaking 12 - with
 Firefox 12 and IE9 on Windows 7 machine:

 '''Firefox'''
 It's possible to navigate with Dragon to most places in the WP admin -
 including the Themes page. Then I can say "Click Customize" and I'm into
 the Theme Customizer. Unfortunately using spoken commands won't achieve
 much after that - it seems that Dragon is not really conscious of the
 opened panel. All commands such as "Click Header Image" which should open
 the Header Image panel yield either nothing, or unexpected results. It is
 possible to use the move mouse commands in Dragon as well as the mouse
 grid, but this is quite laborious when you'd expect the normal speech
 commends to work.

 One unfortunate by-product of having a button labelled Close is that when
 the Dragon user says "Click Close" that is the default command to close
 the browser window, and that is what happens.

 '''IE9'''
 The same situation as with Firefox. Dragon is obviously still conscious of
 all the links beneath the panel as stating "Click Header Image" actually
 closes the Customizer and takes user to Custom Header page under
 Appearance.

 I'm afraid I'm not an expert in how Dragon works so I've no insight into
 why it doesn't recognise the clickable H3s - perhaps because they are not
 actually links maybe? Once the panels are open it also doesn't recognise
 the labels for the controls either. That might be down to the implicit
 linking of the labels with the input fields rather than explicit.

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