Good markup can't handle it all, text-only mode allows for stuff like having a transcript instead of a video with a link to a transcript. Text-only mode is even available on the new site:
I'm going to disagree. Let me share some background, I spent several years helping to write the Web Content Accessibility Guidelines 2.0 spec. The original WCAG 1.0 as well as Section 508 specify an alternate text only site as a viable method.
Real world experience shows us those sites quickly fall behind. Text-alternatives are necessary for multimedia content, text-only sites as an alternative to good markup aren't.
Fall behind in what sense? Obviously, if the multimedia content isn't transcribed quickly enough, then that makes sense, but I would also guess less consequential than if a given page weren't transformed from 'marked up' to 'text', but in the latter case, if the backend is dynamic, and just changing the output format, why would it fall behind?
People just don't want to maintain 2 sites. Extra features and sections often don't get updated to the text only rendering.
I guess my point is that screen readers like (even prefer) well written markup. A text-only site is a kickback from when they couldn't and the accessibility guidelines were written to deal with that.
It's also built using jQuery as tweeted by jResig. I was hoping Obama would begin using twitter immediately after taking the Presidency. We'll see if the twitter account falls into the history books and is not utilized.
"Except where otherwise noted, third-party content on this site is licensed under a Creative Commons Attribution 3.0 License. Visitors to this website agree to grant a non-exclusive, irrevocable, royalty-free license to the rest of the world for their submissions to Whitehouse.gov under the Creative Commons Attribution 3.0 License."
This doesn't mean much. I believe all works produced by the federal government are in the public domain and you don't need permission to reproduce them.
True, and covered in the first of the three paragraphs at that link:
"Pursuant to federal law, government-produced materials appearing on this site are not copyright protected. The United States Government may receive and hold copyrights transferred to it by assignment, bequest, or otherwise."
The news is that they're defaulting to Creative Commons for all "third-party content" on the site, including user submissions. That's the part that got me. Even if they're not producing it, they're trying to keep information open (as opposed to just requiring copyright assignment, for instance)
I'm sure a ton of people will. In fact, I would bet that the whitehouse blog may introduce lots of people to RSS for the first time ever. The concept of a more transparent government where citizens are informed about the happenings inside the white house will be heavily at play here.
ok, am I the only fool who got a bit teary eyed when going through whitehouse.gov? Whether you agree with his politics or not, you have to admit that he is going to change the way we interact with our government.
"President Obama started his career as a community organizer on the South Side of Chicago, where he saw firsthand what people can do when they come together for a common cause"
Blue State Digital built CHANGE.GOV, and this is pretty clearly a continuation, although the impression I get is that they've brought a lot of it in-house.
I thought BSD was a shoe-in for this as well, but if you view source you'll see the hallmarks of ASP.NET (viewstate and control naming), which throws me.
If you search google for 'whitehouse' and 'robots' then you can still see the cache of the robots.txt file of the Bush Administration (http://74.125.47.132/search?q=cache:tCfemw3M-aUJ:www.whiteho...)