blind/disabled people to use an application. I put this small test of Atlas
together for a blind friend of mine to test. It is at
http://216.187.235.116/atlassection508test/. It seems that the applications
runs find and he is able to see/hear the content using JAWS
(www.freedomscientific.com). So, the question is, what's the cause of the
accessibility discussion with Atlas? What are the issues? I hear
discussion but not statement of the issues.
Wally
--
Wallace B. McClure
"The Harder I Work, the Luckier I Get."
Listen to "The ASP.NET Podcast" at http://www.aspnetpodcast.com/
Database Award: http://url123.com/vc3er
Microsoft MVP - Visual Developer ASP/ASP.NET
AspInsider
"AJAX for ASP.NET" Coming Soon!
ADO.NET Book: http://url123.com/vc2bu
865-693-3004
118 Durwood Rd.
Knoxville, TN 37922
http://www.scalabledevelopment.com/
Blog: http://weblogs.asp.net/wallym/Oops, I missed Bertrand's post on the subject. Thanks.
Wally
wrote in message news:1155492@.66.129.67.202...
> When people talk about Accessibility, I think of Section 508 and allowing
> blind/disabled people to use an application. I put this small test of
> Atlas
> together for a blind friend of mine to test. It is at
> http://216.187.235.116/atlassection508test/. It seems that the
> applications
> runs find and he is able to see/hear the content using JAWS
> (www.freedomscientific.com). So, the question is, what's the cause of the
> accessibility discussion with Atlas? What are the issues? I hear
> discussion but not statement of the issues.
>
> Wally
>
> --
> Wallace B. McClure
> "The Harder I Work, the Luckier I Get."
> Listen to "The ASP.NET Podcast" at http://www.aspnetpodcast.com/
> Database Award: http://url123.com/vc3er
> Microsoft MVP - Visual Developer ASP/ASP.NET
> AspInsider
> "AJAX for ASP.NET" Coming Soon!
> ADO.NET Book: http://url123.com/vc2bu
> 865-693-3004
> 118 Durwood Rd.
> Knoxville, TN 37922
> http://www.scalabledevelopment.com/
> Blog: http://weblogs.asp.net/wallym/
>
No comments:
Post a Comment