<?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"
	>
<channel>
	<title>Comments on: Usability heuristics for web development teams</title>
	<atom:link href="http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Fri, 21 Nov 2008 08:02:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: mooj</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-632674</link>
		<dc:creator>mooj</dc:creator>
		<pubDate>Tue, 12 Feb 2008 00:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-632674</guid>
		<description>I would have never considered incorporating a favicon as part usability of a website! Some good points here and arguments aside, I will now be making much more use of this 16x16 space.. and pixel by pixel editing! :)</description>
		<content:encoded><![CDATA[<p>I would have never considered incorporating a favicon as part usability of a website! Some good points here and arguments aside, I will now be making much more use of this 16&#215;16 space.. and pixel by pixel editing! :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: stevebaty</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-161645</link>
		<dc:creator>stevebaty</dc:creator>
		<pubDate>Wed, 24 Jan 2007 01:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-161645</guid>
		<description>This discussion (in the comments) falls broadly into my category of 'where to draw the line between usability and user experience'. Keeping in mind that these are usability heuristics, I think this becomes an important distinguishing factor when deciding whether additional dimensions might be added to the list. Is information findability a usability consideration? Certainly within a site it is, but less so when you're considering how easy the site is to locate on the Web. 

Around the boundaries of usability there are a great deal of ambiquities as to whether a particular issue is related to usability or something else. I would not expend too much energy attempting to determine a definitive list of attributes that are/are not usability concerns. The scope of your heuristic checklist would (and should) be adjusted to meet the terms of enquiry for the evaluation. As Lisa has pointed out, there are considerations below the surface of the presentation layer which affect usability and are available to us for evaluation, and this is a valuable starting point for creating an extended heuristic checklist. Similarly, there are considerations beyond the bounds of the target web site which affect the user's experience with that site, and might also be included in an heuristic review.</description>
		<content:encoded><![CDATA[<p>This discussion (in the comments) falls broadly into my category of &#8216;where to draw the line between usability and user experience&#8217;. Keeping in mind that these are usability heuristics, I think this becomes an important distinguishing factor when deciding whether additional dimensions might be added to the list. Is information findability a usability consideration? Certainly within a site it is, but less so when you&#8217;re considering how easy the site is to locate on the Web. </p>
<p>Around the boundaries of usability there are a great deal of ambiquities as to whether a particular issue is related to usability or something else. I would not expend too much energy attempting to determine a definitive list of attributes that are/are not usability concerns. The scope of your heuristic checklist would (and should) be adjusted to meet the terms of enquiry for the evaluation. As Lisa has pointed out, there are considerations below the surface of the presentation layer which affect usability and are available to us for evaluation, and this is a valuable starting point for creating an extended heuristic checklist. Similarly, there are considerations beyond the bounds of the target web site which affect the user&#8217;s experience with that site, and might also be included in an heuristic review.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Magain</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-161538</link>
		<dc:creator>Matthew Magain</dc:creator>
		<pubDate>Tue, 23 Jan 2007 22:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-161538</guid>
		<description>Why draw the line at browser usability and say "that's not my area"? Whether it's relating to the user finding your site amongst their 17 tabs, or using your site - what's the difference? If it improves the user experience, whether inside your direct area of responsibility or outside of it, and it takes a few seconds to implement, it seems worthwhile listing as a heuristic so that it doesn't get left out, don't you think?</description>
		<content:encoded><![CDATA[<p>Why draw the line at browser usability and say &#8220;that&#8217;s not my area&#8221;? Whether it&#8217;s relating to the user finding your site amongst their 17 tabs, or using your site - what&#8217;s the difference? If it improves the user experience, whether inside your direct area of responsibility or outside of it, and it takes a few seconds to implement, it seems worthwhile listing as a heuristic so that it doesn&#8217;t get left out, don&#8217;t you think?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mrsmiley</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-161511</link>
		<dc:creator>mrsmiley</dc:creator>
		<pubDate>Tue, 23 Jan 2007 21:28:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-161511</guid>
		<description>I'm with XraySierra, I dont get why its a usability feature.  It has absolutely nothing to do with the way people use your site, but everything to do with how they locate it in your bookmarks/favourites lists.  Arguably its a browser usability as it makes the tool (aka the browser) easier to use to find your site.

Implementing a favicon (or not implementing one) doesn't have any impact on how usable a site is when you are actually using it.  Only in discovering the site.

That does bring up an interesting point, why don't search engines put the favicon next to the search results?  If implementing one is such a big deal, it would encourage more sites to do so if they knew their sites would stand out from ones that didn't have one.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with XraySierra, I dont get why its a usability feature.  It has absolutely nothing to do with the way people use your site, but everything to do with how they locate it in your bookmarks/favourites lists.  Arguably its a browser usability as it makes the tool (aka the browser) easier to use to find your site.</p>
<p>Implementing a favicon (or not implementing one) doesn&#8217;t have any impact on how usable a site is when you are actually using it.  Only in discovering the site.</p>
<p>That does bring up an interesting point, why don&#8217;t search engines put the favicon next to the search results?  If implementing one is such a big deal, it would encourage more sites to do so if they knew their sites would stand out from ones that didn&#8217;t have one.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Mackie</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-160965</link>
		<dc:creator>Simon Mackie</dc:creator>
		<pubDate>Tue, 23 Jan 2007 06:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-160965</guid>
		<description>XraySierra- it doesn't, it's a usability feature.</description>
		<content:encoded><![CDATA[<p>XraySierra- it doesn&#8217;t, it&#8217;s a usability feature.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: XraySierra</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-160947</link>
		<dc:creator>XraySierra</dc:creator>
		<pubDate>Tue, 23 Jan 2007 05:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-160947</guid>
		<description>I don't understand what a favicon would have to do with site accessibility?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand what a favicon would have to do with site accessibility?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: saumendra</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-160885</link>
		<dc:creator>saumendra</dc:creator>
		<pubDate>Tue, 23 Jan 2007 02:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-160885</guid>
		<description>The &lt;a href="http://www.useit.com/papers/heuristic/heuristic_list.html" rel="nofollow"&gt;Ten Usability Heuristics &lt;/a&gt;by Jacob Nielson , is a basic design rule for everyone out there, who need to have his/her website in a world wide standard. Now the Design Rules can be utilised smartly with the client side coding i.e javascript. But one can’t force the same as such.In a wider perspective the web needs more of global and unique usability components, which can be accessible by any form of data/content and yet be simple.

Even the Usabilit week 2007 Confrence does make that passion alive. And the results it had shown makes us to think and wait for the comming standards

There is allways more to explore……. Saum</description>
		<content:encoded><![CDATA[<p>The <a href="http://www.useit.com/papers/heuristic/heuristic_list.html" rel="nofollow">Ten Usability Heuristics </a>by Jacob Nielson , is a basic design rule for everyone out there, who need to have his/her website in a world wide standard. Now the Design Rules can be utilised smartly with the client side coding i.e javascript. But one can’t force the same as such.In a wider perspective the web needs more of global and unique usability components, which can be accessible by any form of data/content and yet be simple.</p>
<p>Even the Usabilit week 2007 Confrence does make that passion alive. And the results it had shown makes us to think and wait for the comming standards</p>
<p>There is allways more to explore……. Saum</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mrsmiley</title>
		<link>http://www.sitepoint.com/blogs/2007/01/21/usability-heuristics-for-web-developent-teams/#comment-160303</link>
		<dc:creator>mrsmiley</dc:creator>
		<pubDate>Mon, 22 Jan 2007 05:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1840#comment-160303</guid>
		<description>Considering there is a whole industry devoted to HCI, it's a wonder there isn't a definitive set of rules for web development.  Although, if you look at every area that "web development" covers, said list would be around 1 km long once it came out the printer.

The joys of working in an industry and almost requires you to be an expert in everything.  Well, at least the ones that can be abbreviated to an acronym that is pronounced nothing like its spelt :)</description>
		<content:encoded><![CDATA[<p>Considering there is a whole industry devoted to HCI, it&#8217;s a wonder there isn&#8217;t a definitive set of rules for web development.  Although, if you look at every area that &#8220;web development&#8221; covers, said list would be around 1 km long once it came out the printer.</p>
<p>The joys of working in an industry and almost requires you to be an expert in everything.  Well, at least the ones that can be abbreviated to an acronym that is pronounced nothing like its spelt :)</p>]]></content:encoded>
	</item>
</channel>
</rss>
