EPiServer och tillgänglighet
I’ve written another article in Swedish and had it published at 24timmarsbloggen. The article, EPiServer och tillgänglighet, is a look at what is needed to make a site based on the EPiServer CMS accessible and standards compliant.
- Previous post: The Future: HTML or XHTML
- Next post: Going to @media 2005?
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
Very interesting!
What you don't mention in the article is that if you turn off .NET's feature to serve different HTML to different web browsers (which I also recommend) is that if you then use validation controls, they will generate JavaScripts that aren't DOM compliant, hence the validation won't work and throw an error.
Another issue people might run across is that if use content negotiation to serve XHTML as application/xhtml+xml, __doPostBack functionality will not work, if you don't create a work around for that in .NET.
Robert: True, but we don't use any validation controls, so that takes care of that problem ;-)
Sorry, comments are closed for this post.