<?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 Form Design in the Wild, Part II</title>
	<atom:link href="http://www.uie.com/brainsparks/2007/10/12/uietips-article-web-form-design-in-the-wild-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2007/10/12/uietips-article-web-form-design-in-the-wild-part-ii/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Thu, 20 Jun 2013 04:03:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Paul Rouke</title>
		<link>http://www.uie.com/brainsparks/2007/10/12/uietips-article-web-form-design-in-the-wild-part-ii/comment-page-1/#comment-90732</link>
		<dc:creator>Paul Rouke</dc:creator>
		<pubDate>Sun, 14 Oct 2007 12:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/10/12/uietips-article-web-form-design-in-the-wild-part-ii/#comment-90732</guid>
		<description>Jarod, as you say these are 2 excellent articles on web form best practise. One of my most visited usability posts over the last few months was titled &lt;a href=&quot;http://www.paulrouke.co.uk/2007/05/05/form-field-best-practice-and-hints-to-assure-wary-users/&quot; rel=&quot;nofollow&quot;&gt;Form Field Best Practice and Hints to Assure Wary Users&lt;/a&gt;. This supports a lot of what Luke advises on, and the post had a particular emphasis on transactional websites and the checkout process. For instance:


explaining why certain information is being asked for
removing un-necssary inputs
providing context sensitive and inline feedback to the visitor
emphasising calls to actions which lead to form completion


In summary I would just like to add the summary of my views on web forms (taken from my post):

&lt;em&gt;Although in principle forms are simply different drop downs, text entry boxes and preference setting checkboxes and radio buttons, the visual and coding execution of forms can be the difference between an abandoned shopping journey and a new customer transaction, registration or application.&lt;/em&gt;

I hope this has been useful!</description>
		<content:encoded><![CDATA[<p>Jarod, as you say these are 2 excellent articles on web form best practise. One of my most visited usability posts over the last few months was titled <a href="http://www.paulrouke.co.uk/2007/05/05/form-field-best-practice-and-hints-to-assure-wary-users/" rel="nofollow">Form Field Best Practice and Hints to Assure Wary Users</a>. This supports a lot of what Luke advises on, and the post had a particular emphasis on transactional websites and the checkout process. For instance:</p>
<p>explaining why certain information is being asked for<br />
removing un-necssary inputs<br />
providing context sensitive and inline feedback to the visitor<br />
emphasising calls to actions which lead to form completion</p>
<p>In summary I would just like to add the summary of my views on web forms (taken from my post):</p>
<p><em>Although in principle forms are simply different drop downs, text entry boxes and preference setting checkboxes and radio buttons, the visual and coding execution of forms can be the difference between an abandoned shopping journey and a new customer transaction, registration or application.</em></p>
<p>I hope this has been useful!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
