<?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: Forms. Can&#8217;t live with them. Can&#8217;t live without them.</title>
	<atom:link href="http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 20:09:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bogdan Pop</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1757</link>
		<dc:creator>Bogdan Pop</dc:creator>
		<pubDate>Mon, 21 Mar 2011 08:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1757</guid>
		<description>Hi Iza and thanks for the great comment. Nice links too. Please note that I&#039;ve coded the forms in the second part of the tutorial: &lt;a href=&quot;http://www.webia.info/articles/usability/impressive-web-forms-from-coding-to-validation/&quot; rel=&quot;nofollow&quot;&gt;coding and validating web forms&lt;/a&gt;.</description>
		<content:encoded><![CDATA[Hi Iza and thanks for the great comment. Nice links too. Please note that I&#8217;ve coded the forms in the second part of the tutorial: <a href="http://www.webia.info/articles/usability/impressive-web-forms-from-coding-to-validation/" rel="nofollow">coding and validating web forms</a>.]]></content:encoded>
	</item>
	<item>
		<title>By: Iza Bartosiewicz</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1755</link>
		<dc:creator>Iza Bartosiewicz</dc:creator>
		<pubDate>Mon, 21 Mar 2011 04:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1755</guid>
		<description>Hi Bogdan,
Your post has been up for a while, but there are a couple of points I would like to follow-up on. The first one concerns the &#039;inline labels&#039;. You&#039;ve identified the usability issues, and Ben picked on the potential accessibility problems with this approach. I just wanted to add that anyone wishing to use this technique should check out Terrill Thompson’s page first: http://terrillthompson.blogspot.com/2011/01/testing-accessibility-of-pre-populated.html

The second point is about the accessibility of top-aligned labels raised by Ben. He is right, this form would create problems for the screen reader users IF a table was used for layout, the labels and the corresponding fields were sitting in separate rows, and the label markup was missing. However, we can’t be certain of this, because we don’t know anything about the markup of that form.

You’re absolutely right about the importance of making web forms user-friendly. Since some users are likely to have disabilities, it is also important to make them accessible. There is plenty of information about accessible forms out there, but here are a couple of trusty recommendations: Accessible forms by Roger Hudson at http://www.usability.com.au/resources/forms.cfm, and WebAIM’s article on creating accessible forms at http://webaim.org/techniques/forms/

cheers
Iza</description>
		<content:encoded><![CDATA[Hi Bogdan,<br />
Your post has been up for a while, but there are a couple of points I would like to follow-up on. The first one concerns the &#8216;inline labels&#8217;. You&#8217;ve identified the usability issues, and Ben picked on the potential accessibility problems with this approach. I just wanted to add that anyone wishing to use this technique should check out Terrill Thompson’s page first: <a href="http://terrillthompson.blogspot.com/2011/01/testing-accessibility-of-pre-populated.html" rel="nofollow">http://terrillthompson.blogspot.com/2011/01/testing-accessibility-of-pre-populated.html</a><br />
<br />
The second point is about the accessibility of top-aligned labels raised by Ben. He is right, this form would create problems for the screen reader users IF a table was used for layout, the labels and the corresponding fields were sitting in separate rows, and the label markup was missing. However, we can’t be certain of this, because we don’t know anything about the markup of that form.<br />
<br />
You’re absolutely right about the importance of making web forms user-friendly. Since some users are likely to have disabilities, it is also important to make them accessible. There is plenty of information about accessible forms out there, but here are a couple of trusty recommendations: Accessible forms by Roger Hudson at <a href="http://www.usability.com.au/resources/forms.cfm" rel="nofollow">http://www.usability.com.au/resources/forms.cfm</a>, and WebAIM’s article on creating accessible forms at <a href="http://webaim.org/techniques/forms/" rel="nofollow">http://webaim.org/techniques/forms/</a><br />
<br />
cheers<br />
Iza]]></content:encoded>
	</item>
	<item>
		<title>By: Bogdan Pop</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1194</link>
		<dc:creator>Bogdan Pop</dc:creator>
		<pubDate>Fri, 26 Mar 2010 19:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1194</guid>
		<description>Hi Caroline,

Many many thanks for your comment! It&#039;s a great honor for me to see such great authors stumble on the articles I write and take the time to comment them.

I can&#039;t wait to get some spare time to read your book (Forms that Work). Bought it a couple of weeks back but didn&#039;t get to reading it.

Thanks again,
Bogdan Pop</description>
		<content:encoded><![CDATA[Hi Caroline,<br />
<br />
Many many thanks for your comment! It&#8217;s a great honor for me to see such great authors stumble on the articles I write and take the time to comment them.<br />
<br />
I can&#8217;t wait to get some spare time to read your book (Forms that Work). Bought it a couple of weeks back but didn&#8217;t get to reading it.<br />
<br />
Thanks again,<br />
Bogdan Pop]]></content:encoded>
	</item>
	<item>
		<title>By: Caroline Jarrett</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1193</link>
		<dc:creator>Caroline Jarrett</dc:creator>
		<pubDate>Fri, 26 Mar 2010 18:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1193</guid>
		<description>Hi,

It&#039;s great to see an article about label placement in forms that encourages people to think about the questions themselves, whether they need long or short labels, and the overall balance of the form. Great stuff!

As well as Mario&#039;s piece, which is looking solely at time to read the label, you might be interested in my article that also looks at what the label says.

http://www.usabilitynews.com/news/article3507.asp

Overall: remember that people are much more likely to bail out of forms or give inaccurate answers because of what the questions are asking than because of where the labels are placed.

Best
Caroline Jarrett</description>
		<content:encoded><![CDATA[Hi,<br />
<br />
It&#8217;s great to see an article about label placement in forms that encourages people to think about the questions themselves, whether they need long or short labels, and the overall balance of the form. Great stuff!<br />
<br />
As well as Mario&#8217;s piece, which is looking solely at time to read the label, you might be interested in my article that also looks at what the label says.<br />
<br />
<a href="http://www.usabilitynews.com/news/article3507.asp" rel="nofollow">http://www.usabilitynews.com/news/article3507.asp</a><br />
<br />
Overall: remember that people are much more likely to bail out of forms or give inaccurate answers because of what the questions are asking than because of where the labels are placed.<br />
<br />
Best<br />
Caroline Jarrett]]></content:encoded>
	</item>
	<item>
		<title>By: Impressive web forms. From coding to validation!</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1182</link>
		<dc:creator>Impressive web forms. From coding to validation!</dc:creator>
		<pubDate>Tue, 23 Mar 2010 17:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1182</guid>
		<description>[...] Today I&#039;ll tackle coding a good webform, styling it, client-side and server-side validating. The first part of the tutorial was extremely popular, and that&#039;s why I chose to merge parts two and three, which [...]</description>
		<content:encoded><![CDATA[[...] Today I&#39;ll tackle coding a good webform, styling it, client-side and server-side validating. The first part of the tutorial was extremely popular, and that&#39;s why I chose to merge parts two and three, which [...]]]></content:encoded>
	</item>
	<item>
		<title>By: 9 months stats</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1060</link>
		<dc:creator>9 months stats</dc:creator>
		<pubDate>Sat, 12 Dec 2009 08:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1060</guid>
		<description>[...] 2. Forms. Can’t live with them. Can’t live without them [...]</description>
		<content:encoded><![CDATA[[...] 2. Forms. Can’t live with them. Can’t live without them [...]]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-1000</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 10 Nov 2009 21:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-1000</guid>
		<description>Hi Ben. Thanks for the comment and thanks for being the coolest reader I have seen here since I launched! Your comment is really comprehensive and I appreciate your effort!

Now to address your comments.
&lt;strong&gt;&quot;Assuming you use dynamic text, cons #2 and #3 can be easily addressed with a bit of coding.&quot;&lt;/strong&gt;
I to agree with that too, and I think that a javascript solution would be sufficient. At least for this site, I recall that the percentage of browsers without javascript is under 2 or 3%.

&lt;strong&gt;&quot;Your point about browser screen resolution being “pretty big” doesn’t sound right to me.&quot; &lt;/strong&gt;
This depends. For example, stats for this site show that 98% of resolutions are larger than 1024*768 which is awesome. However, I run different sites for different clients and I have sites that have resolutions up to this as large as 60%, which is not that awesome anymore.

&lt;strong&gt;&quot;The cons for left-aligned labels can also be addressed. If it uses the “label” tag, clicking a form label should position the cursor in the relevant field.&quot;&lt;/strong&gt;
Hmmm. This cons is not about going through the form and using it (with mouse or keyboard) but as to how many eye fixations are required for the human brain to connect the label with its input field. Any implementation will not fix this eye fixations issue.

&lt;strong&gt;&quot;As for top-aligned labels, once again a major problem here is accessibly. A screen reader reads from left to right, so in your example it will say “First name, Last name” and then tell the user that there are two fields afterwards. It won’t say &gt;&gt;First name, field, Last name, field&lt;&lt;.&quot;&lt;/strong&gt;
This is interesting, and I must say that I haven&#039;t thought about that at all. Thanks for pointing it out.

&lt;strong&gt;&quot;Implementing &gt;&gt;subscribe to comments by email&lt;&lt; would be a useful addition to your blog&quot;&lt;/strong&gt;
Well, now that you said you want it, I have to do it. I&#039;ll let you know when it will be up and running (hopefully soon). I planned it for some time, but never got the time to do it.

&lt;strong&gt;&quot;IMO, your comment box is far too small.&quot;&lt;/strong&gt;
And once again a mistake from my part. The truth is I never expected such a through comment. I think I&#039;ll add a modal window for a larger textarea.

Once again, thanks for sharing your thoughts Ben!</description>
		<content:encoded><![CDATA[Hi Ben. Thanks for the comment and thanks for being the coolest reader I have seen here since I launched! Your comment is really comprehensive and I appreciate your effort!<br />
<br />
Now to address your comments.<br />
<strong>&#8220;Assuming you use dynamic text, cons #2 and #3 can be easily addressed with a bit of coding.&#8221;</strong><br />
I to agree with that too, and I think that a javascript solution would be sufficient. At least for this site, I recall that the percentage of browsers without javascript is under 2 or 3%.<br />
<br />
<strong>&#8220;Your point about browser screen resolution being “pretty big” doesn’t sound right to me.&#8221; </strong><br />
This depends. For example, stats for this site show that 98% of resolutions are larger than 1024*768 which is awesome. However, I run different sites for different clients and I have sites that have resolutions up to this as large as 60%, which is not that awesome anymore.<br />
<br />
<strong>&#8220;The cons for left-aligned labels can also be addressed. If it uses the “label” tag, clicking a form label should position the cursor in the relevant field.&#8221;</strong><br />
Hmmm. This cons is not about going through the form and using it (with mouse or keyboard) but as to how many eye fixations are required for the human brain to connect the label with its input field. Any implementation will not fix this eye fixations issue.<br />
<br />
<strong>&#8220;As for top-aligned labels, once again a major problem here is accessibly. A screen reader reads from left to right, so in your example it will say “First name, Last name” and then tell the user that there are two fields afterwards. It won’t say >>First name, field, Last name, field< <."</strong><br />
This is interesting, and I must say that I haven&#8217;t thought about that at all. Thanks for pointing it out.<br />
<br />
</strong><strong>&#8220;Implementing >>subscribe to comments by email< < would be a useful addition to your blog"</strong><br />
Well, now that you said you want it, I have to do it. I&#8217;ll let you know when it will be up and running (hopefully soon). I planned it for some time, but never got the time to do it.<br />
<br />
</strong><strong>&#8220;IMO, your comment box is far too small.&#8221;</strong><br />
And once again a mistake from my part. The truth is I never expected such a through comment. I think I&#8217;ll add a modal window for a larger textarea.<br />
<br />
Once again, thanks for sharing your thoughts Ben!]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.webia.info/articles/usability/forms-cant-live-with-them-cant-live-without-them/comment-page-1/#comment-999</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 10 Nov 2009 21:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=832#comment-999</guid>
		<description>Interesting post.

I&#039;ve never seen text within input fields that was anything other than dynamic. I didn&#039;t even realise people would use static text! Assuming you use dynamic text, cons #2 and #3 can be easily addressed with a bit of coding. The label text does go away, and it does come back, when you click into the field and click out of the field. But it would only come back if you didn&#039;t type anything. If you&#039;re familiar with Javascript, this is fairly simple to put together.

On the other hand, one drawback of dynamic text within input fields is that it won&#039;t work for users who disable Javascript, and the lack of a &quot;label&quot; tag will result in an inaccessible form.

Your point about browser screen resolution being &quot;pretty big&quot; doesn&#039;t sound right to me. Sure, larger monitors are available than in the early days of computers. But don&#039;t forget about mobile devices, such as the iPhone.

The cons for left-aligned labels can also be addressed. If it uses the &quot;label&quot; tag, clicking a form label should position the cursor in the relevant field. Unfortunately, few sites seem to implement this correctly, instead relying on plain text as a form guide. Again, this is inaccessible. As for increased horizontal space, this is down to the design of the form - even a very long label can be forced onto multiple lines. I prefer to put all form labels in a fairly narrow column on the left, and give the form fields plenty of breathing space. From your examples, I&#039;d say that right-aligned labels seem like a fairly good option if you keep the labels within a certain width.

As for top-aligned labels, once again a major problem here is accessibly. A screen reader reads from left to right, so in your example it will say &quot;First name, Last name&quot; and then tell the user that there are two fields afterwards. It won&#039;t say &quot;First name, field, Last name, field&quot;.

PS Implementing &quot;subscribe to comments by email&quot; would be a useful addition to your blog

PPS IMO, your comment box is far too small.</description>
		<content:encoded><![CDATA[Interesting post.<br />
<br />
I&#8217;ve never seen text within input fields that was anything other than dynamic. I didn&#8217;t even realise people would use static text! Assuming you use dynamic text, cons #2 and #3 can be easily addressed with a bit of coding. The label text does go away, and it does come back, when you click into the field and click out of the field. But it would only come back if you didn&#8217;t type anything. If you&#8217;re familiar with Javascript, this is fairly simple to put together.<br />
<br />
On the other hand, one drawback of dynamic text within input fields is that it won&#8217;t work for users who disable Javascript, and the lack of a &#8220;label&#8221; tag will result in an inaccessible form.<br />
<br />
Your point about browser screen resolution being &#8220;pretty big&#8221; doesn&#8217;t sound right to me. Sure, larger monitors are available than in the early days of computers. But don&#8217;t forget about mobile devices, such as the iPhone.<br />
<br />
The cons for left-aligned labels can also be addressed. If it uses the &#8220;label&#8221; tag, clicking a form label should position the cursor in the relevant field. Unfortunately, few sites seem to implement this correctly, instead relying on plain text as a form guide. Again, this is inaccessible. As for increased horizontal space, this is down to the design of the form &#8211; even a very long label can be forced onto multiple lines. I prefer to put all form labels in a fairly narrow column on the left, and give the form fields plenty of breathing space. From your examples, I&#8217;d say that right-aligned labels seem like a fairly good option if you keep the labels within a certain width.<br />
<br />
As for top-aligned labels, once again a major problem here is accessibly. A screen reader reads from left to right, so in your example it will say &#8220;First name, Last name&#8221; and then tell the user that there are two fields afterwards. It won&#8217;t say &#8220;First name, field, Last name, field&#8221;.<br />
<br />
PS Implementing &#8220;subscribe to comments by email&#8221; would be a useful addition to your blog<br />
<br />
PPS IMO, your comment box is far too small.]]></content:encoded>
	</item>
</channel>
</rss>

