<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Web Usability Blog&#187; error messages</title>
	<atom:link href="http://webusability-blog.com/tags/error-messages/feed/" rel="self" type="application/rss+xml" />
	<link>http://webusability-blog.com</link>
	<description>Tips, insights and meandering thoughts about usability and information architecture</description>
	<lastBuildDate>Wed, 01 Sep 2010 13:42:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>This route is not available at the moment</title>
		<link>http://webusability-blog.com/this-route-is-not-available-at-the-moment/</link>
		<comments>http://webusability-blog.com/this-route-is-not-available-at-the-moment/#comments</comments>
		<pubDate>Fri, 12 Mar 2010 09:19:31 +0000</pubDate>
		<dc:creator>Els Aerts</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[error messages]]></category>

		<guid isPermaLink="false">http://webusability-blog.com/?p=915</guid>
		<description><![CDATA[Route planner Mappy has an error message that says 'Sorry, this route is not available at the moment'. I'm not sure that's what they really mean though.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.mappy.com/">Route planner Mappy</a> had a strange message for me last week.</p>
<p><a href="http://farm5.static.flickr.com/4015/4407716555_4fb0d996f9_o.gif" rel="lightbox[915]"><img class="alignnone" title="Sorry, this route is not available at the moment" src="http://farm5.static.flickr.com/4015/4407716555_4bee94d61c.jpg" alt="" width="500" height="360" /></a></p>
<p>What do you mean, this route is not available?<br />
Has the road gone missing?<br />
Was it destroyed by an earthquake?<br />
A tsunami?<br />
Has it been temporarily moved to a parallell universe?<br />
Help!</p>
<h4>Related articles</h4>
<ul>
<li><a href="http://webusability-blog.com/gender-error/">Gender error</a></li>
<li><a href="http://webusability-blog.com/user-friendly-error-messages-7-tips/">7 tips for user-friendly error messages</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://webusability-blog.com/this-route-is-not-available-at-the-moment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User-friendly error messages: 7 tips</title>
		<link>http://webusability-blog.com/user-friendly-error-messages-7-tips/</link>
		<comments>http://webusability-blog.com/user-friendly-error-messages-7-tips/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 08:57:07 +0000</pubDate>
		<dc:creator>Els Aerts</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[error messages]]></category>
		<category><![CDATA[forms]]></category>

		<guid isPermaLink="false">http://webusability-blog.com/?p=357</guid>
		<description><![CDATA[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[<h1>Why are error messages important?</h1>
<p>A lot of websites make usability mistakes on their form pages. And that costs visitors. On a form page that&#8217;s extra painful because if you lose a visitor there, you loose a very valuable visitor. A visitor who&#8217;s willing to make the effort to get in touch with you or perhaps even to order something. A visitor who fills out a form (or tries to) is a visitor you should cherish.</p>
<p>Here&#8217;s a few tips.</p>
<h1>1. Use the language of the form</h1>
<p>If the form is in English, the error messages should be in English. Sounds self-evident, I know. And on single-language websites this usually isn&#8217;t a problem.</p>
<p>But on multi-language websites it often is. Error messages are often overlooked in the translation process. Make sure they aren&#8217;t on your website.<span id="more-357"></span></p>
<h1>2. Use understandable language</h1>
<p>Don&#8217;t use code or words only programmers know the meaning of like <a href="http://webusability-blog.com/gender-error/">&#8220;Customerrelation_gender_error&#8221;</a> or &#8220;FieldT12empty&#8221;.</p>
<p>That&#8217;s pretty much all I&#8217;m going to say about that one.</p>
<h1>3. Be nice</h1>
<p>How hard is it to just be nice? The person filling out your form is a potential customer.</p>
<p>Now is not the time to get smart and say things like &#8220;Your letters stink&#8221; if somebody gets the captcha wrong. Instead, say &#8220;You did not enter the correct text displayed in the spam-prevention image box. Please try again.&#8221;</p>
<p>Sounds a lot nicer, doesn&#8217;t?</p>
<h1>4. Be specific</h1>
<p>General error messages like &#8220;Fill out all the required fields&#8221; are an excellent way to scare off potential customers.</p>
<p>An error message like &#8220;Invalid credit card&#8221; isn&#8217;t exactly helpful either.</p>
<p>Give the user more details about what went wrong and what he can do to fix it: &#8220;There was an error processing your credit card. Please check your name, credit card number, and card expiration date for correctness. Remember, these must match the card exactly.&#8221;.</p>
<p>The more specific your error message is, the easier it is for the user to fix the problem.</p>
<h1>5. Don&#8217;t blame the user</h1>
<p>If the user has made a mistake while filling out your form it&#8217;s not a good idea to rub his nose in it.</p>
<p>Don&#8217;t tell the user what he did wrong. Tell him what he should do to get it right.</p>
<p>Don&#8217;t write:</p>
<ul type="disc">
<li>You forgot to fill out your email address.</li>
</ul>
<p>But write:</p>
<ul type="disc">
<li>Please fill out your email address.</li>
</ul>
<h1>6. Avoid spelling errors</h1>
<p>Check the spelling of your error messages. Error messages are hidden away and often get overlooked. Make sure an editor checks them.</p>
<h1>7. How do you check all this?</h1>
<p>Leave your form empty, press the &#8216;Send&#8217; button and read the error messages. Imagine it&#8217;s somebody else&#8217;s website and see if everything&#8217;s clear and if there isn&#8217;t anything that would annoy you.</p>
<p>Next, put in some &#8216;wrong&#8217; data (email address without an @, postal code that doesn&#8217;t exist, date of birth in 2020, etc) and see what kind of error messages that generates.</p>
<p>It really isn&#8217;t that hard. So hop to it!</p>
<blockquote><p>Would you like to know how your site&#8217;s usability could be improved?<br />
Time for an <a href="http://www.agconsult.be/en/usability/expert.asp">expert review</a>.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://webusability-blog.com/user-friendly-error-messages-7-tips/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Gender error</title>
		<link>http://webusability-blog.com/gender-error/</link>
		<comments>http://webusability-blog.com/gender-error/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 09:01:39 +0000</pubDate>
		<dc:creator>Els Aerts</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[error messages]]></category>
		<category><![CDATA[forms]]></category>

		<guid isPermaLink="false">http://webusability-blog.com/?p=348</guid>
		<description><![CDATA[According to Citroën I'm suffering a 'gender error'. Should I panic? Wear more make-up maybe? Stuff some of those chicken cutlets down my bra? None of the above. It seems I simply forgot to tell them whether I am a MR, MISS or MRS. Phew.]]></description>
			<content:encoded><![CDATA[<p>According to Citroën I&#8217;m suffering from a &#8216;gender error&#8217;.</p>
<p><a href="http://farm4.static.flickr.com/3549/3819417901_29b882abdc_o.jpg" rel="lightbox[348]"><img class="alignnone" title="Citroën Gender Error" src="http://farm4.static.flickr.com/3549/3819417901_f759957785.jpg" alt="I am a LADY!" width="500" height="363" /></a></p>
<p>Should I panic? Wear more make-up maybe? Stuff some of those chicken cutlets down my bra?</p>
<p>None of the above. It seems I simply forgot to tell them whether I am a MR, MISS or MRS.</p>
<p>Phew.</p>
]]></content:encoded>
			<wfw:commentRss>http://webusability-blog.com/gender-error/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
