Again, referring specifically to screen reader users, my anecdotal experience supporting several users who are blind in my job is that Rahul is most of the time correct. Good structured code and Standards Based Design with proper lists, headings, and code that's not abused is more useful to these users than the ever popular "Skip to Content."
However, (there's always a "however") we cannot forget about our users who are sighted, or as my colleague says "light dependent," and cannot or should not use a mouse. Many folks with mobility impairments navigate using the TAB key and Enter. They do benefit from VISIBLE Skip Links to speed their navigation. For these folks, it's not so much about reading the information or finding a section of content, it's about getting to an interface element and activating it or some such. Skip Links can save them several whacks on the TAB key on their way to their goal. Just my 2 yen on the topic. Christopher M. Kelly, Sr. (GM22) State Farm Insurance Companies Accessible Technology Services & Support (ATSS) phone: 309-763-7069 email: [EMAIL PROTECTED] "[Web] Access is not about adding wheelchair ramps to existing pages. It's about getting your page right in the first place. This medium was designed to be accessible. If your work isn't accessible, you're doing it wrong..." - Owen Briggs, Web and CSS guru, http://www.thenoodleincident.com "However bad life may seem, there is always something you can do and succeed at. While there is life, there is hope." - Stephen Hawking -----Original Message----- <deleted for space> ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
