<?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"
	>
<channel>
	<title>Comments on: Checkout forms: Address1 vs. Address2</title>
	<atom:link href="http://www.lunametrics.com/blog/2006/06/06/checkout-forms-address1-vs-address2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lunametrics.com/blog/2006/06/06/checkout-forms-address1-vs-address2/</link>
	<description>LunaMetric's blog on conversion rate and web analytics</description>
	<pubDate>Tue, 06 Jan 2009 06:36:18 +0000</pubDate>
	<generator>http://wordpress.org/</generator>
		<item>
		<title>By: LunaMetrics Blog</title>
		<link>http://www.lunametrics.com/blog/2006/06/06/checkout-forms-address1-vs-address2/#comment-91</link>
		<dc:creator>LunaMetrics Blog</dc:creator>
		<pubDate>Wed, 07 Jun 2006 01:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://72.22.16.69/blog/?p=153#comment-91</guid>
		<description>Nah, I have enough challenges already &lt;B&gt;but&lt;/B&gt; the next time I am doing user testing that includes an e-commerce form, I'll definitely propose an option and see what the user says/does. I'll tell them, "Clint requested this special piece of info."&lt;BR/&gt;&lt;BR/&gt;RFS</description>
		<content:encoded><![CDATA[<p>Nah, I have enough challenges already <b>but</b> the next time I am doing user testing that includes an e-commerce form, I&#8217;ll definitely propose an option and see what the user says/does. I&#8217;ll tell them, &#8220;Clint requested this special piece of info.&#8221;</p>
<p>RFS</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://www.lunametrics.com/blog/2006/06/06/checkout-forms-address1-vs-address2/#comment-92</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 06 Jun 2006 23:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://72.22.16.69/blog/?p=153#comment-92</guid>
		<description>I agree that the form element sizing is a nice clue to the form's intended use but I wonder at the wisdom of leaving the second address line blank. By common usage, pain and experience adults have learned to cope with deciphering the second address line - which, unless I am mistaken, is typically for something like an apartment number, suite number, or some other important piece of information that will direct the shipment to the correct place.&lt;BR/&gt;&lt;BR/&gt;I don't necessarily have an answer, so I challange you, Robbin, to come up with a concise and effective label for the second address line.&lt;BR/&gt;&lt;BR/&gt;An effective label along with a form length clue will do much better at indicating the form's use than either alone.&lt;BR/&gt;&lt;BR/&gt;;~)</description>
		<content:encoded><![CDATA[<p>I agree that the form element sizing is a nice clue to the form&#8217;s intended use but I wonder at the wisdom of leaving the second address line blank. By common usage, pain and experience adults have learned to cope with deciphering the second address line - which, unless I am mistaken, is typically for something like an apartment number, suite number, or some other important piece of information that will direct the shipment to the correct place.</p>
<p>I don&#8217;t necessarily have an answer, so I challange you, Robbin, to come up with a concise and effective label for the second address line.</p>
<p>An effective label along with a form length clue will do much better at indicating the form&#8217;s use than either alone.</p>
<p>;~)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
