- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Thu, 9 Sep 2004 12:43:13 -0500
- To: <tina@greytower.net>, <w3c-wai-ig@w3.org>
Tina Holmboe wrote: <blockquote> On 9 Sep, david poehlman wrote: > actually, assistive technologies can obtain info from markup and if > judicious use of headings and other mark up is used, this becomes > trivial. It does ? Exactly how would you suggest that, programmatically, an UA-AT should differ between a list of links (happens to be a menu) and a list of links (these are my best friend's pages actually) ? </blockquote> On the University of Texas at Austin's Library site, headings identify groups of links; the links are presented under the headings as unordered lists. The JAWS screen reader allows me to jump from heading to heading (or to get a list of all the headings on the page) and/or to jump from list to list using single keystrokes. I can jump to a heading I want, then tab through the links below it; alternatively, I can jump to a list and start tabbing. The US doesn't differentiate programmatically among the lists, but I do <grin>, and I feel able to get around the page pretty quickly. On the Rampweb home page at http://www.rampweb..com, the navigation bar is also coded as a list; css is used to display the list items horizontally rather than vertically.. There are only five items in the list, but if I want to bypass it I can jump to the first heading on the page, or if I'm already in the list I can hit "d" to jump to a different element. Or I *could* use the skipnav link. John
Received on Thursday, 9 September 2004 17:43:15 UTC