<?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: Target Lawsuit: Settlement Reached</title>
	<atom:link href="http://www.joedolson.com/articles/2008/08/target-lawsuit-settlement-reached/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2008/08/target-lawsuit-settlement-reached/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Wed, 07 Jan 2009 11:30:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/08/target-lawsuit-settlement-reached/comment-page-1/#comment-26711</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Thu, 28 Aug 2008 14:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=304#comment-26711</guid>
		<description>Thanks, Bruce! Yeah, that's a serious limitation to the settlement. I fail to understand why using a well-understood and standardized set of accessibility guidelines didn't make it into the settlement...it inevitably makes me concerned that they'll instead follow some bastardized set of rules. They may even create a whole new initialism for it!

Perhaps something like "TOATG."

There are definitely some odd requirements in that document.</description>
		<content:encoded><![CDATA[<p>Thanks, Bruce! Yeah, that&#8217;s a serious limitation to the settlement. I fail to understand why using a well-understood and standardized set of accessibility guidelines didn&#8217;t make it into the settlement&#8230;it inevitably makes me concerned that they&#8217;ll instead follow some bastardized set of rules. They may even create a whole new initialism for it!</p>
<p>Perhaps something like &#8220;TOATG.&#8221;</p>
<p>There are definitely some odd requirements in that&nbsp;document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bruce</title>
		<link>http://www.joedolson.com/articles/2008/08/target-lawsuit-settlement-reached/comment-page-1/#comment-26706</link>
		<dc:creator>bruce</dc:creator>
		<pubDate>Thu, 28 Aug 2008 08:03:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=304#comment-26706</guid>
		<description>The other problem is that the settlement only really mentions screenreader accessibility. And there are some reasonable guidelines laid out for Target to follow (with a bizarre construct for within-page links &#60;span style=”postion:absolute;”&#62;&#60;a name=”skiptocontent”&#62;&#160;&#60;/a&#62;&#60;/span&#62; because of an IE bug), but setting WCAG 1.0 as the benchmark would have been much better. And seemingly no mention of accessibility for other groups at all.

(I've written my  thoughts on my work blog)</description>
		<content:encoded><![CDATA[<p>The other problem is that the settlement only really mentions screenreader accessibility. And there are some reasonable guidelines laid out for Target to follow (with a bizarre construct for within-page links &lt;span style=”postion:absolute;”&gt;&lt;a name=”skiptocontent”&gt;&nbsp;&lt;/a&gt;&lt;/span&gt; because of an <acronym title="Internet Explorer">IE</acronym> bug), but setting <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> 1.0 as the benchmark would have been much better. And seemingly no mention of accessibility for other groups at all.</p>
<p>(I&#8217;ve written my  thoughts on my work&nbsp;blog)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/08/target-lawsuit-settlement-reached/comment-page-1/#comment-26701</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 27 Aug 2008 22:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=304#comment-26701</guid>
		<description>It has, on the other hand, equally demonstrated that it requires a very expensive law suit and several years to gain the awarding of damages, without any indication of long-term gain. 

I &lt;em&gt;am&lt;/em&gt; optimistic, and hope that the issue will be brought into law sooner rather than later, but can't help but look at the more problematic issues of the present, too...

Thanks for stopping by, Mike!</description>
		<content:encoded><![CDATA[<p>It has, on the other hand, equally demonstrated that it requires a very expensive law suit and several years to gain the awarding of damages, without any indication of long-term gain. </p>
<p>I <em>am</em> optimistic, and hope that the issue will be brought into law sooner rather than later, but can&#8217;t help but look at the more problematic issues of the present, too&#8230;</p>
<p>Thanks for stopping by,&nbsp;Mike!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.joedolson.com/articles/2008/08/target-lawsuit-settlement-reached/comment-page-1/#comment-26698</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Wed, 27 Aug 2008 21:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=304#comment-26698</guid>
		<description>No precedent set, but there was in the awarding of damages. Thus, it will come up again, next time. Though hopefully next time something will become law.</description>
		<content:encoded><![CDATA[<p>No precedent set, but there was in the awarding of damages. Thus, it will come up again, next time. Though hopefully next time something will become&nbsp;law.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
