<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Google Wave and Accessibility</title>
	<link>http://ericstoller.com/blog/2009/10/22/google-wave-and-accessibility/</link>
	<description>| social justice | higher education | technology |</description>
	<pubDate>Fri, 12 Mar 2010 18:33:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Google adds auto-captioning to YouTube &#187; Eric Stoller&#8217;s Blog</title>
		<link>http://ericstoller.com/blog/2009/10/22/google-wave-and-accessibility/#comment-37425</link>
		<pubDate>Sun, 29 Nov 2009 03:13:10 +0000</pubDate>
		<guid>http://ericstoller.com/blog/2009/10/22/google-wave-and-accessibility/#comment-37425</guid>
					<description>[...] Google does not always create accessible products (GoogleWave). However, sometimes they do a good job of increasing the accessibility of an existing service. I hope that Vimeo gets the message that accessibility is important. In the first major step toward making millions of videos on YouTube accessible to deaf and hearing-impaired people, Google unveiled new technologies that will automatically bring text captions to many videos on the site. [Google] combined their automatic speech recognition (ASR) technology with the YouTube caption system to offer automatic captions, or auto-caps for short. Auto-caps use the same voice recognition algorithms in Google Voice to automatically generate captions for video. Tags: accessibility, Accessibility Usability, captioning, google, Higher Education, Social Justice, subtitles, technology, Vimeo, youtube [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Google does not always create accessible products (GoogleWave). However, sometimes they do a good job of increasing the accessibility of an existing service. I hope that Vimeo gets the message that accessibility is important. In the first major step toward making millions of videos on YouTube accessible to deaf and hearing-impaired people, Google unveiled new technologies that will automatically bring text captions to many videos on the site. [Google] combined their automatic speech recognition (ASR) technology with the YouTube caption system to offer automatic captions, or auto-caps for short. Auto-caps use the same voice recognition algorithms in Google Voice to automatically generate captions for video. Tags: accessibility, Accessibility Usability, captioning, google, Higher Education, Social Justice, subtitles, technology, Vimeo, youtube [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Curt Grymala</title>
		<link>http://ericstoller.com/blog/2009/10/22/google-wave-and-accessibility/#comment-37159</link>
		<pubDate>Fri, 23 Oct 2009 14:21:13 +0000</pubDate>
		<guid>http://ericstoller.com/blog/2009/10/22/google-wave-and-accessibility/#comment-37159</guid>
					<description>I don't know why anyone's surprised by this. Last time I checked, Gmail, GoogleDocs forms, Google Voice and Analytics (among others, I'm certain) don't conform to most accessibility standards. Why should Google Wave be any different than the rest of the Google commodities?

I think, in the long run, it would be much easier to start a list of the accessibility standards that Google applications do meet and which apps meet those standards rather than to try to point out all of the standards they don't.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why anyone&#8217;s surprised by this. Last time I checked, Gmail, GoogleDocs forms, Google Voice and Analytics (among others, I&#8217;m certain) don&#8217;t conform to most accessibility standards. Why should Google Wave be any different than the rest of the Google commodities?</p>
<p>I think, in the long run, it would be much easier to start a list of the accessibility standards that Google applications do meet and which apps meet those standards rather than to try to point out all of the standards they don&#8217;t.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
