- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 12 Jul 2000 13:21:34 -0400 (EDT)
- To: Jon Gunderson <jongund@uiuc.edu>
- cc: Kitch Barnicle <barnicle@trace.wisc.edu>, w3c-wai-ua@w3.org
And it depends VERY much on the user paradigm. I use up arrow and down arrow to move forward or backward through links, and that seems pretty intuitive to me... Charles McCN On Wed, 12 Jul 2000, Jon Gunderson wrote: Kitch, Remember this is a list of functions the user can configure for one step/command access. The default keyboard configuration can and should use system conventions (i.e. the windows convention you suggest). Jon At 11:53 AM 7/12/2000 -0500, Kitch Barnicle wrote: >Jon, > >Thanks for the refined list. Recently Mark and I had a brief discussion >about using single keystroke commands to move back, for example back to >the previous element or link. Since, shift plus a key, is pretty much a >convention for reversing we wondered if having a single keystroke command >would be problematic. For example, currently shift + tab is used to move >back a link. If a user agent offers a single keystroke for that same >function would it confuse users more than help them. > >Just a thought for discussion. > >Kitch > >At 12:30 PM 7/11/00 , Jon Gunderson wrote: >>These are refinements and additions to the minimum functions proposed by >>Kitch[1] for single command functions. >> >>For hypertext documents: >>1. Move focus to next active element >>2. Move focus to previous active element >>3. Select link >>4. Change state of control with focus (checkbox, radio group) >>5. Move to previous resource in history list (back function) >>6. Move to next resource in history list (forward function) >>7. Refresh current resource >>8. Move next piece of content into the current viewport (Page Down) >>9. Move previous piece of content into the current viewport (Page Up) >>10. Move next line of content into the current viewport (Down Arrow) >>11. Move previous line of content into the current viewport (Down Arrow) >>12. Search for text >>13. Search again for same text >>14. Stop loading resource >>15. Go to history list >>16. Add current resource to favorites list >>17. Go to favorites list >>18. Increase font size >>19 Decrease font size >>20. Open new resource >> >>For multi-media: >>1. Start playing >>2. Stop playing >>3. Fast forward >>4. Rewind >>5. Pause >>6. Increase volume >>7. Decrease volume >> >> >>[1] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0525.html >>Jon Gunderson, Ph.D., ATP >>Coordinator of Assistive Communication and Information Technology >>Division of Rehabilitation - Education Services >>MC-574 >>College of Applied Life Studies >>University of Illinois at Urbana/Champaign >>1207 S. Oak Street, Champaign, IL 61820 >> >>Voice: (217) 244-5870 >>Fax: (217) 333-0248 >> >>E-mail: jongund@uiuc.edu >> >>WWW: http://www.staff.uiuc.edu/~jongund >>WWW: http://www.w3.org/wai/ua Jon Gunderson, Ph.D., ATP Coordinator of Assistive Communication and Information Technology Division of Rehabilitation - Education Services MC-574 College of Applied Life Studies University of Illinois at Urbana/Champaign 1207 S. Oak Street, Champaign, IL 61820 Voice: (217) 244-5870 Fax: (217) 333-0248 E-mail: jongund@uiuc.edu WWW: http://www.staff.uiuc.edu/~jongund WWW: http://www.w3.org/wai/ua -- Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 Postal: GPO Box 2476V, Melbourne 3001, Australia
Received on Wednesday, 12 July 2000 13:22:11 UTC