W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2002

RE: Browser Issues

From: RUST Randal <RRust@COVANSYS.com>
Date: Tue, 26 Feb 2002 08:01:33 -0500
Message-ID: <37925254B67DD311876C009027B0FF9201D3A95E@cbscolex01.cbsinc.com>
To: "'Joe Clark'" <joeclark@joeclark.org>, "WAI (E-mail)" <w3c-wai-ig@w3.org>
Joe, 

First off, thanks for your response.  I spent a lot of time on your web site
today.  The resources are exceptional.  You might want to note that the
State of Illinois has also adopted some accessibility guidelines.  The URL
for them is:

http://www.state.il.us/tech/accessibility/IWASfinal11_91.pdf

Now, on to the "browser issues."

You asked if you made the comment about sites being accessible regardless of
the user's browser.  No, it wasn't on your site, it came from Tom
Worthington's site.  He references the WCAG 1.0, which lists an older
browser as an accessibility issue.

You also said:

>The honest answer is "The requirement to be able to run without 
>JavaScript is outdated and has been superseded by the simple fact 
>that every screen reader save for OutSpoken for Macintosh sits on top 
>of IE and uses IE's own renderings, JavaScript included."

Which makes me breathe a sigh of relief.  I know that there are accessible
ways to use Javascript, but I have very little experience with screen
readers.  I also agree that the requirement is outdated.  Just like "text
only" versions of web sites.

And yes, I did read the article at http://contenu.nu/socog.html, but
suprisingly, I have never read your ALA article.  I thought I had read
everything on that site, but it seems that's not the case.

Thanks for your honest answers!

Randal
Received on Tuesday, 26 February 2002 07:58:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:00 GMT