<?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: Pleasing Jakob Nielsen, Part 1</title>
	<atom:link href="http://blog.webreakstuff.com/2005/10/usability-tips-part1/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/</link>
	<description>A blog on entrepreneurship, user experience, and web innovation. Published by Fred Oliveira.</description>
	<lastBuildDate>Tue, 13 Dec 2011 18:19:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Chris Peters Web Marketer &#187; Face it: you need bigger font</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-41057</link>
		<dc:creator>Chris Peters Web Marketer &#187; Face it: you need bigger font</dc:creator>
		<pubDate>Mon, 11 Jun 2007 20:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-41057</guid>
		<description>[...] Webreakstuff commented on Jakob Nielsen&#8217;s Top Ten Web Design Mistakes of 2005 a couple years ago. The number 1 usability mistake of 2005, according to Nielsen, was illegible font sizes. Two-thirds of users studied complained about font sizes being too small or frozen from being resized. [...]</description>
		<content:encoded><![CDATA[<p>[...] Webreakstuff commented on Jakob Nielsen&#8217;s Top Ten Web Design Mistakes of 2005 a couple years ago. The number 1 usability mistake of 2005, according to Nielsen, was illegible font sizes. Two-thirds of users studied complained about font sizes being too small or frozen from being resized. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Webdesign-Fehler und LÃƒÂ¶sungen &#8212; cne _LOG Archiv</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-5055</link>
		<dc:creator>&#187; Webdesign-Fehler und LÃƒÂ¶sungen &#8212; cne _LOG Archiv</dc:creator>
		<pubDate>Sat, 14 Oct 2006 14:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-5055</guid>
		<description>[...] Jakob Nielsen zeigt fast jÃƒÂ¤hrlich die 10 schlimmsten Webdesign-Fehler hinsichtlich Usability auf. Im letzten Jahr nahm sich Webreakstuff dieser Warnungen an und zeigte, wie man diese Probleme lÃƒÂ¶st bzw. sie gar nicht erst entstehen lÃƒÂ¤sst. [...]</description>
		<content:encoded><![CDATA[<p>[...] Jakob Nielsen zeigt fast jÃƒÂ¤hrlich die 10 schlimmsten Webdesign-Fehler hinsichtlich Usability auf. Im letzten Jahr nahm sich Webreakstuff dieser Warnungen an und zeigte, wie man diese Probleme lÃƒÂ¶st bzw. sie gar nicht erst entstehen lÃƒÂ¤sst. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ECTIO</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-709</link>
		<dc:creator>ECTIO</dc:creator>
		<pubDate>Thu, 13 Oct 2005 18:08:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-709</guid>
		<description>&lt;strong&gt;Pleasing Jakob Nielsen, Part 3&lt;/strong&gt;

So here we are, the final article on how to please Jakob Nielsen by not falling on any of the design mistakes of 2005 (part 1 and part 2 are also available). In this final article, I&#039;ll talk about contact information, liquid layouts and photo enlargem...</description>
		<content:encoded><![CDATA[<p><strong>Pleasing Jakob Nielsen, Part 3</strong></p>
<p>So here we are, the final article on how to please Jakob Nielsen by not falling on any of the design mistakes of 2005 (part 1 and part 2 are also available). In this final article, I&#8217;ll talk about contact information, liquid layouts and photo enlargem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: _In.pix.we.trust. &#187; Blog Archive &#187; TÃ³mate tu lechita</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-629</link>
		<dc:creator>_In.pix.we.trust. &#187; Blog Archive &#187; TÃ³mate tu lechita</dc:creator>
		<pubDate>Wed, 12 Oct 2005 03:13:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-629</guid>
		<description>[...] Pleasing Jakob Nielsen [Part 1] [Part 2] [Part 3] [...]</description>
		<content:encoded><![CDATA[<p>[...] Pleasing Jakob Nielsen [Part 1] [Part 2] [Part 3] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Voice Over IT &#187; Blog Archive &#187; Web2 e usabilita&#8217; dei siti: links&#8230;</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-605</link>
		<dc:creator>Voice Over IT &#187; Blog Archive &#187; Web2 e usabilita&#8217; dei siti: links&#8230;</dc:creator>
		<pubDate>Tue, 11 Oct 2005 07:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-605</guid>
		<description>[...] -&gt; Pleasing Jakob Nielsen, Part 1 -&gt; Pleasing Jakob Nielsen, Part 2 -&gt; Pleasing Jakob Nielsen, Part 3 [...]</description>
		<content:encoded><![CDATA[<p>[...] -&gt; Pleasing Jakob Nielsen, Part 1 -&gt; Pleasing Jakob Nielsen, Part 2 -&gt; Pleasing Jakob Nielsen, Part 3 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WeBreakStuff &#187; Pleasing Jakob Nielsen, Part 3</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-598</link>
		<dc:creator>WeBreakStuff &#187; Pleasing Jakob Nielsen, Part 3</dc:creator>
		<pubDate>Tue, 11 Oct 2005 05:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-598</guid>
		<description>[...] So here we are, the final article on how to please Jakob Nielsen by not falling on any of the design mistakes of 2005 (part 1 and part 2 are also available). In this final article, I&#8217;ll talk about contact information, liquid layouts and photo enlargement. Again, if you haven&#8217;t read Jakob&#8217;s post, read it first and come back here to see how to implement the tips. [...]</description>
		<content:encoded><![CDATA[<p>[...] So here we are, the final article on how to please Jakob Nielsen by not falling on any of the design mistakes of 2005 (part 1 and part 2 are also available). In this final article, I&#8217;ll talk about contact information, liquid layouts and photo enlargement. Again, if you haven&#8217;t read Jakob&#8217;s post, read it first and come back here to see how to implement the tips. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WeBreakStuff &#187; Pleasing Jacob Nielsen, Part 2</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-501</link>
		<dc:creator>WeBreakStuff &#187; Pleasing Jacob Nielsen, Part 2</dc:creator>
		<pubDate>Sat, 08 Oct 2005 18:41:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-501</guid>
		<description>[...] This is the second part of the &#8220;Pleasing Jacob Nielsen&#8221; series about how to use Jacob Nielsen&#8217;s Top Ten Design Mistakes for 2005 guidelines to get yourself a better website or blog. In the first article in the series we talked about font legibility, standard and non-standard links and flash usage. This one will go on into content, search, browser dependencies and getting data from your users. [...]</description>
		<content:encoded><![CDATA[<p>[...] This is the second part of the &#8220;Pleasing Jacob Nielsen&#8221; series about how to use Jacob Nielsen&#8217;s Top Ten Design Mistakes for 2005 guidelines to get yourself a better website or blog. In the first article in the series we talked about font legibility, standard and non-standard links and flash usage. This one will go on into content, search, browser dependencies and getting data from your users. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PELF</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-458</link>
		<dc:creator>PELF</dc:creator>
		<pubDate>Wed, 05 Oct 2005 17:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-458</guid>
		<description>As always, excellent advice with real examples. 

Thank you ;)</description>
		<content:encoded><![CDATA[<p>As always, excellent advice with real examples. </p>
<p>Thank you ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://blog.webreakstuff.com/2005/10/usability-tips-part1/comment-page-1/#comment-457</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Wed, 05 Oct 2005 14:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/?p=120#comment-457</guid>
		<description>I think that if a site has a clear demoographic of technical users, the relative importance of Jakob Nielsen&#039;s suggestions differ slightly.

With small font sizes, you are more likely to annoy, but less likely to render something unreadable.  This is  because, although the users are capable of fixing the problem by bumping up the font size, they are both more likely to change the defaults* and more likely to be using a high resolution where larger fonts are more important.

* e.g. my default font size is 1px smaller than the default, so somebody specifying 80% font size might well be readable at the default size, but not for me.

With link colours, you can rely on them being able to recognise underlined text as links more than the average user, so you don&#039;t need to -rely- on a different colour, but again, they are more likely to use the visited/non-visited differences than average users.

Good advice on the Flash/AJAX point, that&#039;s what I always say.  Use it when it&#039;s appropriate, don&#039;t use it for the sake of it.

As far as the length of lines is concerned, there&#039;s recent evidence that reading online doesn&#039;t match up with the line width rules for physical media.  I believe you can get a link to the survey from Joe Clark&#039;s weblog if memory serves me.</description>
		<content:encoded><![CDATA[<p>I think that if a site has a clear demoographic of technical users, the relative importance of Jakob Nielsen&#8217;s suggestions differ slightly.</p>
<p>With small font sizes, you are more likely to annoy, but less likely to render something unreadable.  This is  because, although the users are capable of fixing the problem by bumping up the font size, they are both more likely to change the defaults* and more likely to be using a high resolution where larger fonts are more important.</p>
<p>* e.g. my default font size is 1px smaller than the default, so somebody specifying 80% font size might well be readable at the default size, but not for me.</p>
<p>With link colours, you can rely on them being able to recognise underlined text as links more than the average user, so you don&#8217;t need to -rely- on a different colour, but again, they are more likely to use the visited/non-visited differences than average users.</p>
<p>Good advice on the Flash/AJAX point, that&#8217;s what I always say.  Use it when it&#8217;s appropriate, don&#8217;t use it for the sake of it.</p>
<p>As far as the length of lines is concerned, there&#8217;s recent evidence that reading online doesn&#8217;t match up with the line width rules for physical media.  I believe you can get a link to the survey from Joe Clark&#8217;s weblog if memory serves me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

