<?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 Call for Accessibility</title>
	<atom:link href="http://cafe.elharo.com/web/a-call-for-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/web/a-call-for-accessibility/</link>
	<description>Longer than a blog; shorter than a book</description>
	<lastBuildDate>Wed, 08 Feb 2012 21:45:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: lawyer in tucson</title>
		<link>http://cafe.elharo.com/web/a-call-for-accessibility/comment-page-1/#comment-707928</link>
		<dc:creator>lawyer in tucson</dc:creator>
		<pubDate>Sat, 18 Jun 2011 11:29:47 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/a-call-for-accessibility/#comment-707928</guid>
		<description>Most of what you say is supprisingly accurate and it makes me wonder why I hadn&#039;t looked at this in this light before. This piece really did turn the light on for me as far as this topic goes. But there is one point I am not too comfortable with and while I try to reconcile that with the central theme of your point, let me see what the rest of your readers have to say. Well done.</description>
		<content:encoded><![CDATA[<p>Most of what you say is supprisingly accurate and it makes me wonder why I hadn&#8217;t looked at this in this light before. This piece really did turn the light on for me as far as this topic goes. But there is one point I am not too comfortable with and while I try to reconcile that with the central theme of your point, let me see what the rest of your readers have to say. Well done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christophe Strobbe</title>
		<link>http://cafe.elharo.com/web/a-call-for-accessibility/comment-page-1/#comment-79498</link>
		<dc:creator>Christophe Strobbe</dc:creator>
		<pubDate>Fri, 20 Apr 2007 22:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/a-call-for-accessibility/#comment-79498</guid>
		<description>Robert Hahn,
The screen reader that comes with Windows is known as &quot;Narrator&quot; and is not considered as a replacement for powerful screen readers such as JAWS or Window-Eyes. See for example the comment at http://www.afb.org/afbpress/pub.asp?DocID=AW030206 : &quot;Narrator is a basic screen reader that provides speech output for blind computer users. It is not intended to replace more powerful commercially available screen readers. Rather, it is intended to help you when your normal adaptive equipment is not available.&quot; 
Microsoft Narrator even has an entry in Wikipedia: http://en.wikipedia.org/wiki/Microsoft_Narrator.

There is also work being done on free screen readers for Windows: 
 * NVDA (NonVisual Desktop Access; http://www.nvda-project.org/), which is also open-source, and
 * Thunder (free, but not open source; http://www.screenreader.net/).</description>
		<content:encoded><![CDATA[<p>Robert Hahn,<br />
The screen reader that comes with Windows is known as &#8220;Narrator&#8221; and is not considered as a replacement for powerful screen readers such as JAWS or Window-Eyes. See for example the comment at <a href="http://www.afb.org/afbpress/pub.asp?DocID=AW030206" rel="nofollow">http://www.afb.org/afbpress/pub.asp?DocID=AW030206</a> : &#8220;Narrator is a basic screen reader that provides speech output for blind computer users. It is not intended to replace more powerful commercially available screen readers. Rather, it is intended to help you when your normal adaptive equipment is not available.&#8221;<br />
Microsoft Narrator even has an entry in Wikipedia: <a href="http://en.wikipedia.org/wiki/Microsoft_Narrator" rel="nofollow">http://en.wikipedia.org/wiki/Microsoft_Narrator</a>.</p>
<p>There is also work being done on free screen readers for Windows:<br />
 * NVDA (NonVisual Desktop Access; <a href="http://www.nvda-project.org/" rel="nofollow">http://www.nvda-project.org/</a>), which is also open-source, and<br />
 * Thunder (free, but not open source; <a href="http://www.screenreader.net/" rel="nofollow">http://www.screenreader.net/</a>).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John G</title>
		<link>http://cafe.elharo.com/web/a-call-for-accessibility/comment-page-1/#comment-70079</link>
		<dc:creator>John G</dc:creator>
		<pubDate>Fri, 30 Mar 2007 02:36:27 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/a-call-for-accessibility/#comment-70079</guid>
		<description>The link (http://www.w3.org/WAI/ER/tools/complete/) appears to be broken. The complete list of tools is available at http://www.w3.org/WAI/ER/tools/complete.php.</description>
		<content:encoded><![CDATA[<p>The link (<a href="http://www.w3.org/WAI/ER/tools/complete/" rel="nofollow">http://www.w3.org/WAI/ER/tools/complete/</a>) appears to be broken. The complete list of tools is available at <a href="http://www.w3.org/WAI/ER/tools/complete.php" rel="nofollow">http://www.w3.org/WAI/ER/tools/complete.php</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roberthahn</title>
		<link>http://cafe.elharo.com/web/a-call-for-accessibility/comment-page-1/#comment-69860</link>
		<dc:creator>roberthahn</dc:creator>
		<pubDate>Thu, 29 Mar 2007 12:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/a-call-for-accessibility/#comment-69860</guid>
		<description>I&#039;ve since learned from the last post that Windows XP and  Vista both contain built-in screen readers; why are you suggesting web developers spend at least US$900 on a license for JAWS?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve since learned from the last post that Windows XP and  Vista both contain built-in screen readers; why are you suggesting web developers spend at least US$900 on a license for JAWS?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roberthahn</title>
		<link>http://cafe.elharo.com/web/a-call-for-accessibility/comment-page-1/#comment-69673</link>
		<dc:creator>roberthahn</dc:creator>
		<pubDate>Thu, 29 Mar 2007 00:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/a-call-for-accessibility/#comment-69673</guid>
		<description>Not bad; it&#039;s a good start. Some points for consideration:


Some of the language in the first handful of paragraphs feel like handwaving. Consider: &quot;When I started on the Web, college students were a majority of the population on the net. Today theyâ€™re probably less than 10%, and are vastly outnumbered by senior citizens.&quot;  When I read that, I thought: &quot;Care to cite a source?&quot;
I feel like the first 5 paragraphs are &#039;fluffy&#039; - they&#039;re not adding a whole lot of value, and they&#039;re making the same (or similar) points over and over again. Could you try cutting it down by half?
 I am such a minority case that it&#039;s not even funny, but I found your comment about buying JAWS and surfing with the monitor off extremely amusing, and this is no reflection on what you wrote.  I&#039;m profoundly hearing impaired, so for me to test my pages for accessibility, I have to turn on my  screen reader, &lt;i&gt;and&lt;/i&gt; turn on voice captioning to read what the computer is saying to me.  Clumsy as it is, it works though.


Elliotte, in this book, are you making any recommendations about having access to Windows, Linux, and OS X as part of the development process (for testing layouts)?  If so, then it may be useful to indicate that on OS X, you have access to built-in screen-reading software that works rather well (and is far cheaper than a JAWS license -- heck, for the price of JAWS, you could pick up a Mac Mini for browser testing and get the screen reader for free!)</description>
		<content:encoded><![CDATA[<p>Not bad; it&#8217;s a good start. Some points for consideration:</p>
<p>Some of the language in the first handful of paragraphs feel like handwaving. Consider: &#8220;When I started on the Web, college students were a majority of the population on the net. Today theyâ€™re probably less than 10%, and are vastly outnumbered by senior citizens.&#8221;  When I read that, I thought: &#8220;Care to cite a source?&#8221;<br />
I feel like the first 5 paragraphs are &#8216;fluffy&#8217; &#8211; they&#8217;re not adding a whole lot of value, and they&#8217;re making the same (or similar) points over and over again. Could you try cutting it down by half?<br />
 I am such a minority case that it&#8217;s not even funny, but I found your comment about buying JAWS and surfing with the monitor off extremely amusing, and this is no reflection on what you wrote.  I&#8217;m profoundly hearing impaired, so for me to test my pages for accessibility, I have to turn on my  screen reader, <i>and</i> turn on voice captioning to read what the computer is saying to me.  Clumsy as it is, it works though.</p>
<p>Elliotte, in this book, are you making any recommendations about having access to Windows, Linux, and OS X as part of the development process (for testing layouts)?  If so, then it may be useful to indicate that on OS X, you have access to built-in screen-reading software that works rather well (and is far cheaper than a JAWS license &#8212; heck, for the price of JAWS, you could pick up a Mac Mini for browser testing and get the screen reader for free!)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

