<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Accessibility Evaluators Aren&#8217;t Worthless</title>
	<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/</link>
	<description>The Art of Accessibility</description>
	<pubDate>Sat, 17 May 2008 02:49:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Simosito</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2553</link>
		<pubDate>Mon, 12 May 2008 13:26:07 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2553</guid>
					<description>I use F.A.E () and it is different from the others.
Maybe it is the future of validators.</description>
		<content:encoded><![CDATA[<p>I use F.A.E () and it is different from the others.<br />
Maybe it is the future of validators.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tim Harshbarger</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2551</link>
		<pubDate>Sat, 10 May 2008 17:36:20 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2551</guid>
					<description>I know that there is a concern about developers misusing evaluation tools to certify the accesibility of a site.  However, I think there is an assumption that accessibility claims were or are important to people using a site.  I don't think users have ever paid that much attention to accessibility claims.  I expect most of them have little or no familiarity with accessibility guidelines and standards.  I expect most people judge a site's commitment to accessibility through personal experience.
The tools can add value in ensuring that people do have a positive accessible experience with a site, but I am uncertain misuse of the tools to make outrageous claims of accessibility negatively impact users that much.</description>
		<content:encoded><![CDATA[<p>I know that there is a concern about developers misusing evaluation tools to certify the accesibility of a site.  However, I think there is an assumption that accessibility claims were or are important to people using a site.  I don&#8217;t think users have ever paid that much attention to accessibility claims.  I expect most of them have little or no familiarity with accessibility guidelines and standards.  I expect most people judge a site&#8217;s commitment to accessibility through personal experience.<br />
The tools can add value in ensuring that people do have a positive accessible experience with a site, but I am uncertain misuse of the tools to make outrageous claims of accessibility negatively impact users that much.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Zemens - 1955 Design</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2541</link>
		<pubDate>Wed, 07 May 2008 13:41:39 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2541</guid>
					<description>I certainly understand the need to manually investigate each checklist warning to assure full compliance.  No question about it.

As a fledgling web developer who is striving to do things the right way, a tool such as Cynthia gives me confidence that I am on the right track.  I confess to not manually checking each warning.  For the moment, I am just happy that I can generally achieve compliance with the automated validation.  I suppose this is the first step to reaching a higher level, but I still have a long way to go.

Great article and great comments!</description>
		<content:encoded><![CDATA[<p>I certainly understand the need to manually investigate each checklist warning to assure full compliance.  No question about it.</p>
<p>As a fledgling web developer who is striving to do things the right way, a tool such as Cynthia gives me confidence that I am on the right track.  I confess to not manually checking each warning.  For the moment, I am just happy that I can generally achieve compliance with the automated validation.  I suppose this is the first step to reaching a higher level, but I still have a long way to go.</p>
<p>Great article and great comments!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dave Woods - HTML, CSS, Web Design &#187; Useful Web Development Links (7th May 2008)</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2540</link>
		<pubDate>Wed, 07 May 2008 08:02:56 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2540</guid>
					<description>[...] Accessibility Evaluators Aren’t Worthless [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Accessibility Evaluators Aren’t Worthless [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dave Woods</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2539</link>
		<pubDate>Wed, 07 May 2008 07:45:12 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2539</guid>
					<description>Hi Mike, I completely agree and I follow exactly the same approach as you in that Cynthia is great as a first step to check that there are no glaringly obvious problems with a site. It's also obviously important that web developers understand that if they want their site to be accessible then they should have an in-depth understanding of the WAI Guidelines and not simply rely on tools like Cynthia as a be all and end all solution.

It's also probably worth mentioning that another useful "tool" towards accessibility validation is disabling images, CSS JavaScript independently of each other as well as any combination of the three. It's not a tool so to speak but is another free and easy way to help spot any accessibility issues.</description>
		<content:encoded><![CDATA[<p>Hi Mike, I completely agree and I follow exactly the same approach as you in that Cynthia is great as a first step to check that there are no glaringly obvious problems with a site. It&#8217;s also obviously important that web developers understand that if they want their site to be accessible then they should have an in-depth understanding of the WAI Guidelines and not simply rely on tools like Cynthia as a be all and end all solution.</p>
<p>It&#8217;s also probably worth mentioning that another useful &#8220;tool&#8221; towards accessibility validation is disabling images, CSS JavaScript independently of each other as well as any combination of the three. It&#8217;s not a tool so to speak but is another free and easy way to help spot any accessibility issues.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Cherim</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2538</link>
		<pubDate>Wed, 07 May 2008 03:20:05 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2538</guid>
					<description>@John: Gez's analyzer's on our list, at least the site version. I have the add-on for Firefox too. It's awesome. As far as the other, I've heard of neither, and both are cool. The IBM tool aDesigner looks like some very helpful software what with its simulations (no blind empathy there), and Total Validator... the name says it all, even spelling. I like it. Thank you very much for sharing them. They have been added to our ever-growing list.</description>
		<content:encoded><![CDATA[<p>@John: Gez&#8217;s analyzer&#8217;s on our list, at least the site version. I have the add-on for Firefox too. It&#8217;s awesome. As far as the other, I&#8217;ve heard of neither, and both are cool. The IBM tool aDesigner looks like some very helpful software what with its simulations (no blind empathy there), and Total Validator&#8230; the name says it all, even spelling. I like it. Thank you very much for sharing them. They have been added to our ever-growing list.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Faulds</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2537</link>
		<pubDate>Tue, 06 May 2008 22:45:33 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2537</guid>
					<description>It seems one of the tools I use most often is missing from your list Mike: &lt;a href="http://www.totalvalidator.com/" rel="nofollow"&gt;Total Validator&lt;/a&gt;. I don't use Cynthia but I'm guessing that Total Validator picks up the same sorts of mistakes that Cynthia does. I also find Gez Lemon's Colour Contrast Analyser extension for Firefox quite useful for pointing out when I haven't specified background-colors when using background-images. Another I use quite often is IBM's &lt;a href="http://www.alphaworks.ibm.com/tech/adesigner" rel="nofollow"&gt;aDesigner&lt;/a&gt; which also seems to be missing from your list of resources.</description>
		<content:encoded><![CDATA[<p>It seems one of the tools I use most often is missing from your list Mike: <a href="http://www.totalvalidator.com/" rel="nofollow">Total Validator</a>. I don&#8217;t use Cynthia but I&#8217;m guessing that Total Validator picks up the same sorts of mistakes that Cynthia does. I also find Gez Lemon&#8217;s Colour Contrast Analyser extension for Firefox quite useful for pointing out when I haven&#8217;t specified background-colors when using background-images. Another I use quite often is IBM&#8217;s <a href="http://www.alphaworks.ibm.com/tech/adesigner" rel="nofollow">aDesigner</a> which also seems to be missing from your list of resources.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Cherim</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2536</link>
		<pubDate>Tue, 06 May 2008 20:01:55 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2536</guid>
					<description>I've ignored them before too, knowing something wasn't an issue even though the validator did. Usually though I can find the cause which is sometimes valuable as well.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve ignored them before too, knowing something wasn&#8217;t an issue even though the validator did. Usually though I can find the cause which is sometimes valuable as well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mel Pedley</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2535</link>
		<pubDate>Tue, 06 May 2008 19:41:05 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2535</guid>
					<description>&lt;blockquote cite="Craig"&gt;It is possible that unscrupulous developers can use these tools to put a stamp of authority on a shoddy website. However, it will still be promoting accessibility as “a good thing” and that developer will be encouraged to update their skills.&lt;/blockquote&gt;

I'm not so sure. A stamp of authority only has real value when it can be trusted. If people persist in using these badges on sites that patently &lt;strong&gt;don't&lt;/strong&gt; achieve the levels of compliance stated, it is the badge/level that becomes ultimately devalued. Developers have to be wary of just ticking boxes and satisfying dumb accessibility parsing tools. 

Don't get me wrong. like yourself and Mike, I find these tools are really helpful in highlighting potential issues or errors but I reserve the right to disagree with them, or even ignore them completely in some circumstances. The final arbiters have to be the appropriate guidelines and the users themselves.  

The tools are simply a means to an end. Not The End.</description>
		<content:encoded><![CDATA[<blockquote cite="Craig"><p>It is possible that unscrupulous developers can use these tools to put a stamp of authority on a shoddy website. However, it will still be promoting accessibility as “a good thing” and that developer will be encouraged to update their skills.</p></blockquote>
<p>I&#8217;m not so sure. A stamp of authority only has real value when it can be trusted. If people persist in using these badges on sites that patently <strong>don&#8217;t</strong> achieve the levels of compliance stated, it is the badge/level that becomes ultimately devalued. Developers have to be wary of just ticking boxes and satisfying dumb accessibility parsing tools. </p>
<p>Don&#8217;t get me wrong. like yourself and Mike, I find these tools are really helpful in highlighting potential issues or errors but I reserve the right to disagree with them, or even ignore them completely in some circumstances. The final arbiters have to be the appropriate guidelines and the users themselves.  </p>
<p>The tools are simply a means to an end. Not The End.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Craig</title>
		<link>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2533</link>
		<pubDate>Tue, 06 May 2008 14:34:13 +0000</pubDate>
		<guid>http://accessites.org/site/2008/05/accessibility-evaluators-arent-worthless/#comment-2533</guid>
					<description>I use accessibility tools such as Cythia, but only to double-check that I've not made fundamental coding errors. After all, it's possible to make a site that passes evaluation, but couldn't really be considered accessible.

It is possible that unscrupulous developers can use these tools to put a stamp of authority on a shoddy website. However, it will still be promoting accessibility as "a good thing" and that developer will be encouraged to update their skills.</description>
		<content:encoded><![CDATA[<p>I use accessibility tools such as Cythia, but only to double-check that I&#8217;ve not made fundamental coding errors. After all, it&#8217;s possible to make a site that passes evaluation, but couldn&#8217;t really be considered accessible.</p>
<p>It is possible that unscrupulous developers can use these tools to put a stamp of authority on a shoddy website. However, it will still be promoting accessibility as &#8220;a good thing&#8221; and that developer will be encouraged to update their skills.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
