Tips for improved accessibility in ASP.NET 1.1
Tips for improved accessibility in ASP.NET 1.1 contains information on some important issues you need to deal with if you use current versions of ASP.NET to develop websites. If you want them to be accessible and adhere to web standards, that is.
Hopefully things will be better when ASP.NET 2.0 is released, though there are reports like Charl van Niekerk’s ASP.NET 2.0 - Part 2 that prevent me from hoping too much. And no matter how good Microsoft makes its developer software, I think we won’t see many ASP.NET driven websites that adhere to the spirit of web standards until a majority of ASP.NET developers start showing some interest.
- Previous post: A List Too Far Apart?
- Next post: HTML tags vs. elements vs. attributes
Information, sponsorship, and externals
About the author
Roger Johansson is a Swedish web professional specialising in web standards, accessibility, and usability. More about me and this site.
Latest articles
- Validation statistics from Nikita the Spider Comments off
- An analysis of the sites crawled by the bulk validation tool Nikita the Spider during March 2008.
- Authentic Jobs API and Affiliates program Comments off
- The Authentic Jobs job listing service now has a public API and an affiliate program.
- What does Acid3 mean to you and me? Comments off
- Opera and Apple have announced that their web browsers pass the Acid3 Browser Test, but how will that help web designers and developers?
- Designing Web Navigation (Book review) Comments off
- Learn the fundamentals of navigation design and design better navigation systems for large and small sites as well as for web based applications.
- DOMAssistant bundle for TextMate Comments off
- To save keystrokes and speed up development I have created a DOMAssistant bundle for TextMate.
- First impressions of Internet Explorer 8 Beta 1 Comments off
- My impressions after trying out Internet Explorer 8 Beta 1 for a couple of days.
Comments
I had no idea you were into .NET, cool :)
If you use VS.NET, then you share my pain.
I only ever touch .NET out of necessity ;-). And when I do, I stay as far away from VS.NET as possible. I only use it to compile stuff - I do all coding in BBEdit on my Mac.
I only do .NET development at work anymore, unless I'm maintaining an old website of mine. At work though, we cannot get away from VS.NET. I even have had to start using the design mode recently, which is something I've never, ever, ever done.
We've started intergrating the Peter Blum Validator controls into our apps, and going into design mode to add controls is much, much easier than by hand.
You're hardcore for using BBEdit, I couldn't do it, not for the size apps I'm dealing with anyway.
I have found that if you understand the boundries of VS.NET in regards to when it starts inserting crappy HTML, you can actually be quite productive using this tool while at the same time writing valid XHTML (transitional) markup.
I think Standard coding in VS.NET is a tragedy !
Sorry, comments are closed for this post.