<?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: Accessibility notes &#8211; Screen readers and Flash</title>
	<atom:link href="http://mentalaxis.com/words/2006/04/19/accessibility-notes-screen-readers-and-flash/feed/" rel="self" type="application/rss+xml" />
	<link>http://mentalaxis.com/words/2006/04/19/accessibility-notes-screen-readers-and-flash/</link>
	<description>in the kingdom of the blind... stay off the highway!</description>
	<lastBuildDate>Wed, 16 Sep 2009 17:40:40 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: web</title>
		<link>http://mentalaxis.com/words/2006/04/19/accessibility-notes-screen-readers-and-flash/comment-page-1/#comment-3765</link>
		<dc:creator>web</dc:creator>
		<pubDate>Sat, 11 Nov 2006 15:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://mentalaxis.com/words/?p=2#comment-3765</guid>
		<description>nice site!</description>
		<content:encoded><![CDATA[<p>nice site!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Milkins</title>
		<link>http://mentalaxis.com/words/2006/04/19/accessibility-notes-screen-readers-and-flash/comment-page-1/#comment-71</link>
		<dc:creator>Jason Milkins</dc:creator>
		<pubDate>Mon, 17 Jul 2006 16:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://mentalaxis.com/words/?p=2#comment-71</guid>
		<description>I probably should have mentioned that the use of Flash with accessibility features should always be taken as a significant project cost, it can often double or triple the cost, especially if an inexperienced Flash designer and or developer is learning the accessibility ropes, so to speak.

The single most important thing to remember is graceful fallback, if the flash content can be produced effectively in HTML (and not AJAX ok) then it shold be considered the primary mode of contact with the accessibility user base.

These are issues which project planners and accessibility guardians should be very aware of, Flash developers need only ensure they&#039;re able to highlight issues with certain Flash design ideas... Patterns will emerge, and as I said in the article, it&#039;s still a young field of expertise, particularly in the Flash community.</description>
		<content:encoded><![CDATA[<p>I probably should have mentioned that the use of Flash with accessibility features should always be taken as a significant project cost, it can often double or triple the cost, especially if an inexperienced Flash designer and or developer is learning the accessibility ropes, so to speak.</p>
<p>The single most important thing to remember is graceful fallback, if the flash content can be produced effectively in HTML (and not AJAX ok) then it shold be considered the primary mode of contact with the accessibility user base.</p>
<p>These are issues which project planners and accessibility guardians should be very aware of, Flash developers need only ensure they&#8217;re able to highlight issues with certain Flash design ideas&#8230; Patterns will emerge, and as I said in the article, it&#8217;s still a young field of expertise, particularly in the Flash community.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
