I've been looking into Accessiblity lately as well as the Microsoft Accessibility Inititive [6].  The American's with Disabilities act requires that Federal Websites be accessible to all [1].    The W3C has a number of pages on Web Accesiblity, under the WAI working group.  These guidelines [2] and [3] offer a lot of guidelines and techniques [4] on how to write HTML that is up to snuff and accesible to all.  These extra tags and techniques allow Screen Reading Software [5] that linearize HTML and provide additional context, like which labels go with which text boxes.  You can test your website for accessiblity with online tools like Bobby.[7] 

[1] http://www.section508.gov/

[2] http://www.w3.org/TR/1998/WD-WAI-PAGEAUTH-0203

[3] http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505

[4] http://www.w3.org/TR/WCAG10-HTML-TECHS

[5] http://www.freedomscientific.com

[6] http://www.microsoft.com/enable  

[7] http://bobby.watchfire.com/bobby/html/en

[8] http://www.w3.org/WAI/ER/IG/ert

I really enjoyed this article in Ray Ozzie's Blog on Software Platform Dynamics. 

This may be an obvious observation to some, but I just think it's fantastic to see how features from Microsoft Research videos from 2 or 3 years ago [http://www.aisto.com/roeder/ip/] show up directly in products today.  What a concept! R&D dollars that go directly into shipping products! :)  This Video on Intentional Programming shows a number of more superficial features that are currently in Visual Studio.NET. 

Aside from these few features they've brought forward like the Compile Error Todo List, I'd like to see how the CodeDom  would end up being used in a more far-reaching IP implementation on top of the .NET CLR.