<?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: 10 Tools for Evaluating Web Design Accessibility</title>
	<atom:link href="http://sixrevisions.com/web-standards/accessibility_testtools/feed/" rel="self" type="application/rss+xml" />
	<link>http://sixrevisions.com/web-standards/accessibility_testtools/</link>
	<description></description>
	<lastBuildDate>Sun, 20 May 2012 16:23:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Jack</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-131689</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Sun, 16 Oct 2011 22:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-131689</guid>
		<description>The EvalAccess site itself needs to be more user-friendly.  I tried to follow the data table guidelines for headers and rows but could not get my site to comply, so I just left it.

And I had to give a fake email address to post this.</description>
		<content:encoded><![CDATA[<p>The EvalAccess site itself needs to be more user-friendly.  I tried to follow the data table guidelines for headers and rows but could not get my site to comply, so I just left it.</p>
<p>And I had to give a fake email address to post this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Mifsud</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-117099</link>
		<dc:creator>Justin Mifsud</dc:creator>
		<pubDate>Thu, 01 Sep 2011 09:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-117099</guid>
		<description>Great post Jacob, Most commentators should note that your post is from 2008, hence the reason why you did not mention some tools (so its not your fault!). 

Tools come and go with time. I have recently written a post where I reviewed the web-based accessibility checking tools that are currently available. Check it out on: http://usabilitygeek.com/10-free-web-based-web-site-accessibility-evaluation-tools/

I am sure that in a couple of months, my list will need to be changed too :)</description>
		<content:encoded><![CDATA[<p>Great post Jacob, Most commentators should note that your post is from 2008, hence the reason why you did not mention some tools (so its not your fault!). </p>
<p>Tools come and go with time. I have recently written a post where I reviewed the web-based accessibility checking tools that are currently available. Check it out on: <a href="http://usabilitygeek.com/10-free-web-based-web-site-accessibility-evaluation-tools/" rel="nofollow">http://usabilitygeek.com/10-free-web-based-web-site-accessibility-evaluation-tools/</a></p>
<p>I am sure that in a couple of months, my list will need to be changed too :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darron Lachowsky</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-109507</link>
		<dc:creator>Darron Lachowsky</dc:creator>
		<pubDate>Fri, 15 Jul 2011 16:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-109507</guid>
		<description>Yet another issue is  video games are usually serious anyway with the key focus on mastering rather than amusement. Although, it comes with an entertainment element to keep the kids engaged, just about every game is frequently designed to work towards a specific experience or programs, such as mathematics or research. Thanks for your write-up.</description>
		<content:encoded><![CDATA[<p>Yet another issue is  video games are usually serious anyway with the key focus on mastering rather than amusement. Although, it comes with an entertainment element to keep the kids engaged, just about every game is frequently designed to work towards a specific experience or programs, such as mathematics or research. Thanks for your write-up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eleg</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-107137</link>
		<dc:creator>Eleg</dc:creator>
		<pubDate>Tue, 21 Jun 2011 09:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-107137</guid>
		<description>To evaluate images or website(&#039;s screencapture):
 http://news.softpedia.com/news/How-To-Install-the-Colorblind-Applet-on-GNOME-91323.shtml
 http://docs.gimp.org/en/gimp-display-filter-dialog.html#gimp-deficient-vision
 http://docs.gimp.org/en/gimp-display-filter-dialog.html#gimp-contrast-dialog</description>
		<content:encoded><![CDATA[<p>To evaluate images or website(&#8216;s screencapture):<br />
 <a href="http://news.softpedia.com/news/How-To-Install-the-Colorblind-Applet-on-GNOME-91323.shtml" rel="nofollow">http://news.softpedia.com/news/How-To-Install-the-Colorblind-Applet-on-GNOME-91323.shtml</a><br />
 <a href="http://docs.gimp.org/en/gimp-display-filter-dialog.html#gimp-deficient-vision" rel="nofollow">http://docs.gimp.org/en/gimp-display-filter-dialog.html#gimp-deficient-vision</a><br />
 <a href="http://docs.gimp.org/en/gimp-display-filter-dialog.html#gimp-contrast-dialog" rel="nofollow">http://docs.gimp.org/en/gimp-display-filter-dialog.html#gimp-contrast-dialog</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: templatebase</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-94530</link>
		<dc:creator>templatebase</dc:creator>
		<pubDate>Tue, 15 Mar 2011 14:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-94530</guid>
		<description>Good list I like it.

I&#039;m using &quot;Firefox Accessibility Extension&quot; for a while and I love it.

Keep up the good work!</description>
		<content:encoded><![CDATA[<p>Good list I like it.</p>
<p>I&#8217;m using &#8220;Firefox Accessibility Extension&#8221; for a while and I love it.</p>
<p>Keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristian Dorobantescu</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-79547</link>
		<dc:creator>Cristian Dorobantescu</dc:creator>
		<pubDate>Tue, 26 Oct 2010 13:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-79547</guid>
		<description>Good list! I wonder how many developers really pay attention to the usability/ accessibility of their sites.</description>
		<content:encoded><![CDATA[<p>Good list! I wonder how many developers really pay attention to the usability/ accessibility of their sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iza Bartosiewicz</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-77653</link>
		<dc:creator>Iza Bartosiewicz</dc:creator>
		<pubDate>Fri, 01 Oct 2010 00:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-77653</guid>
		<description>My favourite is WAVE and Firebug combination plus few other tools mentioned in this article. Fangs is also quite handy (www.standards-schmandards.com/fangs/). 

I&#039;ve recently installed Worldspace FireEyes (it works like a Firebug &#039;plug-in&#039;) but haven&#039;t had much time to road test it yet. On the surface, it looks like a comprehensive but complex inspection tool so it may not be appropriate for everyone. I think WAVE is still the best one, and highly recommended for people who are not web specialists.</description>
		<content:encoded><![CDATA[<p>My favourite is WAVE and Firebug combination plus few other tools mentioned in this article. Fangs is also quite handy (www.standards-schmandards.com/fangs/). </p>
<p>I&#8217;ve recently installed Worldspace FireEyes (it works like a Firebug &#8216;plug-in&#8217;) but haven&#8217;t had much time to road test it yet. On the surface, it looks like a comprehensive but complex inspection tool so it may not be appropriate for everyone. I think WAVE is still the best one, and highly recommended for people who are not web specialists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Axe</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-77111</link>
		<dc:creator>Web Axe</dc:creator>
		<pubDate>Sat, 25 Sep 2010 00:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-77111</guid>
		<description>Nice article. But as Jared mentioned above, WAVE is missing. A great one. http://wave.webaim.org</description>
		<content:encoded><![CDATA[<p>Nice article. But as Jared mentioned above, WAVE is missing. A great one. <a href="http://wave.webaim.org" rel="nofollow">http://wave.webaim.org</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-75921</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 11 Sep 2010 12:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-75921</guid>
		<description>@Jacob Gube  I have been doing accessibility assessments of websites for almost 10 years and I use several of these tools. This is a good summary but, in my opinion, you missed the best ones. The Wave Toolbar for Firefox http://wave.webaim.org/ is unique. It is accurate (few false positives), and precise at identifying issues in context. I then use Firebug to examine the offending code. I find this methodology far superior to most of the other tools. 

One additional correction. You recommend use of the Title attribute to help screen reader users. This is one of the most frequent misconceptions among developers that I see. The advice should read, &quot;Use the Title attribute for page titles and frame titles.&quot; Most screen reader users, using default settings, will not hear titles elsewhere. Titles are for supplemental information. They should not be used as a primary caption for links, images, etc.</description>
		<content:encoded><![CDATA[<p>@Jacob Gube  I have been doing accessibility assessments of websites for almost 10 years and I use several of these tools. This is a good summary but, in my opinion, you missed the best ones. The Wave Toolbar for Firefox <a href="http://wave.webaim.org/" rel="nofollow">http://wave.webaim.org/</a> is unique. It is accurate (few false positives), and precise at identifying issues in context. I then use Firebug to examine the offending code. I find this methodology far superior to most of the other tools. </p>
<p>One additional correction. You recommend use of the Title attribute to help screen reader users. This is one of the most frequent misconceptions among developers that I see. The advice should read, &#8220;Use the Title attribute for page titles and frame titles.&#8221; Most screen reader users, using default settings, will not hear titles elsewhere. Titles are for supplemental information. They should not be used as a primary caption for links, images, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Santosh Reddy Gayam</title>
		<link>http://sixrevisions.com/web-standards/accessibility_testtools/#comment-62247</link>
		<dc:creator>Santosh Reddy Gayam</dc:creator>
		<pubDate>Wed, 17 Mar 2010 05:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=175#comment-62247</guid>
		<description>This is a really good resource for Accessibility tools.
If there are any Accessibility tools offline to evaluate web applications it will be great. If anyone find any tools please share.
Knowledge Shared is Knowledge Gained.

Thanks once again</description>
		<content:encoded><![CDATA[<p>This is a really good resource for Accessibility tools.<br />
If there are any Accessibility tools offline to evaluate web applications it will be great. If anyone find any tools please share.<br />
Knowledge Shared is Knowledge Gained.</p>
<p>Thanks once again</p>
]]></content:encoded>
	</item>
</channel>
</rss>

