- From: Jon Gunderson <jongund@illinois.edu>
- Date: Tue, 18 Nov 2008 15:18:49 -0600 (CST)
- To: Becky Gibson <Becky_Gibson@notesdev.ibm.com>, Jon Gunderson <"jongund <jongund"@illinois.edu>
- Cc: W3C WAI-PFWG <w3c-wai-pf@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
I agree with Becky some of the keyboard shortcuts don't seem natural for a keyboard only user. Should Control+PageUp and Control+PageDown be based on the tabpanel with current focus? Jon ---- Original message ---- >Date: Tue, 18 Nov 2008 11:46:20 -0500 >From: "Becky Gibson" <Becky_Gibson@notesdev.ibm.com> >Subject: Re: Updated accordian example >To: "Jon Gunderson <jongund" <jongund@illinois.edu> >Cc: W3C WAI-PFWG <w3c-wai-pf@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org> > > I think that if an accordion is open, it's title/tab > should be updated to have tabindex=0 and be in the > tab order. This does break the "rule" of only one > item in a component being in the tab order but I > think it makes the most sense for an accordion that > allows multiple tabs to be open. Given an > accordion with 4 panes (as in Jon's example) with > the first pane closed, the second pane open, the > third pane closed and the fourth pane open. If I am > focused on the last item in the open, second pane, > when I press tab I would expect to go to the next > open pane title/tab rather than directly to the > first item in that open pane. I think shift tab is > even more confusing, I go from the first item in the > open fourth pane, directly to the last item in the > open second pane with out stopping at the fourth > pane tab/title. > > Regarding the control-pageup behavior - this seems a > bit broken in John's example. Depending upon which > item has focus in an open pane, there doesn't seem > to be a pattern to which title/pane gets focus when > I press control-pageup or control-pagedown. For > example, load the page and press tab until you reach > Mushrooms in the Vege Option pane which is open on > page load. Press control-pageup -my focus is on the > Delivery Options tab/title rather than the Crust > options. I'm using Firefox 3.0.4 on Windows. > > > Becky Gibson > Web Accessibility Architect > > > IBM Emerging Internet Technologies > 5 Technology Park Drive > Westford, MA 01886 > Voice: 978 399-6101; t/l 333-6101 > Email: gibsonb@us.ibm.com > > wai-xtech-request@w3.org wrote on 11/17/2008 > 05:36:36 PM: > > > From: > > > > Jon Gunderson <jongund@illinois.edu> > > > > To: > > > > W3C WAI-PFWG <w3c-wai-pf@w3.org>, W3C WAI-XTECH > <wai-xtech@w3.org> > > > > Date: > > > > 11/17/2008 06:05 PM > > > > Subject: > > > > Updated accordian example > > > > Sent by: > > > > wai-xtech-request@w3.org > > > > > > > > Updated accordian example > > > http://test.cita.uiuc.edu/aria/tabpanel/tabpanel2.php > > > > I have implemented the following key strokes that > were missing in > > the previous example: > > > > Enter: toggle expanded > > > > Control+PageUp: Move focus to previous tab when > focus is in a tabpanel > > > > Control+PageDown: Move focus to next tab when > focus is in a tabpanel > > > > Control+Up: Move focus to tab associated with the > current tabpanel > > when focus is in the tabpanel > > > > Also tab behavior now is in line with best > practices. Please let me > > know if I missed something or didn't get the > behavoir right. > > > > Jon > > > > Jon Gunderson, Ph.D. > > Coordinator Information Technology Accessibility > > Disability Resources and Educational Services > > > > Rehabilitation Education Center > > Room 86 > > 1207 S. Oak Street > > Champaign, Illinois 61821 > > > > Voice: (217) 244-5870 > > > > WWW: http://www.cita.uiuc.edu/ > > WWW: https://netfiles.uiuc.edu/jongund/www/ > > > > > > Jon Gunderson, Ph.D. Coordinator Information Technology Accessibility Disability Resources and Educational Services Rehabilitation Education Center Room 86 1207 S. Oak Street Champaign, Illinois 61821 Voice: (217) 244-5870 WWW: http://www.cita.uiuc.edu/ WWW: https://netfiles.uiuc.edu/jongund/www/
Received on Tuesday, 18 November 2008 21:19:35 UTC