[wp-trac] [WordPress Trac] #28209: Links inside help tabs (help-tab-content) are not keyboard accessible

WordPress Trac noreply at wordpress.org
Fri May 23 11:49:43 UTC 2014


#28209: Links inside help tabs (help-tab-content) are not keyboard accessible
----------------------------+------------------------------
 Reporter:  rianrietveld    |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  accessibility
----------------------------+------------------------------

Comment (by GrahamArmfield):

 Replying to [comment:4 neil_pie]:
 > I absolutely agree that the tab order is jarring. One would expect to
 tab from left to right through the tab-list, then the tab-panel, then the
 sidebar. As Joe states, this is a separate issue.
 >
 > I personally disagree that activating tab-panels on keyboard focus is
 correct/desired behaviour. I'm basing this on the WAI-ARIA best practices
 at http://www.w3.org/TR/2009/WD-wai-aria-practices-20090224/#tabpanel
 >     '''tab:''' the label/title area of the tab panel. This is where you
 click to activate a tab panel
 >     When the user activates a tab, the contents of that tab is made
 visible ... The active tab is placed into the tab order.
 > The key word to me there is 'click'. In other contexts this would
 indicate a press of the spacebar or enter key. Am I misinterpreting this
 or should it not be applied in this case?
 >
 > Also, isn't the alternative to force the user to tab through all the
 links in a tab-panel before keyboard focus is moved to the next tab in a
 tab-list? This feels like a worse User Experience to me, or is there
 another solution that I'm missing?

 Coincidentally I've been researching this for a client site I've just
 started working on. I'm basing my tabs on the ideas set out in these two
 resources: http://www.marcozehe.de/2013/02/02/advanced-aria-tip-1-tabs-in-
 web-apps/ and http://www.deque.com/blog/building-accessible-tab-panel-
 aria/

 The thrust of the articles is that tabbing around a page will eventually
 bring you to a tab panel grouping. Focus should go to whichever tab is
 currently active. As long as all the ARIA is in place screen readers will
 be notified they are in a tab list.

 The convention is to use the left/right arrow keys to move amongst the
 tabs. But actioning the tabs is carried out using the space bar (or Enter
 key) when the person has found a tab they are interested in. When they
 action a tab then focus is to be transferred into the first item within
 the corresponding tab panel (or the panel itself), and the corresponding
 tab panel will become visible. Further tabbing will visit any links within
 the tab and then move off the tab panel onto the rest of the page.

 Note that not all of the actual tabs are part of the tab order of the page
 - only the currently selected one.

 I think all this agrees with the page you have referenced Neil.

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


More information about the wp-trac mailing list