<?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: A New Approach for Flash Accessibility</title>
	<atom:link href="http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html</link>
	<description>Michael Krotscheck's insights, ideas, and inspirations about web technology, life, and the kitchen sink.</description>
	<lastBuildDate>Fri, 03 Feb 2012 05:12:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Ian</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-2314</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Tue, 21 Dec 2010 20:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-2314</guid>
		<description>horrendously out of date reply, but just in case you&#039;re got notifications for this Susan - tabbing is also useful for other groups, for example if you aren&#039;t able to use a mouse and need to use a keyboard to operate your browser.</description>
		<content:encoded><![CDATA[<p>horrendously out of date reply, but just in case you&#8217;re got notifications for this Susan &#8211; tabbing is also useful for other groups, for example if you aren&#8217;t able to use a mouse and need to use a keyboard to operate your browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: susan chaisson</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1393</link>
		<dc:creator>susan chaisson</dc:creator>
		<pubDate>Tue, 16 Jun 2009 19:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1393</guid>
		<description>oops - never thought of that. I guess there hasn&#039;t been much more talk on this site since this discussion took place. I&#039;m wondering why accessibility is still not being discussed much on the internet. People trying to find more information so they can design for it (like myself) aren&#039;t getting much on the web!</description>
		<content:encoded><![CDATA[<p>oops &#8211; never thought of that. I guess there hasn&#8217;t been much more talk on this site since this discussion took place. I&#8217;m wondering why accessibility is still not being discussed much on the internet. People trying to find more information so they can design for it (like myself) aren&#8217;t getting much on the web!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Johnston</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1385</link>
		<dc:creator>Stuart Johnston</dc:creator>
		<pubDate>Thu, 06 Nov 2008 16:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1385</guid>
		<description>Because they don&#039;t or can&#039;t use a traditional pointing device (mouse).</description>
		<content:encoded><![CDATA[<p>Because they don&#8217;t or can&#8217;t use a traditional pointing device (mouse).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Teare</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1383</link>
		<dc:creator>Phil Teare</dc:creator>
		<pubDate>Thu, 09 Oct 2008 18:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1383</guid>
		<description>Hey Patrick. Yep - good point. But wouldn&#039;t this be neater for VI users? So both solutions would be good. To my mind it would be neater for VI users because ARIA would solve the dynamic nature of Flash for blind users. I.e. what happens when content updates (how and when to notify or read out new content...). Rather than building another framework for flash.</description>
		<content:encoded><![CDATA[<p>Hey Patrick. Yep &#8211; good point. But wouldn&#8217;t this be neater for VI users? So both solutions would be good. To my mind it would be neater for VI users because ARIA would solve the dynamic nature of Flash for blind users. I.e. what happens when content updates (how and when to notify or read out new content&#8230;). Rather than building another framework for flash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan  Chaisson</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1384</link>
		<dc:creator>Susan  Chaisson</dc:creator>
		<pubDate>Thu, 09 Oct 2008 18:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1384</guid>
		<description>I&#039;ve been trying to use the accessibility panel in flash to create an accessible course built in Lectora (which is accessible). The tutorial I completed using macromedia&#039;s OWN files doesn&#039;t even work with my screen reader. Has anyone had any experience with this? It reads the buttons but skips over the text boxes, even though they are labelled, and tab #&#039;d in the swf.


On another note, why would a sighted user want to tab in/out of a flash movie?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been trying to use the accessibility panel in flash to create an accessible course built in Lectora (which is accessible). The tutorial I completed using macromedia&#8217;s OWN files doesn&#8217;t even work with my screen reader. Has anyone had any experience with this? It reads the buttons but skips over the text boxes, even though they are labelled, and tab #&#8217;d in the swf.</p>
<p>On another note, why would a sighted user want to tab in/out of a flash movie?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krotscheck</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1387</link>
		<dc:creator>Michael Krotscheck</dc:creator>
		<pubDate>Fri, 26 Sep 2008 22:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1387</guid>
		<description>By all means, go get started. I haven&#039;t gotten into it on anything other than an architectural level, and far be it from me to proscribe an approach. Keep me posted, if you don&#039;t mind me getting involved when my schedule clears up again.</description>
		<content:encoded><![CDATA[<p>By all means, go get started. I haven&#8217;t gotten into it on anything other than an architectural level, and far be it from me to proscribe an approach. Keep me posted, if you don&#8217;t mind me getting involved when my schedule clears up again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Teare</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1386</link>
		<dc:creator>Phil Teare</dc:creator>
		<pubDate>Fri, 26 Sep 2008 20:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1386</guid>
		<description>Hi again,

Are you laying claim to any IP on this, or can I start a BSD license project without worrying in that regard?</description>
		<content:encoded><![CDATA[<p>Hi again,</p>
<p>Are you laying claim to any IP on this, or can I start a BSD license project without worrying in that regard?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick h. lauke</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1388</link>
		<dc:creator>patrick h. lauke</dc:creator>
		<pubDate>Thu, 25 Sep 2008 18:38:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1388</guid>
		<description>and what about sighted keyboard users? they DO need/want to tab in and out of flash movies themselves, no?</description>
		<content:encoded><![CDATA[<p>and what about sighted keyboard users? they DO need/want to tab in and out of flash movies themselves, no?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Teare</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1391</link>
		<dc:creator>Phil Teare</dc:creator>
		<pubDate>Wed, 24 Sep 2008 14:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1391</guid>
		<description>exactly.

Its a great idea, and similar to something I&#039;ve been toying with in idle moments.

Have you or has anyone started anything on this?</description>
		<content:encoded><![CDATA[<p>exactly.</p>
<p>Its a great idea, and similar to something I&#8217;ve been toying with in idle moments.</p>
<p>Have you or has anyone started anything on this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krotscheck</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1390</link>
		<dc:creator>Michael Krotscheck</dc:creator>
		<pubDate>Wed, 24 Sep 2008 14:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1390</guid>
		<description>Actually, in this case that&#039;d be an advantage. Remember, you don&#039;t want the user to interact with the flash movie itself, simply with the abstracted DOM hierarchy it&#039;s sitting on.</description>
		<content:encoded><![CDATA[<p>Actually, in this case that&#8217;d be an advantage. Remember, you don&#8217;t want the user to interact with the flash movie itself, simply with the abstracted DOM hierarchy it&#8217;s sitting on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Teare</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1389</link>
		<dc:creator>Phil Teare</dc:creator>
		<pubDate>Wed, 24 Sep 2008 14:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1389</guid>
		<description>you still can&#039;t tab in and out of a flash movie in FF :(

So in practice, nope, still no go.

But this is great. Would love to talk some about this...</description>
		<content:encoded><![CDATA[<p>you still can&#8217;t tab in and out of a flash movie in FF <img src='http://www.krotscheck.net/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>So in practice, nope, still no go.</p>
<p>But this is great. Would love to talk some about this&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krotscheck</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1382</link>
		<dc:creator>Michael Krotscheck</dc:creator>
		<pubDate>Sun, 24 Aug 2008 21:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1382</guid>
		<description>I stand corrected, Thanks! Though a bit of research shows that this is a relatively recent improvement via the IAccessible2 inclusion in FF3. Still, a great development overall.... though it&#039;s still not cross platform.</description>
		<content:encoded><![CDATA[<p>I stand corrected, Thanks! Though a bit of research shows that this is a relatively recent improvement via the IAccessible2 inclusion in FF3. Still, a great development overall&#8230;. though it&#8217;s still not cross platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Leventhal</title>
		<link>http://www.krotscheck.net/2008/08/23/a-new-approach-for-flash-accessibility.html/comment-page-1#comment-1381</link>
		<dc:creator>Aaron Leventhal</dc:creator>
		<pubDate>Sun, 24 Aug 2008 18:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalflash.com/articles/a-new-approach-for-flash-accessibility/#comment-1381</guid>
		<description>&gt; Flash content at this point can only interface with several select screen readers,
&gt; only on IE running on Windows. This is because the Flash player uses Microsoft’s
&gt; Accessibility Interface (whose official name I don’t know), which is, of course, only
&gt; supported in and via Microsoft technologies.

Correction. Flash is accessible in Firefox, via Microsoft Active Accessibility, which Firefox supports, as do numerous non-Microsoft technologies.</description>
		<content:encoded><![CDATA[<p>&gt; Flash content at this point can only interface with several select screen readers,<br />
&gt; only on IE running on Windows. This is because the Flash player uses Microsoft’s<br />
&gt; Accessibility Interface (whose official name I don’t know), which is, of course, only<br />
&gt; supported in and via Microsoft technologies.</p>
<p>Correction. Flash is accessible in Firefox, via Microsoft Active Accessibility, which Firefox supports, as do numerous non-Microsoft technologies.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

