Live data from Hacker News

Whitehouse.gov Has A New Face

techcrunch.com

41–47 of 47 posts

Re: Whitehouse.gov Has A New Face

#41
post #37
post #29

Earlier quoted context omitted.

You are correct. The text versions were present for screen readers.

Instead of just using good markup in the first place?

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:

http://www.whitehouse.gov/accessibility/

"In addition to the features that make the graphics version of the site more accessible, a text-only version provides added convenience for users."

I'm not sure how to access it though, maybe that feature hasn't launched yet.

Re: Whitehouse.gov Has A New Face

#42
post #41
post #37

Earlier quoted context omitted.

Instead of just using good markup in the first place?

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: http://www.whitehouse.gov/accessibility/ "In addition to the features that make the graphics version of the site more accessible, a text-only version provides added convenience for users." I'm not sure how to access it though, maybe…

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.

Re: Whitehouse.gov Has A New Face

#43

Even better, it's valid XHTML 1.0 Transitional: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.whitehous...

Who cares if it validates? The underlying markup is pretty unsemantic.

Just because it validates doesn't mean it's a well-coded website.

Re: Whitehouse.gov Has A New Face

#44
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"

Re: Whitehouse.gov Has A New Face

#45
post #7

The main big block of text next to the picture is a jpg, and looks like it has a ton of compression artifacts. tsk tsk! =) Other than that it's an awesome site, definitely the best government agency site I've ever seen.

Those aren't compress... wait.. yessss that's exactly what they are. Compression artifacts. Move along. You didn't see nuthin'.

Re: Whitehouse.gov Has A New Face

#46
post #42
post #41

Earlier quoted context omitted.

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: http://www.whitehouse.gov/accessibility/ "In addition to the features that make the graphics version of the site more accessible, a text-only version provides added convenience for users." I'm not sure how to access it though, maybe…

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?

Re: Whitehouse.gov Has A New Face

#47
post #46
post #42

Earlier quoted context omitted.

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.

Post reply on HN