Last post Dec 07, 2005 07:46 PM by cathal
Dec 07, 2005 02:26 PM|mathisjay|LINK
There is an interesting article about ASP.NET 2.0 controls and, more generally, XHTML compliance and disability accessibility, that I thought was a good read.
In my oversimplistic summary, the article talks in general about concepts that web designers should try to adopt (such as not using <table> for layout) and other things. And it explains how the new .NET2.0 controls *help* adhere to XHTML Transitional 1.0
The article is written by the same guy that made the original Community Starter Kit.
It will interesting to see if the core DNN product adopts some of the new .NET controls (like the Treeview or Login or Wizard) to take advantage of thier new functionality.
Dec 07, 2005 02:42 PM|DougV|LINK
Dec 07, 2005 07:46 PM|cathal|LINK
I did do a quick test on a demo 3.2 site, switching between asp.net 1.1 and asp.net 2.0 a while back, and ran the w3c validator against it. Whilst there were still errors (missing alt tags, id in head, fields beginning with _ etc.), there were a lower number
of compliance failures in asp.net 2.0 (don't have the site anymore to give exact details). There page was also smaller, as the viewstate was 42% smaller due to the change in the viewstate serialisation model in asp.net 2.0.
FYI: a compliance task was added to the roadmap discussion forum that we're debating at the minute, so it's an area we'll be looking at in the next while.