From SlashDot... "It has been going on nine years now, but finally there are formal standards for Web accessibility for technologies other than HTML . They ask that you start with the press release (lots of links), but regulars might be more entertained by the last time WCAG made the front page here. Many folks here will point out that web accessibility is old hat, and by implication this is hardly news, but if you do Web development for any government organization, you should expect that accessibility is a base requirement. The Section 508 standards are to be updated (relatively) soon too." This is great news for government developers! Being finalized, this specification incorporates accessibility guidance for Web 2.0 technologies...
In my previous Silverlight Closed Captioning screencast here , I showed you how to use Expression Encoder to import Closed Captioning information to produce a solution without writing a line of code. What if you store your Closed Captioning information in an external data source (database, SAMI file, XML file, etc.) and want to keep it there? Do you have to reprocess all of your videos using Expression Encoder? Of course not, but you do have to write some code:). In this screencast, I show you how to use Silverlight, ASP.NET AJAX, and the Windows Communication Foundation (WCF) to solve this problem. You can view the screencast here . To get the sample code, just click the link below: The sample requires Visual Studio 2008 beta 2 or later. -...
I just came across this recently published article. A significant portion of it covers accessibility. You'll also want to download the Writing Accessible Web Applications document from MSDN Downloads. The document talks about accessibility with AJAX. -Marc Read More...