i've searched in this forum for XHTML Validation in DNN, but haven't found much talk about it.  I'm not looking to start a battle here.  i just expected that this app has been open sourced long enough that validation was handled many iterations ago and that coding standards ensured 3rd party and any new core development was done with compliant markup.

A template application proliferated this widely on the Internet should strive to render valid XHTML and CSS.  It would: 

1. help teach new developers learning from the codebase how to write proper markup 
2. help ensure proper/consistent rendering across different browsers and devices
3. make utilizing the application for professional development scenarios more attractive for a larger audience 
4. contribute to easier accessibility compliance

Especially when all of the pages in this app identify as XHTML 1.0 Transitional (as do all ASP.NET pages by default created with Vstudio...), but the forums main page, for example, has 110 errors. The CSS on the home page has 41 errors.  

Adding alt tags and HTML encoding ampersands in URLs is a pretty simple task - which is what accounts for most of the errors that i found in my initial validation attempt on 2 pages of the corporate site.  And i found some <br> and <img> tags that aren't self-closing, some style tags (in the body of the page mind you...shame, shame) without the type attribute - that's not professional development.  Some simple validation tools are built directly into VStudio (you get squiggly lines under invalid code - as if you are writing VB/C# that doesn't compile), and the W3C validators are simple to use.  

It isn't a large task to write valid XHTML from the start - it shouldn't be an afterthought to get markup to validate after its been coded.  A developer that has 'HTML' on their resume should be writing valid markup, or shouldn't be contributing to open source projects like this. 

QUESTIONS:

1. is XHTML 1.0 Transitional validation a priority for the development team?  
2. Are there coding standards for 3rd party modules and core development to enforce XHTML validation?
3. Is accessibility a priority (to any degree)?