<?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 Usability Thoughts</title>
	<atom:link href="http://usabilitythoughts.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://usabilitythoughts.com</link>
	<description>content meets user</description>
	<lastBuildDate>Wed, 03 Mar 2010 16:01:08 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Links vs. buttons by Alex Key</title>
		<link>http://usabilitythoughts.com/links-vs-buttons.html/comment-page-1#comment-4125</link>
		<dc:creator>Alex Key</dc:creator>
		<pubDate>Wed, 03 Mar 2010 16:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=40#comment-4125</guid>
		<description>I agree, good points.

One thing to be mindful of is that buttons will be in the natural tab order of the page. Whilst links will not (in many cases), so will need a little extra work to enable keyboard navigation.</description>
		<content:encoded><![CDATA[<p>I agree, good points.</p>
<p>One thing to be mindful of is that buttons will be in the natural tab order of the page. Whilst links will not (in many cases), so will need a little extra work to enable keyboard navigation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Password requirements by Simon</title>
		<link>http://usabilitythoughts.com/password-requirements.html/comment-page-1#comment-3843</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sat, 06 Feb 2010 12:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=126#comment-3843</guid>
		<description>@Jacob - Wrong, &#039;newyorkcity&#039; is less secure than Pus9I34 in every way, teh first is not only open to dictionary attacks it also has fewer combinations.

@adrian - Putting a maximum limit on a pasword is not stupid, putting a vey small one is, but putting some sort of maximum on is sensible. 

As for making users use different characters, tough, users are the first to complain if their account gets hacked, but then when a users use &quot;1234&quot; or &quot;password&quot; for their accoutn what do they expect, unfortuantely some users need to be saved from their own stupidty.</description>
		<content:encoded><![CDATA[<p>@Jacob &#8211; Wrong, &#8216;newyorkcity&#8217; is less secure than Pus9I34 in every way, teh first is not only open to dictionary attacks it also has fewer combinations.</p>
<p>@adrian &#8211; Putting a maximum limit on a pasword is not stupid, putting a vey small one is, but putting some sort of maximum on is sensible. </p>
<p>As for making users use different characters, tough, users are the first to complain if their account gets hacked, but then when a users use &#8220;1234&#8243; or &#8220;password&#8221; for their accoutn what do they expect, unfortuantely some users need to be saved from their own stupidty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple things by JC</title>
		<link>http://usabilitythoughts.com/simple-things.html/comment-page-1#comment-3687</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Fri, 22 Jan 2010 19:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=187#comment-3687</guid>
		<description>It isn&#039;t a problem here in the USA. The bathroom switches are inside of the bathroom. If you&#039;re in the bathroom looking at the door, you&#039;ll find that the switch is pretty much always on the wall next to the door knob, but at standard switch height (about 8 - 12 inches higher than the door knob). 

Therefore it is always easy to find, and as Terry noted, you turn the light on as you enter and turn it off as you leave, so there is no problem to be solved here.

It&#039;s the same sort of setup for pretty much every room, and for the main entry into houses themselves. Switches are always on the inside.</description>
		<content:encoded><![CDATA[<p>It isn&#8217;t a problem here in the USA. The bathroom switches are inside of the bathroom. If you&#8217;re in the bathroom looking at the door, you&#8217;ll find that the switch is pretty much always on the wall next to the door knob, but at standard switch height (about 8 &#8211; 12 inches higher than the door knob). </p>
<p>Therefore it is always easy to find, and as Terry noted, you turn the light on as you enter and turn it off as you leave, so there is no problem to be solved here.</p>
<p>It&#8217;s the same sort of setup for pretty much every room, and for the main entry into houses themselves. Switches are always on the inside.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple things by Terry</title>
		<link>http://usabilitythoughts.com/simple-things.html/comment-page-1#comment-3685</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Fri, 22 Jan 2010 16:09:28 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=187#comment-3685</guid>
		<description>In Europe it is a little different than the US.  In the US, you turn the light switch &quot;on&quot; as you enter the bathroom (because the switch is located right on the wall, INSIDE the door).  

When you exit the bathroom, you turn the switch &quot;off&quot;.  That way, the light is only on when someone is using, or inside, the bathroom.  At all other times, the bathroom light is off...unless of course, you want to waste electricity!</description>
		<content:encoded><![CDATA[<p>In Europe it is a little different than the US.  In the US, you turn the light switch &#8220;on&#8221; as you enter the bathroom (because the switch is located right on the wall, INSIDE the door).  </p>
<p>When you exit the bathroom, you turn the switch &#8220;off&#8221;.  That way, the light is only on when someone is using, or inside, the bathroom.  At all other times, the bathroom light is off&#8230;unless of course, you want to waste electricity!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Drag &amp; Drop on the web by Adrian</title>
		<link>http://usabilitythoughts.com/drag-drop-on-the-web.html/comment-page-1#comment-3609</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Wed, 13 Jan 2010 20:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=182#comment-3609</guid>
		<description>in the first version of the grooveshark software there was a &quot;add to a playlist&quot; option on the song info page, so you can see why one is confused now.

i can see now the option in the selectors, but if you add the song to queue and search for another song there is no other way to add it from your queue. i guess you can say they have half of alternative :D</description>
		<content:encoded><![CDATA[<p>in the first version of the grooveshark software there was a &#8220;add to a playlist&#8221; option on the song info page, so you can see why one is confused now.</p>
<p>i can see now the option in the selectors, but if you add the song to queue and search for another song there is no other way to add it from your queue. i guess you can say they have half of alternative <img src='http://usabilitythoughts.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Drag &amp; Drop on the web by Ivan</title>
		<link>http://usabilitythoughts.com/drag-drop-on-the-web.html/comment-page-1#comment-3607</link>
		<dc:creator>Ivan</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=182#comment-3607</guid>
		<description>There are &quot;select boxes&quot; at the top of the page where you can replace current songs, add to your library or your playlist. But yeah, there should be hint for this operation, although many people could have predicted this since is one of the default operations in every modern OS.</description>
		<content:encoded><![CDATA[<p>There are &#8220;select boxes&#8221; at the top of the page where you can replace current songs, add to your library or your playlist. But yeah, there should be hint for this operation, although many people could have predicted this since is one of the default operations in every modern OS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You know&#8230; by frankux</title>
		<link>http://usabilitythoughts.com/you-know.html/comment-page-1#comment-3279</link>
		<dc:creator>frankux</dc:creator>
		<pubDate>Thu, 10 Dec 2009 06:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=91#comment-3279</guid>
		<description>Help pages are for everyone. I&#039;m an &#039;advanced user&#039; when it comes to software but a basic user when it comes to cooking a turkey.</description>
		<content:encoded><![CDATA[<p>Help pages are for everyone. I&#8217;m an &#8216;advanced user&#8217; when it comes to software but a basic user when it comes to cooking a turkey.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Form labels by Jüri</title>
		<link>http://usabilitythoughts.com/form-labels.html/comment-page-1#comment-3200</link>
		<dc:creator>Jüri</dc:creator>
		<pubDate>Sun, 15 Nov 2009 15:26:02 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=167#comment-3200</guid>
		<description>Hi. Good point. 

But certainly there is one good side to such method: it does not require labels which are usually *two, new type of items* for usual login box combination:

* username [txt input]
* password [pwd input]
* submit [button or image]
* forgot password? [link]

+ sometimes there are also:
* box title [title, hx tag]
* sign up! [link]

you see, this already consists of 4-6 elements (adding two would be quite a lot:) ) and 4-5 different types of elements (adding one would be quite a lot :) )

Also, I guess that everyone who sees this combination knows what the first and second input are for.

I just felt I needed to state the &quot;more minimalist view&quot; on this :)

(I just found your blog. +1 subscription to Reader)</description>
		<content:encoded><![CDATA[<p>Hi. Good point. </p>
<p>But certainly there is one good side to such method: it does not require labels which are usually *two, new type of items* for usual login box combination:</p>
<p>* username [txt input]<br />
* password [pwd input]<br />
* submit [button or image]<br />
* forgot password? [link]</p>
<p>+ sometimes there are also:<br />
* box title [title, hx tag]<br />
* sign up! [link]</p>
<p>you see, this already consists of 4-6 elements (adding two would be quite a lot:) ) and 4-5 different types of elements (adding one would be quite a lot <img src='http://usabilitythoughts.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  )</p>
<p>Also, I guess that everyone who sees this combination knows what the first and second input are for.</p>
<p>I just felt I needed to state the &#8220;more minimalist view&#8221; on this <img src='http://usabilitythoughts.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>(I just found your blog. +1 subscription to Reader)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Use search buttons by Adrian</title>
		<link>http://usabilitythoughts.com/use-search-buttons.html/comment-page-1#comment-3194</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=171#comment-3194</guid>
		<description>one reason: can be easily mistaken for a subscribe form. &quot;GO&quot; doesn&#039;t say anything about the action you&#039;re about to make.</description>
		<content:encoded><![CDATA[<p>one reason: can be easily mistaken for a subscribe form. &#8220;GO&#8221; doesn&#8217;t say anything about the action you&#8217;re about to make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Use search buttons by shellyc</title>
		<link>http://usabilitythoughts.com/use-search-buttons.html/comment-page-1#comment-3193</link>
		<dc:creator>shellyc</dc:creator>
		<pubDate>Fri, 13 Nov 2009 15:57:16 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=171#comment-3193</guid>
		<description>Any reason, arguments for the button being labeled &#039;search&#039; and not &#039;go&#039; other than just dont?</description>
		<content:encoded><![CDATA[<p>Any reason, arguments for the button being labeled &#8217;search&#8217; and not &#8216;go&#8217; other than just dont?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
