<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Thinking Web Design</title>
	<atom:link href="http://thinkingwebdesign.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkingwebdesign.wordpress.com</link>
	<description>Thinking About Web Design and Development</description>
	<lastBuildDate>Wed, 20 Jul 2011 03:56:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='thinkingwebdesign.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Thinking Web Design</title>
		<link>http://thinkingwebdesign.wordpress.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://thinkingwebdesign.wordpress.com/osd.xml" title="Thinking Web Design" />
	<atom:link rel='hub' href='http://thinkingwebdesign.wordpress.com/?pushpress=hub'/>
		<item>
		<title>Anatomy of a Login Form Failure</title>
		<link>http://thinkingwebdesign.wordpress.com/2011/03/07/anatomy-of-a-login-form-failure/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2011/03/07/anatomy-of-a-login-form-failure/#comments</comments>
		<pubDate>Mon, 07 Mar 2011 01:10:53 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Login Forms]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=359</guid>
		<description><![CDATA[I recently went to register for an on-line presentation and to register I had to fill out this annoying form. In someways there were some design ideas that made sense but the way it operated was frustrating and if I didn&#8217;t want what was on the other side of the form I might have given [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=359&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>I recently went to register for an on-line presentation and to register I had to fill out this annoying form. In someways there were some design ideas that made sense but the way it operated was frustrating and if I didn&#8217;t want what was on the other side of the form I might have given up.</p>
<p>The first problem is I already had a relationship with these people.  I had even paid them money once. While this is a free event, I would have thought they could have made it easier for returning customers to access the site. Unfortunately, when you look at the site, on first glance it looks as if you have to fill out the whole form, which is what I did. I left the password field blank because I thought it was something about a coupon since I didn&#8217;t see Password at the beginning of the field. I then hit submit.</p>
<p>This is where the problems started. First of all it asked for a password. So I gave it one. Then it said your email already exists in our system. This is when I noticed the Returning Members Login now! to the right of the password box. After some fiddling around and password resets. I was able to login.</p>
<p>After you login, though, you have to finish filling out the form. Why? I assume it is some marketing gimmick, but they should have already had my information. To finish the process you have to scroll down to the Complete Registration button. While I give them credit for allowing you to login without doing a page refresh (and for presenting my information when I tested this after registering), the form is a barrier.</p>
<p>If you are going to offer existing clients a way to log in you should first make it obvious that they can do it, and two, change the page context once the log in has occurred. Since the form is fairly static and has little separation between the log in and details, the distinction between returning customers and prospective is broken.</p>
<p>Some options to make this a better experience is to have the email first and do a search on the email to see if it is in use and tell the user that it is in use, do you want to login or choose another email address. For returning customers, if you need that information, you should inform them that you recognize the relationship that you have, but you need to do some updates, or fill in missing data. It is insulting and suggests sloppiness when a returning customer is presented with such a form.</p>
<p><a href="http://thinkingwebdesign.files.wordpress.com/2011/03/login-form.png"><img class="alignnone size-full wp-image-360" title="Login Form" src="http://thinkingwebdesign.files.wordpress.com/2011/03/login-form.png?w=640&#038;h=384" alt="" width="640" height="384" /></a></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/359/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/359/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/359/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/359/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/359/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/359/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/359/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/359/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=359&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2011/03/07/anatomy-of-a-login-form-failure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2011/03/login-form.png" medium="image">
			<media:title type="html">Login Form</media:title>
		</media:content>
	</item>
		<item>
		<title>jQuery and the Advantages of Delegate</title>
		<link>http://thinkingwebdesign.wordpress.com/2011/02/27/jquery-and-the-advantages-of-delegate/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2011/02/27/jquery-and-the-advantages-of-delegate/#comments</comments>
		<pubDate>Sun, 27 Feb 2011 23:39:28 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Web development]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=354</guid>
		<description><![CDATA[I was recently putting together a right context menu for a web application. I wanted something simple and I used the menu from Web Developer Juice. I modified the menu so that only when I clicked a cell inside a table the right context menu would change. My table is very data intensive and a lot of different [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=354&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>I was recently putting together a right context menu for a web application. I wanted something simple and I used the menu from <a href="http://www.webdeveloperjuice.com/2010/02/22/create-simple-jquery-right-click-cross-browser-vertical-menu/">Web Developer Juice</a>. I modified the menu so that only when I clicked a cell inside a table the right context menu would change. My table is very data intensive and a lot of different operations need to be available to users with a right click. It worked well enough until I  noticed a strange behavior. If the menu was displayed and I tried to click somewhere other than the menu it didn&#8217;t always close. On further investigation, I noticed it was having trouble when the browser was offering me the select versus pointer cursor.</p>
<p><a href="http://thinkingwebdesign.files.wordpress.com/2011/02/selectacell.jpg"><img class="alignnone size-full wp-image-355" title="SelectACell" src="http://thinkingwebdesign.files.wordpress.com/2011/02/selectacell.jpg?w=640" alt=""   /></a></p>
<p>If the cursor shows select and I click in the cell the menu won&#8217;t close. That is not what one expects.</p>
<p>jQuery&#8217;s <a href="http://api.jquery.com/delegate/">Delegate</a>, though, makes it easy to deal with the situation. You can put delegate higher up the DOM and when ever a click event occurs it will propagate up the DOM it will fire the event you set with delegate. It is a handy feature. I set mine at the containing div for the page which insures that any click on the page will close the menu.</p>
<pre>$("body").delegate("#myDiv", "click", function(){
	//do something
});</pre>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/354/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/354/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/354/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/354/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/354/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/354/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/354/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/354/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=354&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2011/02/27/jquery-and-the-advantages-of-delegate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2011/02/selectacell.jpg" medium="image">
			<media:title type="html">SelectACell</media:title>
		</media:content>
	</item>
		<item>
		<title>Designing Web Interfaces With Bill Scott</title>
		<link>http://thinkingwebdesign.wordpress.com/2011/02/23/designing-web-interfaces-with-bill-scott/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2011/02/23/designing-web-interfaces-with-bill-scott/#comments</comments>
		<pubDate>Wed, 23 Feb 2011 03:49:34 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=352</guid>
		<description><![CDATA[This is almost 2 years old now, but if you haven&#8217;t seen it yet it is still worth while.  He gave a similar talk at the Web App Masters Tour conference.<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=352&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>This is almost 2 years old now, but if you haven&#8217;t seen it yet it is still worth while.  He gave a similar talk at the Web App Masters Tour conference.</p>
<span style="text-align:center; display: block;"><a href="http://thinkingwebdesign.wordpress.com/2011/02/23/designing-web-interfaces-with-bill-scott/"><img src="http://img.youtube.com/vi/LW4MwvgW_ww/2.jpg" alt="" /></a></span>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/352/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/352/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/352/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/352/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/352/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/352/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/352/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/352/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=352&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2011/02/23/designing-web-interfaces-with-bill-scott/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>
	</item>
		<item>
		<title>O&#8217;Reilly Media Wish List</title>
		<link>http://thinkingwebdesign.wordpress.com/2011/02/21/oreilly-media-wish-list/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2011/02/21/oreilly-media-wish-list/#comments</comments>
		<pubDate>Mon, 21 Feb 2011 19:37:08 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[O'Reilly Media]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=349</guid>
		<description><![CDATA[O&#8217;Reilly Media is having a give away if you list the books of theirs you would like. Here is my list, which if I were to win I would like in book form. Http: The Definitive Guide SEO Warrior CSS Cookbook, Third Edition jQuery Cookbook Programming the Semantic Web Even Faster Web Sites JavaScript Patterns HTML5: Up [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=349&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>O&#8217;Reilly Media is having a <a href="http://oreilly.com/new-year-2011-rules.csp#rules">give away</a> if you list the books of theirs you would like. Here is my list, which if I were to win I would like in book form.</p>
<p><a href="http://oreilly.com/catalog/9781565925090/">Http: The Definitive Guide</a></p>
<p><a href="http://oreilly.com/catalog/9780596157074/"><strong>SEO Warrior </strong></a></p>
<p><strong><a href="http://oreilly.com/catalog/9780596155933/"><strong>CSS Cookbook, Third Edition </strong></a></strong></p>
<p><strong><strong><a href="http://oreilly.com/catalog/9780596159771/"><strong>jQuery Cookbook </strong></a></strong></strong></p>
<p><strong><strong><strong><a href="http://oreilly.com/catalog/9780596153816/"><strong>Programming the Semantic Web </strong></a></strong></strong></strong></p>
<p><strong><strong><strong><strong><a href="http://oreilly.com/catalog/9780596522308/"><strong>Even Faster Web Sites </strong></a></strong></strong></strong></strong></p>
<p><strong><strong><strong><strong><strong><strong><a href="http://oreilly.com/catalog/9780596806750/"><strong>JavaScript Patterns</strong></a></strong></strong></strong></strong></strong></strong></p>
<p><strong><strong><strong><strong><strong><strong><strong><a href="http://oreilly.com/catalog/9780596806026/"><strong>HTML5: Up and Running </strong></a></strong></strong></strong></strong></strong></strong></strong></p>
<p><strong><strong><strong><strong><strong><strong><strong><strong><a href="http://oreilly.com/catalog/9780596802790/"><strong>High Performance JavaScript </strong></a></strong></strong></strong></strong></strong></strong></strong></strong></p>
<p><strong><strong><strong><strong><strong><strong><strong><strong><strong><a href="http://oreilly.com/catalog/9780596803025/"><strong>Developing Large Web Applications </strong></a><br />
</strong></strong></strong></strong></strong></strong></strong></strong></strong></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/349/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/349/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/349/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/349/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/349/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/349/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/349/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/349/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=349&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2011/02/21/oreilly-media-wish-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>
	</item>
		<item>
		<title>Web Design Anti-Pattern: Whac-A-Mole</title>
		<link>http://thinkingwebdesign.wordpress.com/2010/07/22/web-design-anti-pattern-whac-a-mole/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2010/07/22/web-design-anti-pattern-whac-a-mole/#comments</comments>
		<pubDate>Thu, 22 Jul 2010 04:50:28 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[anti pattern]]></category>
		<category><![CDATA[error handling]]></category>
		<category><![CDATA[passwords]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=31</guid>
		<description><![CDATA[Recently I upgraded my anti-virus at the Norton site. As I was filling out the credit card information, though, I made a few mistakes and found myself in a game of Whac-A-Mole. Whac-A-Mole is when you fix one field, only to find out that the form had cleared another field you had already filled out. [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=31&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Recently I upgraded my anti-virus at the Norton site. As I was filling out the credit card information, though, I made a few mistakes and found myself in a game of Whac-A-Mole. Whac-A-Mole is when you fix one field, only to find out that the form had cleared another field you had already filled out. If you are not observant you can go back and forth filling out one field only to have it cleared when you fix the next one. It may take several page submissions before you finally get all the information correct.</p>
<p>In the first image I have filled out all of the form fields except the card type. There is quite a bit of sensitive information on the form, including a password, the credit card no, security code, and the expiration date, all of which took me some time to find.</p>
<p><a href="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-1.png"><img class="size-full wp-image-32" title="norton-1" src="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-1.png?w=640" alt=""   /></a></p>
<p>When I clicked submit the form highlighted most of my errors. Unfortunately, it also cleared the password that I worked so hard on to create. Worse, the form has not indicated the error. When I fix the card error and click submit the page is going to return another error.</p>
<p><a href="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-2.png"><img class="alignnone size-full wp-image-33" title="norton-2" src="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-2.png?w=640" alt=""   /></a></p>
<p>Here the page indicates I am missing my password, which I had already entered. What isn&#8217;t obvious right away is that the security code has been erased, too. If you were to fill out the password fields and go straight to the submit button you might miss that the security code was not filled out. You click submit and the page returns an error saying the security code hasn&#8217;t been filled out. But it has also cleared the password again and isn&#8217;t telling you clearly. So the process begins again. It could take several attempts to fill out the form and by this time you are getting mad.</p>
<p><a href="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-3.png"><img class="alignnone size-full wp-image-34" title="norton-3" src="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-3.png?w=640" alt=""   /></a></p>
<p>When I fist filled out the form they didn&#8217;t have the pop up warnings, which are a big help. Unfortunately, the pop ups don&#8217;t cascade from one form error to another when you fix the error. Instead, you have to click the little X on the pop up to get the next error message to pop up. Who wants to do that? What they should attempt is to show each error message as the previous one is cleared. Another part of the problem is the visual separation of the password and credit card information. If they were closer to each other it would be more obvious that the two errors had occurred. Since users are less likely to make a mistake with their address, moving the email, password and credit  information nearer to each other would probably help. Finally, why do they need to clear the password anyway? Isn&#8217;t the connection secure to begin with? Once and a while developers can be overly security conscious.</p>
<p>One last problem with the form is the card type selection box. If you fill out the card number and expiration date before the card type, you will loose all you data. The card type drop down is programed to reset the fields when you select a new card. This doesn&#8217;t make sense since card numbers and expiration dates are on every card there.</p>
<p>Although they have improved their form a little since the last time I  filled it out, many of the problems I first encountered still remain. I hope they have these fixed when I have to renew again.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/31/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/31/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/31/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/31/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/31/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/31/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/31/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/31/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=31&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2010/07/22/web-design-anti-pattern-whac-a-mole/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-1.png" medium="image">
			<media:title type="html">norton-1</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-2.png" medium="image">
			<media:title type="html">norton-2</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2010/07/norton-3.png" medium="image">
			<media:title type="html">norton-3</media:title>
		</media:content>
	</item>
		<item>
		<title>HTML 5 and SEO</title>
		<link>http://thinkingwebdesign.wordpress.com/2010/06/30/html-5-and-seo/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2010/06/30/html-5-and-seo/#comments</comments>
		<pubDate>Wed, 30 Jun 2010 03:54:11 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=28</guid>
		<description><![CDATA[SEO Gadget has a quick run down of the new features in HTML 5 from an SEO perspective. It will be interesting if those translate into the search engines. HTML 5 will introduce new features that help us (and search engines) better dissect a webpage. In the past, &#60;div&#62; elements have been used everywhere where, [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=28&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://seogadget.co.uk/xhtml-20-and-seo/">SEO Gadget</a> has a quick run down of the new features in HTML 5 from an SEO perspective. It will be interesting if those translate into the search engines.</p>
<blockquote><p>HTML 5 will introduce new features that help us (and search engines)  better dissect a webpage. In the past, &lt;div&gt; elements have been  used everywhere where, in HTML 5 an array of elements will be available  to describe navigation, text sections, articles and headers. The  improved sectioning could quite easily assist a search engine in  understanding the layout of a page – check out <a href="http://www.timnash.co.uk/05/2008/block-segmentation-analysis/">this  post on block analysis</a> to understand why that’s cool.</p></blockquote>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/28/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=28&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2010/06/30/html-5-and-seo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>
	</item>
		<item>
		<title>A Search Failure &#8211; Reviewing Canal Sur</title>
		<link>http://thinkingwebdesign.wordpress.com/2010/01/10/a-search-failure-reviewing-canal-sur/</link>
		<comments>http://thinkingwebdesign.wordpress.com/2010/01/10/a-search-failure-reviewing-canal-sur/#comments</comments>
		<pubDate>Sun, 10 Jan 2010 22:19:45 +0000</pubDate>
		<dc:creator>bythefirelight</dc:creator>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Canal Sur]]></category>
		<category><![CDATA[Search Failures]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://thinkingwebdesign.wordpress.com/?p=5</guid>
		<description><![CDATA[Canal Sur is a a television network in Andalusia Spain. The site is an excellent source of Spanish language television programing because they post all their shows on-line for two weeks, in addition to their live feed. Unfortunately, the way the site is laid out it is difficult to find the content you want. I [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=5&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.canalsure.es" target="_blank">Canal Sur</a> is a a television network in Andalusia Spain. The site is an excellent source of Spanish language television programing because they post all their shows on-line for two weeks, in addition to their live feed. Unfortunately, the way the site is laid out it is difficult to find the content you want. I use the site quite a bit and would say I have intermediate experience with the site, and I still have problems finding things.Having used the site of the years, I know that part of the problem is the site has grown over the years and has continued to add items to the original structure.</p>
<p>Canal Sur is full of examples of how to confuse the user and is instructive in what not to do. The analysis of the site will focus on the search and navigation systems and how they either don&#8217;t exist or lead the use to the wrong information. In analyzing the site and its search features, I want to look find the current episodes of a program, either on the show&#8217;s home page or somewhere else</p>
<h3>Home Page Search</h3>
<p>The problems with the Canal Sur site begin on the home page. Imagine that you wanted to find the most recent episode of the program El Público Lee. What would you do? You could search, which many users do when they don&#8217;t see what they want, or as their primary means of site navigation. The site search(buscador in Spanish) is in the top right an extremely common location. If were to search for El Público Lee and hoped to find the show&#8217;s home page or the most recent episode you would be out of luck</p>
<div id="attachment_13" class="wp-caption alignnone" style="width: 520px"><a href="http://thinkingwebdesign.files.wordpress.com/2010/01/canalsur_home.jpg"><img class="size-full wp-image-13" title="Canal Sur Home" src="http://thinkingwebdesign.files.wordpress.com/2010/01/canalsur_home.jpg?w=640" alt="Canal Sur Home"   /></a><p class="wp-caption-text">Canal Sur Home</p></div>
<p>Instead, you would get a list of results that are vague at best (even if you speak Spanish). The first two entries are about the show, but when you follow the links you don&#8217;t go to a sub page within the show&#8217;s sub site. Instead, you go to a press release where you can download a Word document. The second result, which looks the most promising since it actually talks about who will be on the show, has the same problem. The last two items on the first results page are about a different program called El Público.</p>
<div id="attachment_15" class="wp-caption alignnone" style="width: 519px"><a href="http://thinkingwebdesign.files.wordpress.com/2010/01/canalsur_search_results_lee.jpg"><img class="size-full wp-image-15" title="Canal Sur Search Results" src="http://thinkingwebdesign.files.wordpress.com/2010/01/canalsur_search_results_lee.jpg?w=640" alt="Canal Sur Search Results"   /></a><p class="wp-caption-text">Canal Sur Search Results</p></div>
<p>The results page seems designed to confused. First, showing press releases in search results is not a great idea. Press releases are not particularly as time goes on. More users will be looking for the actually content than press releases, especially as the release ages.  Moreover, it is unclear why one press release has more relevance than another. As a regular viewer of the program, I know that the release does not refer to a recent episode. It should also be obvious what the link will go to. Some how they should codify what is a press release and what isn&#8217;t. Finally, the search algorithm should limit the results by the three words, El Público Lee. If designers are worried someone will miss El Público, they should offer a &#8220;Did you mean&#8221; option. If you are going to have a search on your site, you need to produce manageable and usable results that work to user&#8217;s expectations. Going to random press releases is worse than not having a search option.</p>
<p>In part two, I will talk about finding the show home page via navigation.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/thinkingwebdesign.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/thinkingwebdesign.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/thinkingwebdesign.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/thinkingwebdesign.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/thinkingwebdesign.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/thinkingwebdesign.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/thinkingwebdesign.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/thinkingwebdesign.wordpress.com/5/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=thinkingwebdesign.wordpress.com&amp;blog=11342501&amp;post=5&amp;subd=thinkingwebdesign&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://thinkingwebdesign.wordpress.com/2010/01/10/a-search-failure-reviewing-canal-sur/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6b2048c70a1ab7e0813f2ebdfd54e75?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">bythefirelight</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2010/01/canalsur_home.jpg" medium="image">
			<media:title type="html">Canal Sur Home</media:title>
		</media:content>

		<media:content url="http://thinkingwebdesign.files.wordpress.com/2010/01/canalsur_search_results_lee.jpg" medium="image">
			<media:title type="html">Canal Sur Search Results</media:title>
		</media:content>
	</item>
	</channel>
</rss>
