W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2004

Re: Comments on Mozilla content keyboard navigation proposal

From: Susan Crayne <crayne@us.ibm.com>
Date: Fri, 17 Sep 2004 09:45:34 -0400
To: Jon Gunderson <jongund@uiuc.edu>
Cc: Catherine Laws <claws@us.ibm.com>, mozilla-accessibility@mozilla.org, Peter Korn <Peter.Korn@Sun.COM>, w3c-wai-ua@w3.org, w3c-wai-ua-request@w3.org
Message-ID: <OFFA7F7A21.FC2EB80C-ON85256F12.004AD5BD@us.ibm.com>

I think it's a good idea to provide both Element and Visual Line
navigation.  Some people who use the keyboard rather than the mouse will do
so not because they are blind but because they have motor issues which
prevent them from using the mouse.  These people might very well prefer the
Visual Line navigation.  In addition, there is a large population with
visual impairments short of blindness.  Some of them might be able to see
text but not be able to see the mouse cursor.  This population might also
prefer the Visual Line navigation.


Accessibility Research
IBM T.J. Watson Research Center
19 Skyline Drive, Hawthorne, NY  10532  USA


                      Jon Gunderson                                                                                                    
                      <jongund@uiuc.edu        To:       Peter Korn <Peter.Korn@Sun.COM>, Catherine Laws/Austin/IBM@IBMUS              
                      >                        cc:       mozilla-accessibility@mozilla.org, w3c-wai-ua@w3.org                          
                      Sent by:                 Subject:  Re: Comments on Mozilla content keyboard  navigation proposal                 
                      09/16/2004 10:38                                                                                                 

1. Plug-ins
I like Catherines proposal of treating plug-ins as frame like
objects, and basically ignoring them unless someone uses the
frame command to navigate into the plug-in.

2. HTML Element versus Visual Line Navigation with arrow keys
Some people will not be using screen readers with the "caret"
mode, so jumping between elements maybe confusing to them.  I
suggest having the un modified arrow keys move by line and a
modifier key move between elements like ALT+Down Arrow and
ALT+Up Arrow.

Ideally ALT+Up Arrow and Alt+Down Arrow could be a
configuration option.
1. Do nothing
2. Navigate by elements
3. Navigate headings (H1-H6)
4. Navigate form controls

Users could then choose option they want through a config
setting.  Control+Up and Control+Down arrow could have the
same options.

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
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://cita.rehab.uiuc.edu/
WWW: http://www.staff.uiuc.edu/~jongund
Received on Friday, 17 September 2004 14:00:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:33 UTC