<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips Article: Web Application Form Design</title>
	<atom:link href="http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Tue, 21 May 2013 10:35:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Roly</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-85764</link>
		<dc:creator>Roly</dc:creator>
		<pubDate>Thu, 23 Aug 2007 12:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-85764</guid>
		<description>Luke Wroblewski article does provide some guidelines to the &#039;labels&#039; on a form but unfortunately it does not provide any guidelines on the alignment of the form fields ie the characters within the fields. Should they be aligned to the left or the right? Is there a difference if all the field types are numerical? I researched about 50 website and the jury is still out with 50% aligning numerical form fields to the left.....Has anyone come across any evidence that these should be aligned to the left or the right?</description>
		<content:encoded><![CDATA[<p>Luke Wroblewski article does provide some guidelines to the &#8216;labels&#8217; on a form but unfortunately it does not provide any guidelines on the alignment of the form fields ie the characters within the fields. Should they be aligned to the left or the right? Is there a difference if all the field types are numerical? I researched about 50 website and the jury is still out with 50% aligning numerical form fields to the left&#8230;..Has anyone come across any evidence that these should be aligned to the left or the right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Personal Injury Attorney WebLog &#187; Blog Archive &#187; Integrate QuickBooks into a Customer Self-Service Portal</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-82906</link>
		<dc:creator>Personal Injury Attorney WebLog &#187; Blog Archive &#187; Integrate QuickBooks into a Customer Self-Service Portal</dc:creator>
		<pubDate>Sun, 22 Jul 2007 19:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-82906</guid>
		<description>[...] UIEtips Article: Web Application Form Design » UIE Brain Sparks &#8230; on users’ success with your web applications. Read today’s UIEtips article . Do you have &#8230; from your own site. 5 Responses to “ UIEtips Article: Web Application Form Design http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/ [...]</description>
		<content:encoded><![CDATA[<p>[...] UIEtips Article: Web Application Form Design » UIE Brain Sparks &#8230; on users’ success with your web applications. Read today’s UIEtips article . Do you have &#8230; from your own site. 5 Responses to “ UIEtips Article: Web Application Form Design <a href="http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/" rel="nofollow">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tmthai.com All you need for the Website!!!!&#187; Blog Archive &#187; Web Application Form Design</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-82533</link>
		<dc:creator>tmthai.com All you need for the Website!!!!&#187; Blog Archive &#187; Web Application Form Design</dc:creator>
		<pubDate>Wed, 18 Jul 2007 16:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-82533</guid>
		<description>[...] Send us your thoughts on this article on the UIE Brain Sparks blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Send us your thoughts on this article on the UIE Brain Sparks blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jermayn Parker</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-81844</link>
		<dc:creator>Jermayn Parker</dc:creator>
		<pubDate>Wed, 04 Jul 2007 05:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-81844</guid>
		<description>Very good points and to be honest I have never thought about those reasons but it makes sense.

However a few things I would like to raise:
1) I dont agree with Michael as I think the ...... makes the form to cluttered.
2) In the comment section you have the fields on the left and the field titles on the right. That could work nicely. Or do you think its messing with what we know too much?
3) Another option could be to keep the field titles in the actual field itself.

However in saying all that I do like the background solution.</description>
		<content:encoded><![CDATA[<p>Very good points and to be honest I have never thought about those reasons but it makes sense.</p>
<p>However a few things I would like to raise:<br />
1) I dont agree with Michael as I think the &#8230;&#8230; makes the form to cluttered.<br />
2) In the comment section you have the fields on the left and the field titles on the right. That could work nicely. Or do you think its messing with what we know too much?<br />
3) Another option could be to keep the field titles in the actual field itself.</p>
<p>However in saying all that I do like the background solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Selbie</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-81638</link>
		<dc:creator>Joseph Selbie</dc:creator>
		<pubDate>Thu, 28 Jun 2007 01:05:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-81638</guid>
		<description>In all enterprise web applications we&#039;ve designed over the years (e.g. Cisco, KPMG, Cartus) vertical space is always at a premium, making the placement of the label in the same horizontal alignment as the form field a necessity.

We&#039;ve designed using labels aligned left and aligned right against the form fields, and our users have consistently prefered the aligned right style. To overcome any difficulty in scanning, as Luke suggests is the disadvantage of the right alignment, we&#039;ve always limited the number of label/field combinations to 3 to 6 in any one sector or grouping within a form.

We have found that the logical grouping of label/field combinations -- and giving that group a name and sub-head within the form -- is more important than anything else to promote usability, efficiency, rapid scanning and lack of eye strain for users of large form screens.

