- From: Jon Gunderson <jongund@uiuc.edu>
- Date: Mon, 04 Nov 2002 10:31:45 -0600
- To: "Ian B. Jacobs" <ij@w3.org>
- Cc: Steven Pemberton <steven.pemberton@cwi.nl>, wai-xtech@w3.org, voyager-issues@mn.aptest.com, ij@w3.org
At 10:24 AM 11/1/2002 -0500, Ian B. Jacobs wrote: > For direct access with intent to activate, I don't > think the "focus only" option is very interesting: the user > would generally only use those accesskeys once the binding > between key and task is known. In this case, there is no > longer a need for orientation, and the user is unlikely to > want to focus first then activate. I also note that the user > is unlikely to want to discover available accesskeys by randomly > testing key combinations; the focus-but-don't-activate should > not be taken as a mechanism for allowing binding discovery > (see instead UAAG 1.0 checkpoint 11.2). I disagree it is often useful for some one to move the focus to a navigation bar and then select something else from the navigation bar. But getting the focus near a target is useful. Remember access keys for form controls move focus to those controls, so for links there would be consistency with form controls. For people with visual impairments it is often difficult for them to understand the difference between a button and a link, since they do no see the graphical styling. Jon 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
Received on Monday, 4 November 2002 11:31:21 UTC