<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exposure of audio and video elements to assistive technologies</title>
	<atom:link href="http://www.marcozehe.de/2009/06/11/exposure-of-audio-and-video-elements-to-assistive-technologies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marcozehe.de/2009/06/11/exposure-of-audio-and-video-elements-to-assistive-technologies/</link>
	<description>Musings, tips and tricks about the accessible software world</description>
	<lastBuildDate>Thu, 09 Feb 2012 00:25:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Silvia Pfeiffer</title>
		<link>http://www.marcozehe.de/2009/06/11/exposure-of-audio-and-video-elements-to-assistive-technologies/comment-page-1/#comment-24849</link>
		<dc:creator>Silvia Pfeiffer</dc:creator>
		<pubDate>Mon, 02 Nov 2009 00:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/?p=155#comment-24849</guid>
		<description>Hmm ... what&#039;s the shortcut for &quot;mute&quot; ?</description>
		<content:encoded><![CDATA[<p>Hmm &#8230; what&#8217;s the shortcut for &#8220;mute&#8221; ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ginger&#8217;s thoughts &#187; The different aspects of video accessibility</title>
		<link>http://www.marcozehe.de/2009/06/11/exposure-of-audio-and-video-elements-to-assistive-technologies/comment-page-1/#comment-19831</link>
		<dc:creator>ginger&#8217;s thoughts &#187; The different aspects of video accessibility</dc:creator>
		<pubDate>Mon, 03 Aug 2009 01:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/?p=155#comment-19831</guid>
		<description>[...] for exposure of these controls to screen readers, Mozilla implemented this in June, see Marco Zehe&#8217;s blog post on it. It implies having to use focus mode for now, so if you haven&#8217;t been able to use keyboard for [...]</description>
		<content:encoded><![CDATA[<p>[...] for exposure of these controls to screen readers, Mozilla implemented this in June, see Marco Zehe&#8217;s blog post on it. It implies having to use focus mode for now, so if you haven&#8217;t been able to use keyboard for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: about:mozilla &#8211; Service Week, New AMO, Community store, 3.5 demos, FSOSS, audio/video, Design Challenge, Weave, Jetpack, Personas, and more&#8230; &#124; Easy Firefox</title>
		<link>http://www.marcozehe.de/2009/06/11/exposure-of-audio-and-video-elements-to-assistive-technologies/comment-page-1/#comment-17191</link>
		<dc:creator>about:mozilla &#8211; Service Week, New AMO, Community store, 3.5 demos, FSOSS, audio/video, Design Challenge, Weave, Jetpack, Personas, and more&#8230; &#124; Easy Firefox</dc:creator>
		<pubDate>Wed, 17 Jun 2009 08:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/?p=155#comment-17191</guid>
		<description>[...] Marco Zehe, part of Mozilla&#8217;s Accessibility effort, writes that the Firefox 3.5 Preview release included &#8220;exposure of the HTML5 audio and video elements through the MSAA/IAccessible2 and ATK/AT-SPI accessibility interfaces, further strengthening our commitment to Open Video. What this means is that, using NVDA or Orca, you now have access to an HTML5 audio or video file embedded in a web page. If the &#8216;controls&#8217; attribute is specified within the audio or video tag, Firefox 3.5 creates its own set of playback controls. These are now exposed to screen readers using MSAA or AT-SPI to traverse our trees. Exposure through iSimpleDOM interfaces on Windows will come at a later stage. Previously, these controls were unreachable.&#8221; For more information about these new features, see Marco&#8217;s post. [...]</description>
		<content:encoded><![CDATA[<p>[...] Marco Zehe, part of Mozilla&#8217;s Accessibility effort, writes that the Firefox 3.5 Preview release included &#8220;exposure of the HTML5 audio and video elements through the MSAA/IAccessible2 and ATK/AT-SPI accessibility interfaces, further strengthening our commitment to Open Video. What this means is that, using NVDA or Orca, you now have access to an HTML5 audio or video file embedded in a web page. If the &#8216;controls&#8217; attribute is specified within the audio or video tag, Firefox 3.5 creates its own set of playback controls. These are now exposed to screen readers using MSAA or AT-SPI to traverse our trees. Exposure through iSimpleDOM interfaces on Windows will come at a later stage. Previously, these controls were unreachable.&#8221; For more information about these new features, see Marco&#8217;s post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Smith</title>
		<link>http://www.marcozehe.de/2009/06/11/exposure-of-audio-and-video-elements-to-assistive-technologies/comment-page-1/#comment-16854</link>
		<dc:creator>Aaron Smith</dc:creator>
		<pubDate>Thu, 11 Jun 2009 16:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/?p=155#comment-16854</guid>
		<description>FWIW, this feature works with Window-Eyes 7 (current 7.1 beta 1) as well. Navigate to the play button, press space to start the video. Toggle off browse mode with Control-Shift-A, tab once to hear, &quot;Grouping Object,&quot; then the rest of the keys outlined in the table above work as expected.</description>
		<content:encoded><![CDATA[<p>FWIW, this feature works with Window-Eyes 7 (current 7.1 beta 1) as well. Navigate to the play button, press space to start the video. Toggle off browse mode with Control-Shift-A, tab once to hear, &#8220;Grouping Object,&#8221; then the rest of the keys outlined in the table above work as expected.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

