<?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: Google launches Accessibility Search</title>
	<atom:link href="http://mnteractive.com/archive/google-launches-accessibility-search/feed" rel="self" type="application/rss+xml" />
	<link>http://mnteractive.com/archive/google-launches-accessibility-search</link>
	<description>Minnesota's Interaction Design, Information Architecture, and User Experience Design Community</description>
	<lastBuildDate>Fri, 27 Apr 2012 22:37:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Darrel</title>
		<link>http://mnteractive.com/archive/google-launches-accessibility-search/comment-page-1#comment-1950</link>
		<dc:creator>Darrel</dc:creator>
		<pubDate>Tue, 01 Aug 2006 13:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/archive/google-launches-accessibility-search/#comment-1950</guid>
		<description>Thierry:

Good point. 

Paul:

Valid point, but completely separating accessible content is also an accessibility reducer, IMHO.</description>
		<content:encoded><![CDATA[<p>Thierry:</p>
<p>Good point. </p>
<p>Paul:</p>
<p>Valid point, but completely separating accessible content is also an accessibility reducer, IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Cantrell</title>
		<link>http://mnteractive.com/archive/google-launches-accessibility-search/comment-page-1#comment-1868</link>
		<dc:creator>Paul Cantrell</dc:creator>
		<pubDate>Sun, 23 Jul 2006 03:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/archive/google-launches-accessibility-search/#comment-1868</guid>
		<description>&lt;blockquote&gt; An icon/text could be placed next to search results that emphasize the screenreader-friendly pages and even a â€˜filter byâ€¦â€™ option to rank in the search results.&lt;/blockquote&gt;

Another feature in the search results -- and for every result? 

Guess what interface clutter does? Reduces accessibility!</description>
		<content:encoded><![CDATA[<blockquote><p> An icon/text could be placed next to search results that emphasize the screenreader-friendly pages and even a â€˜filter byâ€¦â€™ option to rank in the search results.</p></blockquote>
<p>Another feature in the search results &#8212; and for every result? </p>
<p>Guess what interface clutter does? Reduces accessibility!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry Koblentz</title>
		<link>http://mnteractive.com/archive/google-launches-accessibility-search/comment-page-1#comment-1861</link>
		<dc:creator>Thierry Koblentz</dc:creator>
		<pubDate>Fri, 21 Jul 2006 16:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/archive/google-launches-accessibility-search/#comment-1861</guid>
		<description>From your article:
&lt;blockquote cite=&quot;http://mnteractive.com/archive/google-launches-accessibility-search/&quot;&gt;So, is this a good thing? Well, if you are blind, and depend on a screen
reader, then yes, this is a nice addition to your web surfing tool kit.&lt;/blockquote&gt;

I think you&#039;re taking the same shortcut as they do.

From their FAQ page:
&lt;blockquote cite=&quot;http://labs.google.com/accessible/faq.html&quot;&gt;Google Accessible Search looks at a number of signals by examining the HTML
markup found on a web page. It tends to favor pages that degrade
gracefully --- pages with few visual distractions and pages that are likely
to render well with images turned off.&lt;/blockquote&gt;

&lt;blockquote cite=&quot;http://labs.google.com/accessible/faq.html&quot;&gt;Currently we take into account several factors, including a given page&#039;s
simplicity, how much visual imagery it carries and whether or not it&#039;s
primary purpose is immediately viable with keyboard navigation.&lt;/blockquote&gt;

&lt;blockquote cite=&quot;http://labs.google.com/accessible/faq.html&quot;&gt;Some of the basic recommendations on how to make a website more useable and
accessible include keeping Web pages easy to read, avoiding visual
clutter -- especially extraneous content -- and ensuring that the primary
purpose of the Web page is immediately accessible with full keyboard
navigation&lt;/blockquote&gt;

IMHO, their tool/filter takes into consideration many more issues than just sight impairment.
I think the &quot;problem&quot; is that they made a too narrow claim ;-)</description>
		<content:encoded><![CDATA[<p>From your article:</p>
<blockquote cite="http://mnteractive.com/archive/google-launches-accessibility-search/"><p>So, is this a good thing? Well, if you are blind, and depend on a screen<br />
reader, then yes, this is a nice addition to your web surfing tool kit.</p></blockquote>
<p>I think you&#8217;re taking the same shortcut as they do.</p>
<p>From their FAQ page:</p>
<blockquote cite="http://labs.google.com/accessible/faq.html"><p>Google Accessible Search looks at a number of signals by examining the HTML<br />
markup found on a web page. It tends to favor pages that degrade<br />
gracefully &#8212; pages with few visual distractions and pages that are likely<br />
to render well with images turned off.</p></blockquote>
<blockquote cite="http://labs.google.com/accessible/faq.html"><p>Currently we take into account several factors, including a given page&#8217;s<br />
simplicity, how much visual imagery it carries and whether or not it&#8217;s<br />
primary purpose is immediately viable with keyboard navigation.</p></blockquote>
<blockquote cite="http://labs.google.com/accessible/faq.html"><p>Some of the basic recommendations on how to make a website more useable and<br />
accessible include keeping Web pages easy to read, avoiding visual<br />
clutter &#8212; especially extraneous content &#8212; and ensuring that the primary<br />
purpose of the Web page is immediately accessible with full keyboard<br />
navigation</p></blockquote>
<p>IMHO, their tool/filter takes into consideration many more issues than just sight impairment.<br />
I think the &#8220;problem&#8221; is that they made a too narrow claim <img src='http://mnteractive.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

