<?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: User-friendly error messages: 7 tips</title>
	<atom:link href="http://webusability-blog.com/user-friendly-error-messages-7-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/</link>
	<description>Tips, insights and meandering thoughts about usability and information architecture</description>
	<lastBuildDate>Mon, 21 May 2012 12:45:23 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 10 most popular usability articles in 2009 &#124; Uxable</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-5520</link>
		<dc:creator>10 most popular usability articles in 2009 &#124; Uxable</dc:creator>
		<pubDate>Fri, 25 Jun 2010 21:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-5520</guid>
		<description>[...] User-friendly error messages: 7 tips A lot of websites make usability mistakes on their form pages. And that costs visitors. On a form page that’s extra painful because if you lose a visitor there, you loose a very valuable visitor. A visitor who’s willing to make the effort to get in touch with you or perhaps even to order something. 7 tips for user-friendly error messages. [...]</description>
		<content:encoded><![CDATA[<p>[...] User-friendly error messages: 7 tips A lot of websites make usability mistakes on their form pages. And that costs visitors. On a form page that’s extra painful because if you lose a visitor there, you loose a very valuable visitor. A visitor who’s willing to make the effort to get in touch with you or perhaps even to order something. 7 tips for user-friendly error messages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atomiton</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-2623</link>
		<dc:creator>Atomiton</dc:creator>
		<pubDate>Wed, 20 Jan 2010 16:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-2623</guid>
		<description>One comment regarding email addresses. If they didn&#039;t enter an email address, sure, &quot;please enter an email address&quot; is good. However, if it&#039;s an invalid email address. saying something like &quot;Please enter a valid email address&quot; isn&#039;t the best, because they may have made a typo and won&#039;t catch the &quot;VALID&quot; word in the middle. Instead, something like: &quot;We couldn&#039;t validate the email address. Please check your email and enter a valid address.&quot; may work.  I know the wording isn&#039;t the best, but I&#039;m just thinking off the cuff. The point is, if the user has made a typographical error, it&#039;s usually good to point it out, as most users will only glance at the error message and assume they&#039;re missing something.</description>
		<content:encoded><![CDATA[<p>One comment regarding email addresses. If they didn&#8217;t enter an email address, sure, &#8220;please enter an email address&#8221; is good. However, if it&#8217;s an invalid email address. saying something like &#8220;Please enter a valid email address&#8221; isn&#8217;t the best, because they may have made a typo and won&#8217;t catch the &#8220;VALID&#8221; word in the middle. Instead, something like: &#8220;We couldn&#8217;t validate the email address. Please check your email and enter a valid address.&#8221; may work.  I know the wording isn&#8217;t the best, but I&#8217;m just thinking off the cuff. The point is, if the user has made a typographical error, it&#8217;s usually good to point it out, as most users will only glance at the error message and assume they&#8217;re missing something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Els Aerts</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-2474</link>
		<dc:creator>Els Aerts</dc:creator>
		<pubDate>Mon, 11 Jan 2010 14:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-2474</guid>
		<description>@Erika: You&#039;re absolutely right. &#039;You did not&#039; is to be avoided in error messages. My bad.</description>
		<content:encoded><![CDATA[<p>@Erika: You&#8217;re absolutely right. &#8216;You did not&#8217; is to be avoided in error messages. My bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erika</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-2391</link>
		<dc:creator>Erika</dc:creator>
		<pubDate>Sat, 09 Jan 2010 01:19:24 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-2391</guid>
		<description>Hi,

Did you notice that under &#039;3. Be nice,&#039; your example text &quot;You did not enter the correct text etc&quot; is critiqued in your very own &#039;5. Don&#039;t blame the user&#039;? I cringed at the &quot;you did not&quot; myself. How about, &quot;Those characters didn&#039;t match. Try this one&quot;?

I couldn&#039;t agree more with the mantra to never blame the user. It is always up to us to be clear and accommodating.

:-) erika</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Did you notice that under &#8216;3. Be nice,&#8217; your example text &#8220;You did not enter the correct text etc&#8221; is critiqued in your very own &#8216;5. Don&#8217;t blame the user&#8217;? I cringed at the &#8220;you did not&#8221; myself. How about, &#8220;Those characters didn&#8217;t match. Try this one&#8221;?</p>
<p>I couldn&#8217;t agree more with the mantra to never blame the user. It is always up to us to be clear and accommodating.</p>
<p> <img src='http://webusability-blog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  erika</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 most popular usability articles in 2009 - The Web Usability Blog</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-2125</link>
		<dc:creator>10 most popular usability articles in 2009 - The Web Usability Blog</dc:creator>
		<pubDate>Wed, 23 Dec 2009 18:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-2125</guid>
		<description>[...] User-friendly error messages: 7 tips [...]</description>
		<content:encoded><![CDATA[<p>[...] User-friendly error messages: 7 tips [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: En guide til feilmeldinger i webløsninger &#8211; Stammen.no</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-1509</link>
		<dc:creator>En guide til feilmeldinger i webløsninger &#8211; Stammen.no</dc:creator>
		<pubDate>Mon, 09 Nov 2009 09:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-1509</guid>
		<description>[...] Brukervennlige feilmeldinger: 7 tips (The Web usability blog) [...]</description>
		<content:encoded><![CDATA[<p>[...] Brukervennlige feilmeldinger: 7 tips (The Web usability blog) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marijn</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-1126</link>
		<dc:creator>Marijn</dc:creator>
		<pubDate>Thu, 01 Oct 2009 20:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-1126</guid>
		<description>pingback: http://marijnsomers.blogspot.com/2009/10/web-usability-blog-hits-nail-on-error.html

Love your blog, and specially this post!! I couldn&#039;t agree more!!</description>
		<content:encoded><![CDATA[<p>pingback: <a href="http://marijnsomers.blogspot.com/2009/10/web-usability-blog-hits-nail-on-error.html" rel="nofollow">http://marijnsomers.blogspot.com/2009/10/web-usability-blog-hits-nail-on-error.html</a></p>
<p>Love your blog, and specially this post!! I couldn&#8217;t agree more!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Els Aerts</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-759</link>
		<dc:creator>Els Aerts</dc:creator>
		<pubDate>Sat, 05 Sep 2009 15:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-759</guid>
		<description>Thanks for adding your tips, Julia!</description>
		<content:encoded><![CDATA[<p>Thanks for adding your tips, Julia!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julia Slavin</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/comment-page-1/#comment-747</link>
		<dc:creator>Julia Slavin</dc:creator>
		<pubDate>Fri, 04 Sep 2009 12:23:42 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=357#comment-747</guid>
		<description>Nice tips in overall. I could only add a few to strengthen the point:
* Make a tip per a field - it&#039;s not so nice to get to the top of the page, read the message and look down for the relevant field.
* Where is possible to validate the input in real time - do it and show the tip immediately after the field loses focus.
* Show positive indicator after verifying the data. For example, if the visitor has submitted a valid email address, color the field&#039;s borders in green.
* Keep the error tips as short as possible, even if it makes them less mannered. For example, instead of &quot;To create a strong password, please use both letters and numbers. Passwords may be maximum six characters long&quot;, say &quot;Please combine up to 6 letters and numbers&quot;. This bullet a little bit contradicts your 4th tip about being more specific. I suppose that a compromise should be found to keep the message clear yet brief.
* Present your tips in a way that doesn&#039;t take any effort from the visitor, for example clicking on an (?) icon to switch the tip on and off.

Good luck with your forms!</description>
		<content:encoded><![CDATA[<p>Nice tips in overall. I could only add a few to strengthen the point:<br />
* Make a tip per a field &#8211; it&#8217;s not so nice to get to the top of the page, read the message and look down for the relevant field.<br />
* Where is possible to validate the input in real time &#8211; do it and show the tip immediately after the field loses focus.<br />
* Show positive indicator after verifying the data. For example, if the visitor has submitted a valid email address, color the field&#8217;s borders in green.<br />
* Keep the error tips as short as possible, even if it makes them less mannered. For example, instead of &#8220;To create a strong password, please use both letters and numbers. Passwords may be maximum six characters long&#8221;, say &#8220;Please combine up to 6 letters and numbers&#8221;. This bullet a little bit contradicts your 4th tip about being more specific. I suppose that a compromise should be found to keep the message clear yet brief.<br />
* Present your tips in a way that doesn&#8217;t take any effort from the visitor, for example clicking on an (?) icon to switch the tip on and off.</p>
<p>Good luck with your forms!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

