E-mail List Archives
RE: Accessibility of dotNET
From: Derek Featherstone
Date: Apr 24, 2003 7:27AM
- Next message: Jay Dougherty: "Powerpoint problems"
- Previous message: Benjer: "Re: Accessible menus [another option]"
- Next message in Thread: None
- Previous message in Thread: Cohen, Lisa A.: "Accessibility of dotNET"
- View all messages in this Thread
> My question to this list: Has anyone found information about ASPdotNET
> (regarding how to make it accessible) - other than the very little bit
> offered on the MSDN website?
I can't say that I've really read too much of the MSDN reference material,
however here are some of my observations on what I've seen with ASP.NET:
1. As Joel mentioned, different HTML is delivered to different browsers. If
the user agent is a recent version of IE and client-side error checking is
error checking. This is backed up with server-side checking for alternative
browsers (and presumably IE if JS is off).
2. With ASP.NET, client side checking can be either on or off. When it is
on, the .NET controls auto-generated code that allows for displaying error
messages instantly to the user. These error messages are in
<span>...</span>'s that are hidden from graphical browsers with visibility:
hidden or perhaps display: none. JAWS will read content that is visibility:
hidden, but not display: none. I don't recall if the ASP.NET generated code
uses visibility: hidden or display: none, but it has obvious implications
and testing would be required...
3. The <span>'s contained many attributes that are used to perform the
client-side error checking -- these attributes are not part of HTML, so if
they were to be included, it would appear that a custom DTD would be
required for ensuring that documents validate.
Derek Featherstone <EMAIL REMOVED>
Further Ahead Inc.
toll-free: 1.866.932.4878 (North America)
Web Development: http://www.furtherahead.com
Training and Learning: http://www.completelearning.com
To subscribe, unsubscribe, or view list archives,