<?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: Checklists are useless. Really?</title>
	<atom:link href="http://blog.usabilityone.com/2010/05/checklists-are-useless-really/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.usabilityone.com/2010/05/checklists-are-useless-really/</link>
	<description>Usability, design and technology</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:26:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Emanuela Gorla</title>
		<link>http://blog.usabilityone.com/2010/05/checklists-are-useless-really/comment-page-1/#comment-651</link>
		<dc:creator>Emanuela Gorla</dc:creator>
		<pubDate>Fri, 28 May 2010 00:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=482#comment-651</guid>
		<description>I couldn’t agree more Vlad, the accessibility of websites cannot be assessed using automated testing tools. Understanding the issues that each checkpoint was written to address and the benefits that is meant to bring to users with disabilities is absolutely necessary to decide whether a website satisfies the checkpoint. Clearly, automated testing software cannot do that. 

However, in my opinion the origin of the problem does not lie in the fact that checkpoints are not an appropriate mean to evaluate the accessibility of websites. The origin of the problem is, again, that organisations do not understand the importance of accessibility and do not address it seriously.</description>
		<content:encoded><![CDATA[<p>I couldn’t agree more Vlad, the accessibility of websites cannot be assessed using automated testing tools. Understanding the issues that each checkpoint was written to address and the benefits that is meant to bring to users with disabilities is absolutely necessary to decide whether a website satisfies the checkpoint. Clearly, automated testing software cannot do that. </p>
<p>However, in my opinion the origin of the problem does not lie in the fact that checkpoints are not an appropriate mean to evaluate the accessibility of websites. The origin of the problem is, again, that organisations do not understand the importance of accessibility and do not address it seriously.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vlad Alexander</title>
		<link>http://blog.usabilityone.com/2010/05/checklists-are-useless-really/comment-page-1/#comment-648</link>
		<dc:creator>Vlad Alexander</dc:creator>
		<pubDate>Thu, 27 May 2010 20:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=482#comment-648</guid>
		<description>Many authoring tool vendors have implemented WCAG/Section 508 checklists into accessibility checking features. These checklists give content authors a false sense of accomplishment. The content author&#039;s focus is on doing anything that will pass the checkpoint test rather than real review of content for accessibility issues. Unfortunately, accessibility cannot be packaged into a neat set of automated tests. Let&#039;s take an example. A blank alternate text value will raise an error in accessibility checkers even if it is appropriate for the given image. And if an image contains practically any value for alternate text will cause the checkers to give a passing mark to the checkpoint even if it causes comprehension issues.</description>
		<content:encoded><![CDATA[<p>Many authoring tool vendors have implemented WCAG/Section 508 checklists into accessibility checking features. These checklists give content authors a false sense of accomplishment. The content author&#8217;s focus is on doing anything that will pass the checkpoint test rather than real review of content for accessibility issues. Unfortunately, accessibility cannot be packaged into a neat set of automated tests. Let&#8217;s take an example. A blank alternate text value will raise an error in accessibility checkers even if it is appropriate for the given image. And if an image contains practically any value for alternate text will cause the checkers to give a passing mark to the checkpoint even if it causes comprehension issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Barber</title>
		<link>http://blog.usabilityone.com/2010/05/checklists-are-useless-really/comment-page-1/#comment-631</link>
		<dc:creator>Gary Barber</dc:creator>
		<pubDate>Thu, 27 May 2010 01:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=482#comment-631</guid>
		<description>I can see where you are coming from with the checklists. And I agree in part.  However I have seen these checklists so abused and used as the definitive solution.  It would be to the point of 9/10 sites that have had the checklist applied have just glossed over most of the issues that are applicable and ticked them off. We all know the story -  If is just becomes to hard to do, the solution is simple, just tick it off - no one will know.  After all people using the accessibility components don&#039;t use web sites.  

Years ago the accessibility community pointed out that the checklist would be open to abuse.   And now I say that we have our evidence.   

Yes they are helpful in setting a direction and starting point.   But when the completion of the checklist is seen as all that is required you really have to question what is the point.  

I don&#039;t have the solution (yet) we need something, maybe a stronger peer review process, that can stop this wholesale checklist abuse.</description>
		<content:encoded><![CDATA[<p>I can see where you are coming from with the checklists. And I agree in part.  However I have seen these checklists so abused and used as the definitive solution.  It would be to the point of 9/10 sites that have had the checklist applied have just glossed over most of the issues that are applicable and ticked them off. We all know the story &#8211;  If is just becomes to hard to do, the solution is simple, just tick it off &#8211; no one will know.  After all people using the accessibility components don&#8217;t use web sites.  </p>
<p>Years ago the accessibility community pointed out that the checklist would be open to abuse.   And now I say that we have our evidence.   </p>
<p>Yes they are helpful in setting a direction and starting point.   But when the completion of the checklist is seen as all that is required you really have to question what is the point.  </p>
<p>I don&#8217;t have the solution (yet) we need something, maybe a stronger peer review process, that can stop this wholesale checklist abuse.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

