<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: NFB Makes a Deal with Amazon</title>
	<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/</link>
	<description>Raising the awareness of Web Site Accessibility and Marketing.</description>
	<pubDate>Sun, 20 Jul 2008 14:11:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Deals &#38; Discounts</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-277660</link>
		<dc:creator>Deals &#38; Discounts</dc:creator>
		<pubDate>Thu, 29 May 2008 15:51:48 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-277660</guid>
		<description>Everything is possible nowadays and we shouldn't be afraid to use the technology that serves our needs as it should be, but of course we should not forget that technology does not rule our lives.</description>
		<content:encoded><![CDATA[<p>Everything is possible nowadays and we shouldn&#8217;t be afraid to use the technology that serves our needs as it should be, but of course we should not forget that technology does not rule our lives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: didier_quelle</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-122711</link>
		<dc:creator>didier_quelle</dc:creator>
		<pubDate>Sun, 23 Sep 2007 15:47:07 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-122711</guid>
		<description>A friend of mine got injured and needed to rest his right hand for few months. I bought him a screen reading software and I can tell you he was more than happy...and he is not visually impaired! My point is: those assitive technologies can help everyone ...at any time!</description>
		<content:encoded><![CDATA[<p>A friend of mine got injured and needed to rest his right hand for few months. I bought him a screen reading software and I can tell you he was more than happy&#8230;and he is not visually impaired! My point is: those assitive technologies can help everyone &#8230;at any time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sailesh Panchang, Deque Systems</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-58219</link>
		<dc:creator>Sailesh Panchang, Deque Systems</dc:creator>
		<pubDate>Mon, 11 Jun 2007 14:01:38 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-58219</guid>
		<description>The introduction to WCAG 1.0 also  recognizes that making Web content accessible to one 
group of users often serves the interest of other users with disabilities. And that is quite 
true. Users of screen reading software require both input and output mediums to be made 
accessible and this benefits many many users who are not blind. 
For many other organizations  that need to be forced to incorporate accessibility into their 
Web content perhaps meeting the needs of non-visual access is a good first step. Certainly 
making content accessible to everyone should be the final goal.</description>
		<content:encoded><![CDATA[<p>The introduction to <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> 1.0 also  recognizes that making Web content accessible to one<br />
group of users often serves the interest of other users with disabilities. And that is quite<br />
true. Users of screen reading software require both input and output mediums to be made<br />
accessible and this benefits many many users who are not blind.<br />
For many other organizations  that need to be forced to incorporate accessibility into their<br />
Web content perhaps meeting the needs of non-visual access is a good first step. Certainly<br />
making content accessible to everyone should be the final goal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan B</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-45844</link>
		<dc:creator>Ryan B</dc:creator>
		<pubDate>Fri, 11 May 2007 22:12:39 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-45844</guid>
		<description>I think it is pretty funny that an image-only PDF was used. One thing think about is that there is the NFB, and they have the power to bring Target to court, but what about other disabilities. The only other group I can think about is UCP. So websites are given athumbs up after they pass for blind users, because there is not any major groups that say hey what about us?</description>
		<content:encoded><![CDATA[<p>I think it is pretty funny that an image-only <acronym title="Portable Document Format">PDF</acronym> was used. One thing think about is that there is the NFB, and they have the power to bring Target to court, but what about other disabilities. The only other group I can think about is UCP. So websites are given athumbs up after they pass for blind users, because there is not any major groups that say hey what about us?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Thatcher</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42810</link>
		<dc:creator>Jim Thatcher</dc:creator>
		<pubDate>Sun, 29 Apr 2007 19:30:52 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42810</guid>
		<description>Joe, I totally agree with you when you say: "It just isn’t fine for accessibility advocates to pretend that’s [sticking up for the blind, I think] enough."
But Matt said:
&lt;blockquote&gt;I think what you just advocated in the name of the NFB defeats the purpose of both the term and the concept itself.&lt;/blockquote&gt;

At no time have I said that I advocated just for blind access; I said the NFB did - and should. And by the way, I am not saying that amazon.com/access is good - for anything, especially accessibility. Just that I think the site was designed for mobile devices. I think alternative sites are a bad idea for many reasons.</description>
		<content:encoded><![CDATA[<p>Joe, I totally agree with you when you say: &#8220;It just isn’t fine for accessibility advocates to pretend that’s [sticking up for the blind, I think] enough.&#8221;<br />
But Matt said:</p>
<blockquote><p>I think what you just advocated in the name of the NFB defeats the purpose of both the term and the concept itself.</p></blockquote>
<p>At no time have I said that I advocated just for blind access; I said the NFB did - and should. And by the way, I am not saying that amazon.com/access is good - for anything, especially accessibility. Just that I think the site was designed for mobile devices. I think alternative sites are a bad idea for many reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42519</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Sat, 28 Apr 2007 15:07:57 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42519</guid>
		<description>If you want to go that far, Jim, then neither “screen reader” nor “screen-access software” adequately explains what’s happening when a Web &lt;em&gt;site&lt;/em&gt; is read.

Of course it’s fine and dandy for the NFB to stick up for the blind, despite their history of selectively doing so. It just isn’t fine for accessibility advocates to &lt;em&gt;pretend that’s enough&lt;/em&gt;.</description>
		<content:encoded><![CDATA[<p>If you want to go that far, Jim, then neither “screen reader” nor “screen-access software” adequately explains what’s happening when a Web <em>site</em> is read.</p>
<p>Of course it’s fine and dandy for the NFB to stick up for the blind, despite their history of selectively doing so. It just isn’t fine for accessibility advocates to <em>pretend that’s enough</em>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42394</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Sat, 28 Apr 2007 02:12:27 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42394</guid>
		<description>Although it's reasonable, I suppose, for the &lt;abbr title="national federation of the blind"&gt;NFB&lt;/abbr&gt; to &lt;em&gt;prioritize&lt;/em&gt; access for the blind, it seems more in the spirit of the organization to at least allow for consideration of other disabilities.  Granted, the issues experienced by the deaf aren't the "responsibility" of the NFB --- but website accessibility should always be considered to be a wider field than just improving the experiences of the blind.</description>
		<content:encoded><![CDATA[<p>Although it&#8217;s reasonable, I suppose, for the <abbr title="national federation of the blind">NFB</abbr> to <em>prioritize</em> access for the blind, it seems more in the spirit of the organization to at least allow for consideration of other disabilities.  Granted, the issues experienced by the deaf aren&#8217;t the &#8220;responsibility&#8221; of the NFB &#8212; but website accessibility should always be considered to be a wider field than just improving the experiences of the blind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Bailey</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42391</link>
		<dc:creator>Matt Bailey</dc:creator>
		<pubDate>Sat, 28 Apr 2007 01:33:30 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42391</guid>
		<description>Jim, I can even view Amazon.com on a mobile device.  It's tricky, and not fluid by any means, but I see what you mean.  Ideally, if sites were built for interoperability, would a seperate mobile site even be necessary?

Obviously, you and Joe Clark have a history and some strong opinions to go along with that.  However, I will always side with complete accessibility, and not just accessibility for one group of people.  I think what you just advocated in the name of the NFB defeats the purpose of both the term and the concept itself.  

Do you remember the criticism Google Accessible Search came under just last year because it was accessibility for blind users?  You can't focus on one group, leave the rest out, and still call it accessible. </description>
		<content:encoded><![CDATA[<p>Jim, I can even view Amazon.com on a mobile device.  It&#8217;s tricky, and not fluid by any means, but I see what you mean.  Ideally, if sites were built for interoperability, would a seperate mobile site even be necessary?</p>
<p>Obviously, you and Joe Clark have a history and some strong opinions to go along with that.  However, I will always side with complete accessibility, and not just accessibility for one group of people.  I think what you just advocated in the name of the NFB defeats the purpose of both the term and the concept itself.  </p>
<p>Do you remember the criticism Google Accessible Search came under just last year because it was accessibility for blind users?  You can&#8217;t focus on one group, leave the rest out, and still call it accessible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Thatcher</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42324</link>
		<dc:creator>Jim Thatcher</dc:creator>
		<pubDate>Fri, 27 Apr 2007 18:46:47 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42324</guid>
		<description>Hi Matt. You mentioned, &lt;blockquote&gt;I could use Amazon.com on my mobile phone or any other device besides a browser if that were possible.&lt;/blockquote&gt; That is exactly what &lt;a href="http://amazon.com/access"&gt;amazon.com/access&lt;/a&gt; was designed for (I believe). 

And while I'm "here," contrary to Joe Clark's opinion, it is proper and sensible that the National Federation of the Blind advocate for access by blind people - that is where their expertise is and where their priorities lie.</description>
		<content:encoded><![CDATA[<p>Hi Matt. You mentioned,<br />
<blockquote>I could use Amazon.com on my mobile phone or any other device besides a browser if that were possible.</p></blockquote>
<p> That is exactly what <a href="http://amazon.com/access">amazon.com/access</a> was designed for (I believe). </p>
<p>And while I&#8217;m &#8220;here,&#8221; contrary to Joe Clark&#8217;s opinion, it is proper and sensible that the National Federation of the Blind advocate for access by blind people - that is where their expertise is and where their priorities lie.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Bailey</title>
		<link>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42154</link>
		<dc:creator>Matt Bailey</dc:creator>
		<pubDate>Thu, 26 Apr 2007 20:54:01 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2007/04/25/nfb-amazon-deal/#comment-42154</guid>
		<description>Jim, very good to know that - thank you very much for the education and the clarification on the terminology.</description>
		<content:encoded><![CDATA[<p>Jim, very good to know that - thank you very much for the education and the clarification on the terminology.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.256 seconds -->
