ello,
I have a question regarding the general navigation strategy for web based
applications with JAWS:
or normal web sites, the virtual pc cursor (arrow key navigation for the
whole page and tab key navigation for interactive elements) works fine. But,
for web applications which have a very fat front end and a lot of UI
elements on screens, this does not work as well (since the users have to
switch between cursors a lot). So, in the case of web application, is it a
good idea to have everything on the screen (including descriptive text) be
tabbed to with the virtual pc cursor turned off?. This would mean including
all the elements on the screen, including text, in the TABINDEX.
I haven't done any end user testing with this navigation strategy and wanted
an outside opinion on the issue. The clear advantage of the "All Tab"
strategy is that it requires minimal training and there is no switching of
cursors for navigation (this will be faster and will induce less mental
workload for the users). The disadvantage is that this strategy is not
consistent with how visually impaired users navigate web based material.
I'll greatly appreciate any feedback on this issue.
Regards,
Manik.


VICUG-L is the Visually Impaired Computer User Group List.
To join or leave the list, send a message to
[log in to unmask]  In the body of the message, simply type
"subscribe vicug-l" or "unsubscribe vicug-l" without the quotations.
 VICUG-L is archived on the World Wide Web at
http://maelstrom.stjohns.edu/archives/vicug-l.html