Once you create groups of labels/fields make sure you align them consitently on a grid. This makes for a lot less &quot;eye ping-pong&quot; for your users.</description>
		<content:encoded><![CDATA[<p>In all enterprise web applications we&#8217;ve designed over the years (e.g. Cisco, KPMG, Cartus) vertical space is always at a premium, making the placement of the label in the same horizontal alignment as the form field a necessity.</p>
<p>We&#8217;ve designed using labels aligned left and aligned right against the form fields, and our users have consistently prefered the aligned right style. To overcome any difficulty in scanning, as Luke suggests is the disadvantage of the right alignment, we&#8217;ve always limited the number of label/field combinations to 3 to 6 in any one sector or grouping within a form.</p>
<p>We have found that the logical grouping of label/field combinations &#8212; and giving that group a name and sub-head within the form &#8212; is more important than anything else to promote usability, efficiency, rapid scanning and lack of eye strain for users of large form screens.</p>
<p>Once you create groups of labels/fields make sure you align them consitently on a grid. This makes for a lot less &#8220;eye ping-pong&#8221; for your users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Zuschlag</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-81492</link>
		<dc:creator>Michael Zuschlag</dc:creator>
		<pubDate>Wed, 27 Jun 2007 12:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-81492</guid>
		<description>I&#039;m inclined to agree with Wroblewski that shading is a too &quot;heavy&quot; solution for the problem of visually associating left-aligned labels with fields, but I&#039;d like to see it tested empirically before making any final conclusion. As for alternatives, there&#039;s one ancient solution from the era of dead tree media: leaders.
Label . . . . . . . . . . . [Field1]
Longer Label . . . . . [Field2]
Even Longer Label: [Field3]
I&#039;d like to see an experiment involving that too. Anyone out there looking for a senior thesis topic?</description>
		<content:encoded><![CDATA[<p>I&#8217;m inclined to agree with Wroblewski that shading is a too &#8220;heavy&#8221; solution for the problem of visually associating left-aligned labels with fields, but I&#8217;d like to see it tested empirically before making any final conclusion. As for alternatives, there&#8217;s one ancient solution from the era of dead tree media: leaders.<br />
Label . . . . . . . . . . . [Field1]<br />
Longer Label . . . . . [Field2]<br />
Even Longer Label: [Field3]<br />
I&#8217;d like to see an experiment involving that too. Anyone out there looking for a senior thesis topic?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blog.dsetia.com&#187; Blog Archive &#187; UIEtips Article: Web Application Form Design</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-81425</link>
		<dc:creator>blog.dsetia.com&#187; Blog Archive &#187; UIEtips Article: Web Application Form Design</dc:creator>
		<pubDate>Wed, 27 Jun 2007 06:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-81425</guid>
		<description>[...] UIEtips 6/26/07:  Web Application Form Design Luke Wroblewski discusses how variations in the alignment of input fields, labels, calls to action, and their surrounding visual elements can support or impair different aspects of user behavior. Source: [Link] [...]</description>
		<content:encoded><![CDATA[<p>[...] UIEtips 6/26/07:  Web Application Form Design Luke Wroblewski discusses how variations in the alignment of input fields, labels, calls to action, and their surrounding visual elements can support or impair different aspects of user behavior. Source: [Link] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jana Steiger</title>
		<link>http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/comment-page-1/#comment-81299</link>
		<dc:creator>Jana Steiger</dc:creator>
		<pubDate>Tue, 26 Jun 2007 19:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/06/26/uietips-article-web-application-form-design/#comment-81299</guid>
		<description>My form usability story is really more of a wizard story.  We have a rather lengthy e-mail alert creation process that used to live in a bunch of really long forms, and a couple of years ago we compacted these into a 5-step wizard.  It&#039;s nested inside our site navigation, so to prevent users from losing their work we added the requirement that a user who clicked a tab before their process was complete would be informed that their work was not saved, and given the choice to complete their alert or navigate away from it.

Well, our developers *hated* this requirement.  They said it made no sense, was not a web behavior, was next to impossible to implement, and amounted to putting our users in wizard jail.  No matter what rational arguments, best practices research, threats, cajoling, beer or tears we tried, we got nowhere, and this requirement was never built.

To this day, we refer to this battle of wills as &quot;the Azkaban issue.&quot;</description>
		<content:encoded><![CDATA[<p>My form usability story is really more of a wizard story.  We have a rather lengthy e-mail alert creation process that used to live in a bunch of really long forms, and a couple of years ago we compacted these into a 5-step wizard.  It&#8217;s nested inside our site navigation, so to prevent users from losing their work we added the requirement that a user who clicked a tab before their process was complete would be informed that their work was not saved, and given the choice to complete their alert or navigate away from it.</p>
<p>Well, our developers *hated* this requirement.  They said it made no sense, was not a web behavior, was next to impossible to implement, and amounted to putting our users in wizard jail.  No matter what rational arguments, best practices research, threats, cajoling, beer or tears we tried, we got nowhere, and this requirement was never built.</p>
<p>To this day, we refer to this battle of wills as &#8220;the Azkaban issue.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
