<?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 for UsabilityOne Blog</title>
	<atom:link href="http://blog.usabilityone.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.usabilityone.com</link>
	<description>Usability, design and technology</description>
	<lastBuildDate>Fri, 09 Jul 2010 15:33:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Forget Roger, where&#8217;s my mobile site? by Makayla Gonzalez</title>
		<link>http://blog.usabilityone.com/2010/05/forget-roger-wheres-my-mobile-site/comment-page-1/#comment-1731</link>
		<dc:creator>Makayla Gonzalez</dc:creator>
		<pubDate>Fri, 09 Jul 2010 15:33:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=472#comment-1731</guid>
		<description>Mobile browsers are still kind of crude if you compare it to the desktop browsers we use on PC.&#039;:~</description>
		<content:encoded><![CDATA[<p>Mobile browsers are still kind of crude if you compare it to the desktop browsers we use on PC.&#8217;:~</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on No hidden surprises in my shopping cart thanks by Puzzler World</title>
		<link>http://blog.usabilityone.com/2010/06/no-hidden-surprises-in-my-shopping-cart-thanks/comment-page-1/#comment-1056</link>
		<dc:creator>Puzzler World</dc:creator>
		<pubDate>Fri, 11 Jun 2010 17:17:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=505#comment-1056</guid>
		<description>[...] No hidden surprises in my shopping cart thanks &#124; UsabilityOne Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] No hidden surprises in my shopping cart thanks | UsabilityOne Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Checklists are useless. Really? 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>Comment on iPad meets user: UsabilityOne tests the iPad by jopas (Jussi Pasanen)</title>
		<link>http://blog.usabilityone.com/2010/05/ipad-meets-user-usabilityone-tests-the-ipad/comment-page-1/#comment-662</link>
		<dc:creator>jopas (Jussi Pasanen)</dc:creator>
		<pubDate>Thu, 27 May 2010 21:23:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=507#comment-662</guid>
		<description>RT &lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/owenhodda&quot;&gt;@owenhodda&lt;/a&gt; UsabilityOne&#039;s thoughts after two weeks with the iPad http://tinyurl.com/34rjry7</description>
		<content:encoded><![CDATA[<p>RT <a rel="nofollow" href="http://twitter.com/owenhodda">@owenhodda</a> UsabilityOne&#8217;s thoughts after two weeks with the iPad <a href="http://tinyurl.com/34rjry7" rel="nofollow">http://tinyurl.com/34rjry7</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Checklists are useless. Really? 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>Comment on Checklists are useless. Really? 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>
	<item>
		<title>Comment on Photo Friday: Unconventional conventional doors by Chris Gray</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-unconventional-conventional-doors/comment-page-1/#comment-151</link>
		<dc:creator>Chris Gray</dc:creator>
		<pubDate>Mon, 29 Mar 2010 02:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=283#comment-151</guid>
		<description>Myvan I take your point, in a restaurant this design would make perfect sense.  As ever context is so important.  I&#039;m not sure how many offices are as frantic as a restaurant kitchen, though.  I guess the design does offer user&#039;s options however I&#039;d be concerned that it would confuse people - should I push or pull?</description>
		<content:encoded><![CDATA[<p>Myvan I take your point, in a restaurant this design would make perfect sense.  As ever context is so important.  I&#8217;m not sure how many offices are as frantic as a restaurant kitchen, though.  I guess the design does offer user&#8217;s options however I&#8217;d be concerned that it would confuse people &#8211; should I push or pull?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Photo Friday: Unconventional conventional doors by Myvan</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-unconventional-conventional-doors/comment-page-1/#comment-137</link>
		<dc:creator>Myvan</dc:creator>
		<pubDate>Fri, 26 Mar 2010 04:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=283#comment-137</guid>
		<description>On second thought, I guess it is quite considerate of the designer to give both the &#039;pull&#039; and &#039;push&#039; options.</description>
		<content:encoded><![CDATA[<p>On second thought, I guess it is quite considerate of the designer to give both the &#8216;pull&#8217; and &#8216;push&#8217; options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Photo Friday: Unconventional conventional doors by Myvan</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-unconventional-conventional-doors/comment-page-1/#comment-136</link>
		<dc:creator>Myvan</dc:creator>
		<pubDate>Fri, 26 Mar 2010 04:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=283#comment-136</guid>
		<description>Hello Chris,

These doors are indeed well labelled and their design does seem strange. They remind me of restaurant kitchen doors, where the one on the left is for &#039;pushing out&#039; and the one on the right is for &#039;pushing &#039;in&#039;. That is, no one should have to &#039;pull&#039;, as they may not have their hands free to pull and no one should crash into anyone else if they use the wrong door, as the doors would only open one way.  

 Perhaps these were restaurant kitchen doors that have been converted and the &#039;pull&#039; handle added later? 

 In such a fast paced environment, you want those who are leaving/entering to be using a consistent door</description>
		<content:encoded><![CDATA[<p>Hello Chris,</p>
<p>These doors are indeed well labelled and their design does seem strange. They remind me of restaurant kitchen doors, where the one on the left is for &#8216;pushing out&#8217; and the one on the right is for &#8216;pushing &#8216;in&#8217;. That is, no one should have to &#8216;pull&#8217;, as they may not have their hands free to pull and no one should crash into anyone else if they use the wrong door, as the doors would only open one way.  </p>
<p> Perhaps these were restaurant kitchen doors that have been converted and the &#8216;pull&#8217; handle added later? </p>
<p> In such a fast paced environment, you want those who are leaving/entering to be using a consistent door</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is your homepage your homepage? by Chris Gray</title>
		<link>http://blog.usabilityone.com/2010/03/is-your-homepage-your-homepage/comment-page-1/#comment-75</link>
		<dc:creator>Chris Gray</dc:creator>
		<pubDate>Thu, 04 Mar 2010 23:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usabilityone.com/?p=218#comment-75</guid>
		<description>I think this has some interesting implications for the way that we undertake lab based user testing.  In the past we have generally started tasks on the homepage however your project may suggest that we could start tasks from the most common entry pages.  

How do you think this should influence our testing in the fuuture? Should we be starting users on Google with an explicit instruction to use a specific site?</description>
		<content:encoded><![CDATA[<p>I think this has some interesting implications for the way that we undertake lab based user testing.  In the past we have generally started tasks on the homepage however your project may suggest that we could start tasks from the most common entry pages.  </p>
<p>How do you think this should influence our testing in the fuuture? Should we be starting users on Google with an explicit instruction to use a specific site?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
