E-mail List Archives
RE: Visual Studio.Net 2003 and accessibility
From: Austin, Darrel
Date: Mar 17, 2006 8:30AM
- Next message: Christian Heilmann: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message: Michael R. Burks: "Visual Studio.Net 2003 and accessibility"
- Next message in Thread: Christian Heilmann: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message in Thread: Michael R. Burks: "Visual Studio.Net 2003 and accessibility"
- View all messages in this Thread
> Does anyone know of any information about building accessible
> web sites with Visual Studio.Net 2003?
VS.net is just the IDE for writing ASP.net code. So, accessibility
issues are really about the developer moreso than the tool.
Version 2003, while popular, does produce pretty crappy markup if you
let it. Most folks that want control over the markup use VS.net for
their back end development and another editor (like Dreamweaver) to
maintain the front end markup.
In addition, in .net 1.1, a lot of the built-in controls spit out pretty
bad markup. As such, I've resorted to writing a lot of my own controls
that manually build the HTML. Kind of defeats the purpose of .net, but
was the only way to get control over my output.
Supposedly, asp.net 2.0 as well as the Visual Studio 2005 product line
fix a lot of these issues.
-Darrel
- Next message: Christian Heilmann: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message: Michael R. Burks: "Visual Studio.Net 2003 and accessibility"
- Next message in Thread: Christian Heilmann: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message in Thread: Michael R. Burks: "Visual Studio.Net 2003 and accessibility"
- View all messages in this Thread