<?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: WebAIM Study: Screenreaders and Javascript Co-Exist</title>
	<atom:link href="http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Martindale</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277928</link>
		<dc:creator>Martindale</dc:creator>
		<pubDate>Sat, 16 Jan 2010 07:29:22 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277928</guid>
		<description>I can attest to this; we have an XHR-dependent web app that we have several blind users quite active in.  Some use braille displays, some use screen readers.  How the data is parsed depends entirely on clean markup.</description>
		<content:encoded><![CDATA[<p>I can attest to this; we have an XHR-dependent web app that we have several blind users quite active in.  Some use braille displays, some use screen readers.  How the data is parsed depends entirely on clean markup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mare</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277799</link>
		<dc:creator>mare</dc:creator>
		<pubDate>Tue, 12 Jan 2010 08:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277799</guid>
		<description>@nataxia
Some can, but these are pirates...</description>
		<content:encoded><![CDATA[<p>@nataxia<br />
Some can, but these are pirates&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nataxia</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277792</link>
		<dc:creator>nataxia</dc:creator>
		<pubDate>Mon, 11 Jan 2010 20:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277792</guid>
		<description>I hear that that a lot of people who unplug their DVD player can&#039;t watch DVD&#039;s.</description>
		<content:encoded><![CDATA[<p>I hear that that a lot of people who unplug their DVD player can&#8217;t watch DVD&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Skilldrick</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277788</link>
		<dc:creator>Skilldrick</dc:creator>
		<pubDate>Mon, 11 Jan 2010 13:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277788</guid>
		<description>Just because a swf&#039;s content is extracted, doesn&#039;t mean that you can read it. Who knows whether paragraphs, words, or even letters will come out in the correct order?</description>
		<content:encoded><![CDATA[<p>Just because a swf&#8217;s content is extracted, doesn&#8217;t mean that you can read it. Who knows whether paragraphs, words, or even letters will come out in the correct order?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ywg</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277783</link>
		<dc:creator>ywg</dc:creator>
		<pubDate>Mon, 11 Jan 2010 09:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277783</guid>
		<description>&quot;The presence of inaccessible Flash content&quot;

Does this mean all flash content, or only content that does not mean certain requirement.
Considering that adobe published SDK to extract swf&#039;s content (initially for search engine) in 2002, I would expect decent screenreaders being able to read basics swf.</description>
		<content:encoded><![CDATA[<p>&#8220;The presence of inaccessible Flash content&#8221;</p>
<p>Does this mean all flash content, or only content that does not mean certain requirement.<br />
Considering that adobe published SDK to extract swf&#8217;s content (initially for search engine) in 2002, I would expect decent screenreaders being able to read basics swf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lennym</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277782</link>
		<dc:creator>lennym</dc:creator>
		<pubDate>Mon, 11 Jan 2010 08:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277782</guid>
		<description>I can&#039;t help but think that the more interesting part of that survey is the stats around browser version usage amongst screenreader users.

A lot of the work towards making scripted web-apps more accessible for these users is based around the WAI-ARIA technologies. However, since these are implemented only in a small subset of clients, it&#039;s difficult to know their efficacy.

I had largely assumed that a user reliant on screenreaders or similar technology would be far more sensitive to browser technology than a fully able user, and therefore would be more likely to change/update their browsers, especially where the implementation or otherwise of a particular feature would make a significant impact on their experince of the web.

On the whole though, this is tremendously interesting set of results for those of us who might have fallen into the trap of looking at screenreader accessibility purely from the perspective of someone who has never relied on such a thing.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t help but think that the more interesting part of that survey is the stats around browser version usage amongst screenreader users.</p>
<p>A lot of the work towards making scripted web-apps more accessible for these users is based around the WAI-ARIA technologies. However, since these are implemented only in a small subset of clients, it&#8217;s difficult to know their efficacy.</p>
<p>I had largely assumed that a user reliant on screenreaders or similar technology would be far more sensitive to browser technology than a fully able user, and therefore would be more likely to change/update their browsers, especially where the implementation or otherwise of a particular feature would make a significant impact on their experince of the web.</p>
<p>On the whole though, this is tremendously interesting set of results for those of us who might have fallen into the trap of looking at screenreader accessibility purely from the perspective of someone who has never relied on such a thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aimos</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277781</link>
		<dc:creator>Aimos</dc:creator>
		<pubDate>Mon, 11 Jan 2010 08:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277781</guid>
		<description>Javascript disabled is like surfing in 2001 or so. Bad.</description>
		<content:encoded><![CDATA[<p>Javascript disabled is like surfing in 2001 or so. Bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulIrish</title>
		<link>http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist/comment-page-1#comment-277770</link>
		<dc:creator>PaulIrish</dc:creator>
		<pubDate>Mon, 11 Jan 2010 03:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8408#comment-277770</guid>
		<description>Tip of the accessible hat to Mr. kangax who I picked up that link from.</description>
		<content:encoded><![CDATA[<p>Tip of the accessible hat to Mr. kangax who I picked up that link from.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

