<?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: Why do passwords appear as dots in a form?</title>
	<atom:link href="http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/</link>
	<description>Articles &#38; Reviews on Web Design, User Experience and Usability</description>
	<lastBuildDate>Wed, 16 May 2012 08:06:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-13002</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Mon, 28 Nov 2011 15:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-13002</guid>
		<description>Hi Clive, thank you so much for making your point. I think that comments like these are a real eye-opener for all of us. I have to admit that many companies I have worked with value accessibility as a nice-to-have rather than a must-have because the necessary investments don&#039;t weigh up to the minimal increase of users.




Little do these companies know, literally! They seem to claim that their websites or applications aren&#039;t used by people with disabilities, so they don&#039;t need to pay attention to web accessibility. However, the tracked profile of a user with a disability is identical to anybody else using that browser.




Knowing that 18.7 percent of US citizens are disabled (according to a 2005 report from the United States Census Bureau), they should start right away!




I haven&#039;t found any metrics on the matter but I do believe that many, mostly governmental, instances are making the extra efford - although slowly - in optimizing their websites, (web) applications, ... but companies and others still have to follow their example.</description>
		<content:encoded><![CDATA[<p>Hi Clive, thank you so much for making your point. I think that comments like these are a real eye-opener for all of us. I have to admit that many companies I have worked with value accessibility as a nice-to-have rather than a must-have because the necessary investments don&#8217;t weigh up to the minimal increase of users.</p>
<p>Little do these companies know, literally! They seem to claim that their websites or applications aren&#8217;t used by people with disabilities, so they don&#8217;t need to pay attention to web accessibility. However, the tracked profile of a user with a disability is identical to anybody else using that browser.</p>
<p>Knowing that 18.7 percent of US citizens are disabled (according to a 2005 report from the United States Census Bureau), they should start right away!</p>
<p>I haven&#8217;t found any metrics on the matter but I do believe that many, mostly governmental, instances are making the extra efford &#8211; although slowly &#8211; in optimizing their websites, (web) applications, &#8230; but companies and others still have to follow their example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-12881</link>
		<dc:creator>Clive</dc:creator>
		<pubDate>Sat, 26 Nov 2011 08:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-12881</guid>
		<description>Hi, I don&#039;t know if this article/discussion is recent or archived but found it extremely interesting. A point that all your replies seem to be missing is how useful it would be for disabled people like me with poor dexterity (cerebral palsy) Jamie posed the question &quot;Is it really that hard to type a string of 8 to 13 characters correctly?&quot; Believe me Jamie for some of us its very difficult. I&#039;m forttunate enough to be able to type one finger. Others, my wife for example, co-ordination and use of hands so bad she can only type with the tip of her nose!! So anything that makes the process a bit easier is appreciated. 

(to make a point... this messaage has taken well over half hour to write and involved 32 corrections).</description>
		<content:encoded><![CDATA[<p>Hi, I don&#8217;t know if this article/discussion is recent or archived but found it extremely interesting. A point that all your replies seem to be missing is how useful it would be for disabled people like me with poor dexterity (cerebral palsy) Jamie posed the question &#8220;Is it really that hard to type a string of 8 to 13 characters correctly?&#8221; Believe me Jamie for some of us its very difficult. I&#8217;m forttunate enough to be able to type one finger. Others, my wife for example, co-ordination and use of hands so bad she can only type with the tip of her nose!! So anything that makes the process a bit easier is appreciated. </p>
<p>(to make a point&#8230; this messaage has taken well over half hour to write and involved 32 corrections).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Do we really need dots on a password field? &#124; marcomonteiro&#039;s &#8211; Blog</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-5573</link>
		<dc:creator>Do we really need dots on a password field? &#124; marcomonteiro&#039;s &#8211; Blog</dc:creator>
		<pubDate>Thu, 23 Dec 2010 13:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-5573</guid>
		<description>[...] never really thought about this until a while ago when i&#8217;ve come across with this article. And i was blown away that i&#8217;ve never thought this myself. Seriously, imagine that you have [...]</description>
		<content:encoded><![CDATA[<p>[...] never really thought about this until a while ago when i&#8217;ve come across with this article. And i was blown away that i&#8217;ve never thought this myself. Seriously, imagine that you have [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-4554</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Sat, 13 Nov 2010 10:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-4554</guid>
		<description>@&lt;a href=&quot;http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-4543&quot; rel=&quot;nofollow&quot;&gt;Marco Monteiro&lt;/a&gt;: You&#039;re most welcome Marco! Glad you liked it.</description>
		<content:encoded><![CDATA[<p>@<a href="http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-4543" rel="nofollow">Marco Monteiro</a>: You&#8217;re most welcome Marco! Glad you liked it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Monteiro</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-4543</link>
		<dc:creator>Marco Monteiro</dc:creator>
		<pubDate>Fri, 12 Nov 2010 22:58:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-4543</guid>
		<description>This is a really good article =) save me a lot of time with research... thanks mate..</description>
		<content:encoded><![CDATA[<p>This is a really good article =) save me a lot of time with research&#8230; thanks mate..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-517</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Mon, 11 Jan 2010 11:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-517</guid>
		<description>I&#039;ve found a nice solution for the Iphone-like approach on the website of &lt;a href=&quot;https://www.queridodesign.net/blog/passshark&quot; title=&quot;website of queridodesign&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Queridodesign&lt;/a&gt;. It is using Mootools and works in Safari 3+, Firefox 3+, Opera 10+, Internet Explorer 6 and 7.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found a nice solution for the Iphone-like approach on the website of <a href="https://www.queridodesign.net/blog/passshark" title="website of queridodesign" target="_blank" rel="nofollow">Queridodesign</a>. It is using Mootools and works in Safari 3+, Firefox 3+, Opera 10+, Internet Explorer 6 and 7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaime</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-167</link>
		<dc:creator>Jaime</dc:creator>
		<pubDate>Wed, 18 Nov 2009 15:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-167</guid>
		<description>@&lt;a href=&quot;#comment-166&quot; rel=&quot;nofollow&quot;&gt;Paul Olyslager&lt;/a&gt;:  Thanks Paul! I by no chance mean there should not be room for improvement. I do agree that if there&#039;s a chance to improve, so it shall be done in a tasteful and effective way. The thing is, a password input box that displays the letter and then transforms to a asterisk, is just a bit more safe than having the box display plaintext. A person with good visual ability and memory looking to steal your password will do so by looking at your plain text, by looking ad the changing letters, or by looking at your fingers when you type. In that same order you could say there&#039;s no protection with the first, somewhat a protection with the second and as much a protection with the last option. The main reason the iphone&#039;s password input boxes work like that is because of two reasons. First the fact that the phone is always in close proximity to your person and it&#039;s easier to &quot;protect&quot; your password entering with your body (which most people do, if only because most people use the phone in a position where people can&#039;t snoop from behind). And Second the fact that typing in an iphone is by definition harder than typing on a regular keyboard, as well as it&#039;s a lot more error prone. Add to that the fact that if I can probably type my password wrongly 2 times and get it the third time on the browser faster than typing it on an iphone (though that might be because I really don&#039;t get a lot of use from opposable thumbs). It&#039;s that much annoying to have to retype your password on the phone than on a laptop or desktop. I believe Apple decided to sacrifice a little security to make the experience easier for people. But we shouldn&#039;t do that on the web, because the security risk is a lot higher than on a mobile phone.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-166" rel="nofollow">Paul Olyslager</a>:  Thanks Paul! I by no chance mean there should not be room for improvement. I do agree that if there&#8217;s a chance to improve, so it shall be done in a tasteful and effective way. The thing is, a password input box that displays the letter and then transforms to a asterisk, is just a bit more safe than having the box display plaintext. A person with good visual ability and memory looking to steal your password will do so by looking at your plain text, by looking ad the changing letters, or by looking at your fingers when you type. In that same order you could say there&#8217;s no protection with the first, somewhat a protection with the second and as much a protection with the last option. The main reason the iphone&#8217;s password input boxes work like that is because of two reasons. First the fact that the phone is always in close proximity to your person and it&#8217;s easier to &#8220;protect&#8221; your password entering with your body (which most people do, if only because most people use the phone in a position where people can&#8217;t snoop from behind). And Second the fact that typing in an iphone is by definition harder than typing on a regular keyboard, as well as it&#8217;s a lot more error prone. Add to that the fact that if I can probably type my password wrongly 2 times and get it the third time on the browser faster than typing it on an iphone (though that might be because I really don&#8217;t get a lot of use from opposable thumbs). It&#8217;s that much annoying to have to retype your password on the phone than on a laptop or desktop. I believe Apple decided to sacrifice a little security to make the experience easier for people. But we shouldn&#8217;t do that on the web, because the security risk is a lot higher than on a mobile phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-166</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Wed, 18 Nov 2009 14:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-166</guid>
		<description>@&lt;a href=&quot;#comment-157&quot; rel=&quot;nofollow&quot;&gt;Jaime&lt;/a&gt;: 
First of all, thank you for your comment. It is always nice to hear someone else&#039;s opinion and takes the time to clarify it. I must say I partly agree with your comment. You shouldn&#039;t change the usability of something that is so standarized as the dots of a password field, but that doesn&#039;t mean there is no room for improvement (or at least have a look for other possibilities for that matter). Re-inventing the wheel is not necessary, but improving it to the changing external conditions without touching the basics of the wheel (it needs to roll) is. The essence of a password field are the dots itself, without these the field is not recognisable as a passform field. In all the alternatives mentioned in this article I kept the dots for consistency reasons. I do understand the solution of Apple, changing the character in a dot after you entered the next character makes sense. People still recognise it as a passform field, it is still consistent and it&#039;s more difficult to make a typo. I&#039;m not saying that this option will be the new standard, but it is nice to know that people still think about the functionality.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-157" rel="nofollow">Jaime</a>:<br />
First of all, thank you for your comment. It is always nice to hear someone else&#8217;s opinion and takes the time to clarify it. I must say I partly agree with your comment. You shouldn&#8217;t change the usability of something that is so standarized as the dots of a password field, but that doesn&#8217;t mean there is no room for improvement (or at least have a look for other possibilities for that matter). Re-inventing the wheel is not necessary, but improving it to the changing external conditions without touching the basics of the wheel (it needs to roll) is. The essence of a password field are the dots itself, without these the field is not recognisable as a passform field. In all the alternatives mentioned in this article I kept the dots for consistency reasons. I do understand the solution of Apple, changing the character in a dot after you entered the next character makes sense. People still recognise it as a passform field, it is still consistent and it&#8217;s more difficult to make a typo. I&#8217;m not saying that this option will be the new standard, but it is nice to know that people still think about the functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaime</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-157</link>
		<dc:creator>Jaime</dc:creator>
		<pubDate>Mon, 16 Nov 2009 11:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-157</guid>
		<description>I&#039;ve heard this a gazillion times. &quot;Why mask passwords? Give control back to the users!&quot;

There are various reasons why this is not a good idea. 

1) You may think that &quot;over the shoulder&quot; password peeking doesn&#039;t occur anymore, but it&#039;s far more likely to happen now than ever. Be it your girlfriend trying to figure out your Facebook password to see if you&#039;re cheating, or the florist that brought flowers to your office who is really a corporate spy. No this is not a movie script. This stuff does happen.

2) It has worked the way it is for ages. Why change something that works? Most people authenticate many different ways. Browser&#039;s password manager, a password managing app, the leave their account logged in, or are so used to typing their password that muscle memory takes care of the rest. Is it really that hard to type a string of 8 to 13 characters correctly? 

3) Users grew up with the idea that masked passwords mean security. You take that away and people will think twice about using your website. Though password masking does not equal security, it&#039;s to late to change the perception of it all. 

There&#039;s a point where usability pioneering starts getting in the way. Study the effects of positioning, whitespace, simplicity and complexity in interfaces, call to action importance hierarchies, and the whole plethora of other usability issues; but really, this stuff works well already, and changing it will make you the outcast in the list of sites the user uses. If out of the 10 sites I use 9 mask passwords and 1 doesn&#039;t, I might associate that with not being safe or meaning something completely different to what it would mean otherwise. 

To finish up, one of the most important concepts in user experience is consistency, and this doesn&#039;t only apply to the design of your site. It is just as important to maintain a consistency in certain elements the user interacts with throughout the whole web, and one of said components is the password field.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve heard this a gazillion times. &#8220;Why mask passwords? Give control back to the users!&#8221;</p>
<p>There are various reasons why this is not a good idea. </p>
<p>1) You may think that &#8220;over the shoulder&#8221; password peeking doesn&#8217;t occur anymore, but it&#8217;s far more likely to happen now than ever. Be it your girlfriend trying to figure out your Facebook password to see if you&#8217;re cheating, or the florist that brought flowers to your office who is really a corporate spy. No this is not a movie script. This stuff does happen.</p>
<p>2) It has worked the way it is for ages. Why change something that works? Most people authenticate many different ways. Browser&#8217;s password manager, a password managing app, the leave their account logged in, or are so used to typing their password that muscle memory takes care of the rest. Is it really that hard to type a string of 8 to 13 characters correctly? </p>
<p>3) Users grew up with the idea that masked passwords mean security. You take that away and people will think twice about using your website. Though password masking does not equal security, it&#8217;s to late to change the perception of it all. </p>
<p>There&#8217;s a point where usability pioneering starts getting in the way. Study the effects of positioning, whitespace, simplicity and complexity in interfaces, call to action importance hierarchies, and the whole plethora of other usability issues; but really, this stuff works well already, and changing it will make you the outcast in the list of sites the user uses. If out of the 10 sites I use 9 mask passwords and 1 doesn&#8217;t, I might associate that with not being safe or meaning something completely different to what it would mean otherwise. </p>
<p>To finish up, one of the most important concepts in user experience is consistency, and this doesn&#8217;t only apply to the design of your site. It is just as important to maintain a consistency in certain elements the user interacts with throughout the whole web, and one of said components is the password field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/#comment-154</link>
		<dc:creator>Sue</dc:creator>
		<pubDate>Mon, 16 Nov 2009 01:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-154</guid>
		<description>The dots are there for security, so someone looking over your shoulder can&#039;t find out your password (social engineering hacks).

In our software program, when you enter a password, such as for your key, it&#039;s in all dots. But there&#039;s a check box you can select that allows you to &quot;Show keystrokes.&quot; If you know no one is at your back, you can select this to verify you&#039;ve typed the correct password. In our case, it&#039;s a simple usability fix. :)</description>
		<content:encoded><![CDATA[<p>The dots are there for security, so someone looking over your shoulder can&#8217;t find out your password (social engineering hacks).</p>
<p>In our software program, when you enter a password, such as for your key, it&#8217;s in all dots. But there&#8217;s a check box you can select that allows you to &#8220;Show keystrokes.&#8221; If you know no one is at your back, you can select this to verify you&#8217;ve typed the correct password. In our case, it&#8217;s a simple usability fix. <img src='http://www.paulolyslager.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching 5/7 queries in 0.078 seconds using disk: basic
Object Caching 435/435 objects using disk: basic

Served from: www.paulolyslager.com @ 2012-05-18 02:34:14 -->
