<?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"
	>
<channel>
	<title>Comments on: Screen Readers Suck</title>
	<atom:link href="http://erik.eae.net/archives/2005/07/19/21.02.16/feed/" rel="self" type="application/rss+xml" />
	<link>http://erik.eae.net/archives/2005/07/19/21.02.16/</link>
	<description>The Weblog of Erik Arvidsson</description>
	<pubDate>Thu, 28 Aug 2008 14:12:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Maria Carter</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-47288</link>
		<dc:creator>Maria Carter</dc:creator>
		<pubDate>Tue, 05 Dec 2006 08:38:05 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-47288</guid>
		<description>&lt;strong&gt;George Lewis...&lt;/strong&gt;

The 2534 Dorothy Harris blog...</description>
		<content:encoded><![CDATA[<p><strong>George Lewis&#8230;</strong></p>
<p>The 2534 Dorothy Harris blog&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Site Accessibility Blog &#8220; Joe Clark&#8217;s ScreenReader Rant</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-5843</link>
		<dc:creator>Web Site Accessibility Blog &#8220; Joe Clark&#8217;s ScreenReader Rant</dc:creator>
		<pubDate>Fri, 11 Nov 2005 19:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-5843</guid>
		<description>[...] rently, the feeling in the industry is that   &#8220;screen readers suck&#8221;, and again &#8220;screen readers suck&#8221; 2.    Designers who are aware o [...]</description>
		<content:encoded><![CDATA[<p>[...] rently, the feeling in the industry is that   &#8220;screen readers suck&#8221;, and again &#8220;screen readers suck&#8221; 2.    Designers who are aware o [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Krantz</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-5335</link>
		<dc:creator>Peter Krantz</dc:creator>
		<pubDate>Sun, 11 Sep 2005 10:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-5335</guid>
		<description>Good news is that screen readers are getting better. The mozilla DHTML accessibility support (http://www.mozilla.org/access/dhtml/#atsupport) is apparently already supported by the upcoming version of Window Eyes 5.5 (beta 1: http://www.gwmicro.com/beta/).</description>
		<content:encoded><![CDATA[<p>Good news is that screen readers are getting better. The mozilla DHTML accessibility support (http://www.mozilla.org/access/dhtml/#atsupport) is apparently already supported by the upcoming version of Window Eyes 5.5 (beta 1: <a href="http://www.gwmicro.com/beta/" rel="nofollow">http://www.gwmicro.com/beta/</a>).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Featherstone</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-5111</link>
		<dc:creator>Derek Featherstone</dc:creator>
		<pubDate>Tue, 19 Jul 2005 21:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-5111</guid>
		<description>&lt;blockquote&gt;If you turn off js you will limit keyboard navigation and visually impared users are people that really make use of improved keyboard navigation.&lt;/blockquote&gt;

That entirely depends on context and how the "thing" was built. I say "thing" because interacting with an application will be entirely different than interacting with a page, for example, that shows and hides content using DOM Scripting.

The tree example you mention is a good example, in theory. It might still be a situation where a user of some older screen reader "insert version here" might not handle that interaction properly, and if so, if we've built things "correctly" even with JS off, that tree example might be less than optimally usable, but better than not being able to interact with it at all.

Believe me - as a member of both the DOM Scripting Task Force, and the Accessibility/Assistive Devices Task Force - I want nothing more than to move this stuff forward so that we can use modern scripting techniques along side assistive tech in a complementary way, rather than in a limiting way.</description>
		<content:encoded><![CDATA[<blockquote><p>If you turn off js you will limit keyboard navigation and visually impared users are people that really make use of improved keyboard navigation.</p></blockquote>
<p>That entirely depends on context and how the &#8220;thing&#8221; was built. I say &#8220;thing&#8221; because interacting with an application will be entirely different than interacting with a page, for example, that shows and hides content using DOM Scripting.</p>
<p>The tree example you mention is a good example, in theory. It might still be a situation where a user of some older screen reader &#8220;insert version here&#8221; might not handle that interaction properly, and if so, if we&#8217;ve built things &#8220;correctly&#8221; even with JS off, that tree example might be less than optimally usable, but better than not being able to interact with it at all.</p>
<p>Believe me - as a member of both the DOM Scripting Task Force, and the Accessibility/Assistive Devices Task Force - I want nothing more than to move this stuff forward so that we can use modern scripting techniques along side assistive tech in a complementary way, rather than in a limiting way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Arvidsson</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-5110</link>
		<dc:creator>Erik Arvidsson</dc:creator>
		<pubDate>Tue, 19 Jul 2005 21:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-5110</guid>
		<description>That makes a bit more sense. However I do not agree with you that people should turn off js to get a better experience. If you turn off js you will limit keyboard navigation and visually impared users are people that really make use of improved keyboard navigation.

Take a tree as a good example. With scripting enabled you can allow the user to navigate using the arrow keys and you can make the tree have one tab index, instead of each item having its own entry in the focus chain.</description>
		<content:encoded><![CDATA[<p>That makes a bit more sense. However I do not agree with you that people should turn off js to get a better experience. If you turn off js you will limit keyboard navigation and visually impared users are people that really make use of improved keyboard navigation.</p>
<p>Take a tree as a good example. With scripting enabled you can allow the user to navigate using the arrow keys and you can make the tree have one tab index, instead of each item having its own entry in the focus chain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Featherstone</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-5109</link>
		<dc:creator>Derek Featherstone</dc:creator>
		<pubDate>Tue, 19 Jul 2005 21:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-5109</guid>
		<description>&lt;blockquote&gt;There are currently three ways to go here:

   1. Shut out visually impared people. (Is this what Derek Featherstone is suggesting?)&lt;/blockquote&gt;

No, actually, that is most definitely &lt;em&gt;not&lt;/em&gt; what I was suggesting. To provide some context, I was actually making the following points:

1. Screen reader software is getting better in its support for scripting
2. Where screen reader software fails (for example, in certain AJAXian techniques), if we've built things "correctly" using progressive enhancement, graceful degradation and unobtrusive scripting, we should be able to tell screen readers users to turn JS off so that they actually get a better experience.
3. Turning JS off may be more important for people using &lt;em&gt;older versions&lt;/em&gt; of screen reader software.

That's what I was suggesting - certainly not suggesting that they be shut out, in any way shape or form.

Hope that clarifies... </description>
		<content:encoded><![CDATA[<blockquote><p>There are currently three ways to go here:</p>
<p>   1. Shut out visually impared people. (Is this what Derek Featherstone is suggesting?)</p></blockquote>
<p>No, actually, that is most definitely <em>not</em> what I was suggesting. To provide some context, I was actually making the following points:</p>
<p>1. Screen reader software is getting better in its support for scripting<br />
2. Where screen reader software fails (for example, in certain AJAXian techniques), if we&#8217;ve built things &#8220;correctly&#8221; using progressive enhancement, graceful degradation and unobtrusive scripting, we should be able to tell screen readers users to turn JS off so that they actually get a better experience.<br />
3. Turning JS off may be more important for people using <em>older versions</em> of screen reader software.</p>
<p>That&#8217;s what I was suggesting - certainly not suggesting that they be shut out, in any way shape or form.</p>
<p>Hope that clarifies&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Arvidsson</title>
		<link>http://erik.eae.net/archives/2005/07/19/21.02.16/#comment-5106</link>
		<dc:creator>Erik Arvidsson</dc:creator>
		<pubDate>Tue, 19 Jul 2005 19:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://erik.eae.net/archives/2005/07/19/20.16.10/#comment-5106</guid>
		<description>Here are the pages at Mozilla.org. Try these in Deer Park Alpha 2 with MS Narrator (JAWS chokes)

http://www.mozilla.org/access/dhtml/</description>
		<content:encoded><![CDATA[<p>Here are the pages at Mozilla.org. Try these in Deer Park Alpha 2 with MS Narrator (JAWS chokes)</p>
<p><a href="http://www.mozilla.org/access/dhtml/" rel="nofollow">http://www.mozilla.org/access/dhtml/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
