<?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: Primary &amp; Secondary Actions in Web Forms</title>
	<atom:link href="http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: tommy australien</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-258054</link>
		<dc:creator>tommy australien</dc:creator>
		<pubDate>Thu, 01 Nov 2007 07:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-258054</guid>
		<description>Neat article, but as for the examples I&#039;d agree with em_te. Get rid of the &quot;cancel&quot; button altogether as in 99% of all cases it is not needed. Simply because everyone else does it, does not mean you have to do so also, something that struck me a while ago.
Consequently I redesigned a few froms and projects, reducing the number of buttons, which may have been redundant or missleading.
When it comes to usability, less often is more.</description>
		<content:encoded><![CDATA[<p>Neat article, but as for the examples I&#8217;d agree with em_te. Get rid of the &#8220;cancel&#8221; button altogether as in 99% of all cases it is not needed. Simply because everyone else does it, does not mean you have to do so also, something that struck me a while ago.<br />
Consequently I redesigned a few froms and projects, reducing the number of buttons, which may have been redundant or missleading.<br />
When it comes to usability, less often is more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Davies</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-255079</link>
		<dc:creator>Richard Davies</dc:creator>
		<pubDate>Thu, 06 Sep 2007 16:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-255079</guid>
		<description>Where was this post last week when I was desperately searching the web for information like this to help me out with a current project? ;-)</description>
		<content:encoded><![CDATA[<p>Where was this post last week when I was desperately searching the web for information like this to help me out with a current project? ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barnaby Claydon</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-255045</link>
		<dc:creator>Barnaby Claydon</dc:creator>
		<pubDate>Thu, 06 Sep 2007 03:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-255045</guid>
		<description>The requirement for &quot;Cancel&quot; is entirely dependant on the type of application. We&#039;re not really privy to the user flow in this study with only this one page being used. You would have to give the users an indirect reason to utilize the &quot;Cancel&quot; button to be able to /fully/ assess the usability, but one a simple sign-up page such as this 99% of all web users would simply click their browser&#039;s back button; &quot;Cancel&quot; only comes into play in the midst of a multi-step flow.

Anyway, I thought the differences in alignment were telling although somewhat predictable.</description>
		<content:encoded><![CDATA[<p>The requirement for &#8220;Cancel&#8221; is entirely dependant on the type of application. We&#8217;re not really privy to the user flow in this study with only this one page being used. You would have to give the users an indirect reason to utilize the &#8220;Cancel&#8221; button to be able to /fully/ assess the usability, but one a simple sign-up page such as this 99% of all web users would simply click their browser&#8217;s back button; &#8220;Cancel&#8221; only comes into play in the midst of a multi-step flow.</p>
<p>Anyway, I thought the differences in alignment were telling although somewhat predictable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sensei Loco</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-255021</link>
		<dc:creator>Sensei Loco</dc:creator>
		<pubDate>Wed, 05 Sep 2007 16:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-255021</guid>
		<description>My first reaction is that the buttons&#039; order should be swapped. Cancel -&gt; Esc, Submit -&gt; Return
Then again, I kinda agree that the Cancel button prob shouldn&#039;t even be there.</description>
		<content:encoded><![CDATA[<p>My first reaction is that the buttons&#8217; order should be swapped. Cancel -&gt; Esc, Submit -&gt; Return<br />
Then again, I kinda agree that the Cancel button prob shouldn&#8217;t even be there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Searle</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-255003</link>
		<dc:creator>Searle</dc:creator>
		<pubDate>Wed, 05 Sep 2007 11:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-255003</guid>
		<description>I don&#039;t think the test is thought out well. This is why:

- Users are used to recognise grayed UI elements as &quot;not available&quot;. Using gray is wrong. A lighter color would be better, maybe.

- Tests with images are missing completly. Placing e.g. a &quot;Arrow to the Right&quot; icon next to &quot;Submit&quot; (but inside the button) makes the button intuitively primary, in my opion.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think the test is thought out well. This is why:</p>
<p>- Users are used to recognise grayed UI elements as &#8220;not available&#8221;. Using gray is wrong. A lighter color would be better, maybe.</p>
<p>- Tests with images are missing completly. Placing e.g. a &#8220;Arrow to the Right&#8221; icon next to &#8220;Submit&#8221; (but inside the button) makes the button intuitively primary, in my opion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin L</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254997</link>
		<dc:creator>Justin L</dc:creator>
		<pubDate>Wed, 05 Sep 2007 09:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254997</guid>
		<description>I see it&#039;s fashionable at the moment to use plain links for cancel, or secondry actions - ala facebook, basecamp. but why are these secondary anyway? The actions themselves are pretty black and white</description>
		<content:encoded><![CDATA[<p>I see it&#8217;s fashionable at the moment to use plain links for cancel, or secondry actions &#8211; ala facebook, basecamp. but why are these secondary anyway? The actions themselves are pretty black and white</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Peavy</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254985</link>
		<dc:creator>Will Peavy</dc:creator>
		<pubDate>Wed, 05 Sep 2007 02:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254985</guid>
		<description>From a usability standpoint - I think it is best to not use buttons that say Cancel / Clear / Reset ... etc. These types of buttons are rarely &lt;i&gt;intentionally&lt;/i&gt; used, and are more likely to be accidentaly clicked in place of the Submit button.</description>
		<content:encoded><![CDATA[<p>From a usability standpoint &#8211; I think it is best to not use buttons that say Cancel / Clear / Reset &#8230; etc. These types of buttons are rarely <i>intentionally</i> used, and are more likely to be accidentaly clicked in place of the Submit button.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254982</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Wed, 05 Sep 2007 01:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254982</guid>
		<description>@dwhsix: Not a contradiction really. Option B was the quickest from start to finish. This is because users just presumed the placement of the buttons at the bottom, automatically clicking on the left, ignoring the right. This is backed up by the failure in option E where the buttons are reversed.

As option A and C had a different visual element (cancel), the user had to slow down to understand the function of this rogue visual element. As such, these designs help ensure that the user clicks the correct button.

So, B is quicker but A and C are more accurate. This is what Luke is getting at.</description>
		<content:encoded><![CDATA[<p>@dwhsix: Not a contradiction really. Option B was the quickest from start to finish. This is because users just presumed the placement of the buttons at the bottom, automatically clicking on the left, ignoring the right. This is backed up by the failure in option E where the buttons are reversed.</p>
<p>As option A and C had a different visual element (cancel), the user had to slow down to understand the function of this rogue visual element. As such, these designs help ensure that the user clicks the correct button.</p>
<p>So, B is quicker but A and C are more accurate. This is what Luke is getting at.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bmiedlar</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254966</link>
		<dc:creator>bmiedlar</dc:creator>
		<pubDate>Tue, 04 Sep 2007 20:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254966</guid>
		<description>It would be interesting to see if right alignment would have equal success if the buttons were reversed in order.</description>
		<content:encoded><![CDATA[<p>It would be interesting to see if right alignment would have equal success if the buttons were reversed in order.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dwhsix</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254958</link>
		<dc:creator>dwhsix</dc:creator>
		<pubDate>Tue, 04 Sep 2007 18:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254958</guid>
		<description>Luke&#039;s article and study looks very impressive, with lots of fancy graphics and &#039;fixations&#039; and heat maps.  But if you read it closely, the empirical evidence contradicts the claim he puts forth.

He claims &lt;blockquote&gt;...the best practice Iâ€™ve advocated has been to visually distinguish primary and secondary actions ... Reducing the visual prominence of secondary actions minimizes the risk for potential errors and further directs people toward a successful outcome.&lt;/blockquote&gt;

But from the data they collected, they concluded: &lt;blockquote&gt;Option B performed best of all. Fixations were shorter and fewer in number when using this design. And people were also able to complete the task more quickly and efficiently than they did when using the others.&lt;/blockquote&gt;

What was Option B?  The one where the secondary action had, in fact, just as much weight as the primary action (same button style, left justified).</description>
		<content:encoded><![CDATA[<p>Luke&#8217;s article and study looks very impressive, with lots of fancy graphics and &#8216;fixations&#8217; and heat maps.  But if you read it closely, the empirical evidence contradicts the claim he puts forth.</p>
<p>He claims<br />
<blockquote>&#8230;the best practice Iâ€™ve advocated has been to visually distinguish primary and secondary actions &#8230; Reducing the visual prominence of secondary actions minimizes the risk for potential errors and further directs people toward a successful outcome.</p></blockquote>
<p>But from the data they collected, they concluded:<br />
<blockquote>Option B performed best of all. Fixations were shorter and fewer in number when using this design. And people were also able to complete the task more quickly and efficiently than they did when using the others.</p></blockquote>
<p>What was Option B?  The one where the secondary action had, in fact, just as much weight as the primary action (same button style, left justified).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254957</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 04 Sep 2007 18:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254957</guid>
		<description>Yes - it would have been interesting to just remove the &quot;Cancel&quot; button/link altogether and see how users reacted.</description>
		<content:encoded><![CDATA[<p>Yes &#8211; it would have been interesting to just remove the &#8220;Cancel&#8221; button/link altogether and see how users reacted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: em_te</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254944</link>
		<dc:creator>em_te</dc:creator>
		<pubDate>Tue, 04 Sep 2007 16:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254944</guid>
		<description>What if someone actually wanted to &quot;cancel&quot; in design A. Would they be more likely to click the link or hit their browser&#039;s back button? Maybe that&#039;s why design A is so good. Because the user begins to see in buttons and completely ignores links, making the link useless, which means the user really only has to deal with 1 action.</description>
		<content:encoded><![CDATA[<p>What if someone actually wanted to &#8220;cancel&#8221; in design A. Would they be more likely to click the link or hit their browser&#8217;s back button? Maybe that&#8217;s why design A is so good. Because the user begins to see in buttons and completely ignores links, making the link useless, which means the user really only has to deal with 1 action.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liming</title>
		<link>http://ajaxian.com/archives/primary-secondary-actions-in-web-forms/comment-page-1#comment-254933</link>
		<dc:creator>Liming</dc:creator>
		<pubDate>Tue, 04 Sep 2007 14:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2742#comment-254933</guid>
		<description>Very interesting topic. When we designed our software, our designer went through similar case studies, wish we had this discussions back then.</description>
		<content:encoded><![CDATA[<p>Very interesting topic. When we designed our software, our designer went through similar case studies, wish we had this discussions back then.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

