> Probably even more off-topic than a discussion of browsers: a screen > reader isn't a browser at all.
Of course, I never intended for this to be a discussion of various screen readers, but of whether creating aural cascading style sheets (ACSS) held value for those who use screen readers. As a few have pointed out, when ACSS are created by a sighted person with no experience in using screen readers, one could make the browser experience more frustrating rather than less. I've read that the downloadable free trial of JAWS is applicable for 40 minutes. After that time you must reboot your computer and then can run the program again. This apparently can be done repeatedly. This product can be found here: http://www.freedomscientific.com/fs_products/software_jaws.asp For the moment I'll be focusing on following the W3C guidelines as much as possible with a primary focus on adding keyboard accessibility, skip navigation links, etc. For those who are interested, I found the following site to have the most complete information on making your pages accessible: http://www.webaim.org/. Thanks to all for your feedback, Denise ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
