<?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: Fade-to-Gray to Improve Experience</title>
	<atom:link href="http://www.grokdotcom.com/index.php/2007/05/02/fade-to-gray-to-improve-experience/feed" rel="self" type="application/rss+xml" />
	<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/</link>
	<description>Marketing blog focused on marketing optimization, improving website conversion rates, search engine marketing, web analytics, word of mouth, etc.</description>
	<lastBuildDate>Sat, 21 Nov 2009 19:57:59 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Boomer</title>
		<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/comment-page-1/#comment-43095</link>
		<dc:creator>Paul Boomer</dc:creator>
		<pubDate>Thu, 03 May 2007 12:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/#comment-43095</guid>
		<description>It is amazing to find so many warnings and notices on forms – most of the time they make me feel anxious about accidentally double clicking (“is it going to blow up?”).

Something I’ve started to talk with people about is if a form will take more than just a second to process, send them to a ‘middle page’ much like what Travelocity.com does when you search for a flight.  Yes, you can use java and other code techniques to grey out a button, but what happens if the person has disabled java… where does that leave your visitor?  Sending them to a middle page allows a business to settle visitors’ nerves down and may provide an opportunity to deepen their relationship with the visitor and provide them with more info about the business or some other piece of relevant information.  

I will say, I have not yet tested the effectiveness of any of the above… but I plan too.</description>
		<content:encoded><![CDATA[<p>It is amazing to find so many warnings and notices on forms – most of the time they make me feel anxious about accidentally double clicking (“is it going to blow up?”).</p>
<p>Something I’ve started to talk with people about is if a form will take more than just a second to process, send them to a ‘middle page’ much like what Travelocity.com does when you search for a flight.  Yes, you can use java and other code techniques to grey out a button, but what happens if the person has disabled java… where does that leave your visitor?  Sending them to a middle page allows a business to settle visitors’ nerves down and may provide an opportunity to deepen their relationship with the visitor and provide them with more info about the business or some other piece of relevant information.  </p>
<p>I will say, I have not yet tested the effectiveness of any of the above… but I plan too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Václav</title>
		<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/comment-page-1/#comment-42728</link>
		<dc:creator>Václav</dc:creator>
		<pubDate>Thu, 03 May 2007 04:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/#comment-42728</guid>
		<description>Another good way how to prevent people from clicking any button while processing data is to show them that something is happening right now (and therefore they should wait and do nothing). This can be neatly done by animated progress bar with JavaScript loader.

I would prefer this solution to yours, because it doesn&#039;t demage the standard behaviour of Web page elements.</description>
		<content:encoded><![CDATA[<p>Another good way how to prevent people from clicking any button while processing data is to show them that something is happening right now (and therefore they should wait and do nothing). This can be neatly done by animated progress bar with JavaScript loader.</p>
<p>I would prefer this solution to yours, because it doesn&#8217;t demage the standard behaviour of Web page elements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Cahalan</title>
		<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/comment-page-1/#comment-42407</link>
		<dc:creator>Tom Cahalan</dc:creator>
		<pubDate>Wed, 02 May 2007 19:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/#comment-42407</guid>
		<description>As far as I&#039;m aware, Bill, it may change the image once they&#039;ve clicked on the button, but it won&#039;t actually disable the image from being clicked.  So, people are still able to click on it again, even though less hopefully will, as it appears greyed out.  

I may be wrong, though.</description>
		<content:encoded><![CDATA[<p>As far as I&#8217;m aware, Bill, it may change the image once they&#8217;ve clicked on the button, but it won&#8217;t actually disable the image from being clicked.  So, people are still able to click on it again, even though less hopefully will, as it appears greyed out.  </p>
<p>I may be wrong, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor</title>
		<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/comment-page-1/#comment-41857</link>
		<dc:creator>Victor</dc:creator>
		<pubDate>Wed, 02 May 2007 02:45:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/#comment-41857</guid>
		<description>That is the most hilarious point of assurance message I have ever read! Sadly, the first shopping cart software I ever used was guilty of the same faux pas. 

While playing with money is like playing with people&#039;s emotions - there is one common usability blunder that continuously annoys me.
If there is one thing I hate in this world, it would be DVD menu systems. Sometimes they can be so intrusive, and so animation-intensive, that they have literally caused me to hate certain movies. Compared to how websites have changed over the years, DVD menu systems are almost exactly the same. The solution to this problem? Video on Demand (though Viacom is calling the shots here).</description>
		<content:encoded><![CDATA[<p>That is the most hilarious point of assurance message I have ever read! Sadly, the first shopping cart software I ever used was guilty of the same faux pas. </p>
<p>While playing with money is like playing with people&#8217;s emotions &#8211; there is one common usability blunder that continuously annoys me.<br />
If there is one thing I hate in this world, it would be DVD menu systems. Sometimes they can be so intrusive, and so animation-intensive, that they have literally caused me to hate certain movies. Compared to how websites have changed over the years, DVD menu systems are almost exactly the same. The solution to this problem? Video on Demand (though Viacom is calling the shots here).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bill</title>
		<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/comment-page-1/#comment-41825</link>
		<dc:creator>bill</dc:creator>
		<pubDate>Wed, 02 May 2007 01:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/#comment-41825</guid>
		<description>The idea is simple, and a very good one.  One challenge here is that there are still SO MANY sites that use images for their buttons.  This greyed out technique will not work on an image.  You could do something with the OnClick event that would swap images but... even something that seems so trivially easy like that usually touches pages that development only wants to touch on new releases.  Also... switching the button functionality like this on an entire site... is not a quick task. I would argue worth doing but... this could EASILY get put in the &quot;nice to have&quot; category by a lot of IT teams.</description>
		<content:encoded><![CDATA[<p>The idea is simple, and a very good one.  One challenge here is that there are still SO MANY sites that use images for their buttons.  This greyed out technique will not work on an image.  You could do something with the OnClick event that would swap images but&#8230; even something that seems so trivially easy like that usually touches pages that development only wants to touch on new releases.  Also&#8230; switching the button functionality like this on an entire site&#8230; is not a quick task. I would argue worth doing but&#8230; this could EASILY get put in the &#8220;nice to have&#8221; category by a lot of IT teams.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/comment-page-1/#comment-41729</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Tue, 01 May 2007 23:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/05/02/fade-to-gray-to-improve-experience/#comment-41729</guid>
		<description>Yes, this definitely improves usability. But I was just thinking, why don&#039;t the browsers do this automatically? If there is no javascript interfering, the browser could grey out the button. I cannot think of any case where this would be a bad idea, although I am sure that those cases exist :)</description>
		<content:encoded><![CDATA[<p>Yes, this definitely improves usability. But I was just thinking, why don&#8217;t the browsers do this automatically? If there is no javascript interfering, the browser could grey out the button. I cannot think of any case where this would be a bad idea, although I am sure that those cases exist <img src='http://www.grokdotcom.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
