<?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: The sorry state of usability</title>
	<atom:link href="http://blog.keyes.us/2008/04/10/the-sorry-state-of-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.keyes.us/2008/04/10/the-sorry-state-of-usability/</link>
	<description></description>
	<lastBuildDate>Thu, 12 Feb 2009 17:04:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robin</title>
		<link>http://blog.keyes.us/2008/04/10/the-sorry-state-of-usability/comment-page-1/#comment-14236</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Fri, 11 Apr 2008 03:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/04/10/the-sorry-state-of-usability/#comment-14236</guid>
		<description>I think usability is something that&#039;s very often overlooked in favour of over-zealous adherence to tickbox web accessibility standards. Too many people fail to realise that &quot;accessibility&quot; in this particular context doesn&#039;t really mean that the site is accessible to the general user as a visitor experience. It&#039;s also surprising how many things can be easily overlooked by the tech savvy developer, things that I think are simple and obvious clearly aren&#039;t when I get a web novice to evaluate the site for me. As a simple example of a wider problem, on my homepage I used to have no &quot;Home&quot; menu button because I thought it was obvious and common practice that one could reach the homepage by clicking on the main logo...but that wasn&#039;t the case when it came to testing it with less experienced web users.</description>
		<content:encoded><![CDATA[<p>I think usability is something that&#8217;s very often overlooked in favour of over-zealous adherence to tickbox web accessibility standards. Too many people fail to realise that &#8220;accessibility&#8221; in this particular context doesn&#8217;t really mean that the site is accessible to the general user as a visitor experience. It&#8217;s also surprising how many things can be easily overlooked by the tech savvy developer, things that I think are simple and obvious clearly aren&#8217;t when I get a web novice to evaluate the site for me. As a simple example of a wider problem, on my homepage I used to have no &#8220;Home&#8221; menu button because I thought it was obvious and common practice that one could reach the homepage by clicking on the main logo&#8230;but that wasn&#8217;t the case when it came to testing it with less experienced web users.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
