<?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: Styling Your Forms to Improve Usability</title>
	<atom:link href="http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 28 Dec 2011 20:34:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Craig Sullivan</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-533</link>
		<dc:creator>Craig Sullivan</dc:creator>
		<pubDate>Thu, 12 Mar 2009 21:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-533</guid>
		<description>I often see this when analysing search results - things like

hhotels in antigua
arartichokes in olive oil

Where fields are &#039;corrected&#039; because part of the form entry has scrolled off to the left.  One of the inclinations is to retype the &#039;missing&#039; piece with these consequences.  The general rule of thumb is good but beware of user supplied formats that may exceed your expected length.</description>
		<content:encoded><![CDATA[<p>I often see this when analysing search results &#8211; things like</p>
<p>hhotels in antigua<br />
arartichokes in olive oil</p>
<p>Where fields are &#8216;corrected&#8217; because part of the form entry has scrolled off to the left.  One of the inclinations is to retype the &#8216;missing&#8217; piece with these consequences.  The general rule of thumb is good but beware of user supplied formats that may exceed your expected length.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Addicott Web</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-532</link>
		<dc:creator>Addicott Web</dc:creator>
		<pubDate>Thu, 12 Mar 2009 19:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-532</guid>
		<description>That&#039;s an excellent point about breathing room, Craig. I agree that the general rule of thumb should be to never set the length of an input field so short so that when someone is filling it out, they can&#039;t see what they entered in its entirety without having to scroll over. When designers do that, they&#039;re just setting whomever up for problems down the road.</description>
		<content:encoded><![CDATA[<p>That&#8217;s an excellent point about breathing room, Craig. I agree that the general rule of thumb should be to never set the length of an input field so short so that when someone is filling it out, they can&#8217;t see what they entered in its entirety without having to scroll over. When designers do that, they&#8217;re just setting whomever up for problems down the road.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Sullivan</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-526</link>
		<dc:creator>Craig Sullivan</dc:creator>
		<pubDate>Thu, 12 Mar 2009 15:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-526</guid>
		<description>Hi,

I&#039;ve done quite a few hundred hours testing (a lot with forms) and I&#039;ve rarely seen people notice the focus set to the first form.  However, when I have had it set, it hasn&#039;t interfered so it doesn&#039;t do any *harm* and probably a *little* benefit for some advanced users.

One comment on breathing room - even input fields with expected value lengths should be slightly larger - try to imagine either one or more keyboard slips, formatting additions (e.g. +()- in phone numbers) or spaces and increase accordingly.  I&#039;ve seen a lot of people mangle fields due to the size being spot on, but with no room for error whatsoever.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;ve done quite a few hundred hours testing (a lot with forms) and I&#8217;ve rarely seen people notice the focus set to the first form.  However, when I have had it set, it hasn&#8217;t interfered so it doesn&#8217;t do any *harm* and probably a *little* benefit for some advanced users.</p>
<p>One comment on breathing room &#8211; even input fields with expected value lengths should be slightly larger &#8211; try to imagine either one or more keyboard slips, formatting additions (e.g. +()- in phone numbers) or spaces and increase accordingly.  I&#8217;ve seen a lot of people mangle fields due to the size being spot on, but with no room for error whatsoever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Addicott Web</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-507</link>
		<dc:creator>Addicott Web</dc:creator>
		<pubDate>Mon, 09 Mar 2009 13:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-507</guid>
		<description>Thanks for bringing that up Rob - that&#039;s a great point. I had mentioned it briefly in my post, but it&#039;s kind of buried within one of the lists, so I can see how it&#039;s difficult to find.

In any case, after I wrote this post I restyled my comments form, and included an &quot;input:focus&quot; style in my stylesheet. You probably noticed it in action when you filled out the comments form earlier. It&#039;s definitely something that I&#039;m going to start incorporating as standard practice in all of my designs though.

On a somewhat related note, what do you think of having the cursor automatically appear in the first form field when the page loads? I&#039;ve seen varying viewpoints about the topic, but I&#039;m curious what you think of it from the usability standpoint.</description>
		<content:encoded><![CDATA[<p>Thanks for bringing that up Rob &#8211; that&#8217;s a great point. I had mentioned it briefly in my post, but it&#8217;s kind of buried within one of the lists, so I can see how it&#8217;s difficult to find.</p>
<p>In any case, after I wrote this post I restyled my comments form, and included an &#8220;input:focus&#8221; style in my stylesheet. You probably noticed it in action when you filled out the comments form earlier. It&#8217;s definitely something that I&#8217;m going to start incorporating as standard practice in all of my designs though.</p>
<p>On a somewhat related note, what do you think of having the cursor automatically appear in the first form field when the page loads? I&#8217;ve seen varying viewpoints about the topic, but I&#8217;m curious what you think of it from the usability standpoint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob's Web Usability Site</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-503</link>
		<dc:creator>Rob's Web Usability Site</dc:creator>
		<pubDate>Mon, 09 Mar 2009 05:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-503</guid>
		<description>input:focus is a handy little tip to keep the form moving.</description>
		<content:encoded><![CDATA[<p>input:focus is a handy little tip to keep the form moving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Addicott Web</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-466</link>
		<dc:creator>Addicott Web</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-466</guid>
		<description>Fieldsets are definitely worth reconsidering, but I think this is a better way of saying it: you should know about them so that you know when they might be useful to you.

Like I wrote, I think they can be particularly handy when you have a longer form and you want to break it up into smaller units to make it more organized for the user. You don’t have to use a fieldset for every form you have, and even if you do use one, you don’t necessarily have to style it. For example, this comment form is wrapped in a fieldset, but you wouldn’t know it unless you looked in the code.

Regarding labels, those are definitely something worth considering and using more often. I’ve only begun to use them recently myself, but if you’re into making your code as semantic as possible, they are definitely the way to go.</description>
		<content:encoded><![CDATA[<p>Fieldsets are definitely worth reconsidering, but I think this is a better way of saying it: you should know about them so that you know when they might be useful to you.</p>
<p>Like I wrote, I think they can be particularly handy when you have a longer form and you want to break it up into smaller units to make it more organized for the user. You don’t have to use a fieldset for every form you have, and even if you do use one, you don’t necessarily have to style it. For example, this comment form is wrapped in a fieldset, but you wouldn’t know it unless you looked in the code.</p>
<p>Regarding labels, those are definitely something worth considering and using more often. I’ve only begun to use them recently myself, but if you’re into making your code as semantic as possible, they are definitely the way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Addicott Web</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-465</link>
		<dc:creator>Addicott Web</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-465</guid>
		<description>Thanks for commenting, Caroline! I looked at your website and I&#039;m glad that someone of your expertise not only commented, but liked what I wrote!

Regarding the &quot;breathing room&quot; you mentioned - I think adding the small touches such as padding help us move away from forms as they used to look (boring, unstyled, etc.) towards the point where forms truly look like they belong on a website.

As I looked through some of the design galleries that I linked to, I was glad to see that so many designers were giving forms serious consideration. I know they can often go overlooked, despite the knowledge that how they are designed and laid out does have some big usability implications.</description>
		<content:encoded><![CDATA[<p>Thanks for commenting, Caroline! I looked at your website and I&#8217;m glad that someone of your expertise not only commented, but liked what I wrote!</p>
<p>Regarding the &#8220;breathing room&#8221; you mentioned &#8211; I think adding the small touches such as padding help us move away from forms as they used to look (boring, unstyled, etc.) towards the point where forms truly look like they belong on a website.</p>
<p>As I looked through some of the design galleries that I linked to, I was glad to see that so many designers were giving forms serious consideration. I know they can often go overlooked, despite the knowledge that how they are designed and laid out does have some big usability implications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caroline Jarrett</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-463</link>
		<dc:creator>Caroline Jarrett</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-463</guid>
		<description>Very nice - good advice, particularly &quot;Give the user breathing room to type&quot;, a courteous touch that is often forgotten. How many times have I seen sillinesses like a box intended for an email address that is way too small for many typical addresses.

Caroline Jarrett,
&quot;Forms that work: Designing web forms for usability&quot; - foreword by Steve Krug.</description>
		<content:encoded><![CDATA[<p>Very nice &#8211; good advice, particularly &#8220;Give the user breathing room to type&#8221;, a courteous touch that is often forgotten. How many times have I seen sillinesses like a box intended for an email address that is way too small for many typical addresses.</p>
<p>Caroline Jarrett,<br />
&#8220;Forms that work: Designing web forms for usability&#8221; &#8211; foreword by Steve Krug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.addicottweb.com/2009/03/styling-your-forms-to-improve-usability/#comment-462</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 03 Mar 2009 17:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.addicottweb.com/?p=782#comment-462</guid>
		<description>Fieldsets and labels are things that I ALWAYS overlook to add. I suppose I just never found the usefulness for them. Maybe I should reconsider?</description>
		<content:encoded><![CDATA[<p>Fieldsets and labels are things that I ALWAYS overlook to add. I suppose I just never found the usefulness for them. Maybe I should reconsider?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

