I have converted all but two modules to XHTML compliant Traditional 1.0.  Some modules have also been converted to WSAG and Section 508 compliancy.  The most recurring errors were:

- no end tag i.e:  an hr tag without a closing /
- hanging tags i.e just a random td tag or footer tag
- no html xmlns declartion i.e all aspx pages need this
- td's without a tr i.e: just place a tr inside a table without a tr around it
- no title tag


All in all the html wasnt bad.  There were some random hardcore errors but most were pretty simple.  I have to go apply some XHTML updates to the error pages to finish up.  The pages are using partial classes and their events need to be checked. We need to find a solution to this issue.  Initialize component needs to be refactored out and the events need to be checked if they are working.  I know jon is going through some of this but we need more help.  I also know Mike is going to be on this but it would really be nice if we could have an XHTML or Standards Admin.  Just to make sure all modules and code is of standards.  Second we need someone to head module testing [ maybe mike ;) ].  If you like standards hit me up.  I offer to the community first before I go to site point hehe.  I have already done most of the work to get the first model down.  There are still warnings in the pages such as "This method is out of date".  We need some devs to go through these and use the .NET 2.0 recommendations or apply industry fixes.  This will make the core stronger.  The modules pretty much run on top of rainbow and provide its functionality and are comforted by the Rainbow.Framework and Core assemblies.