<?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: Conversion practices and usability</title>
	<atom:link href="http://www.lunametrics.com/blog/2006/03/15/conversion-practices-and-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lunametrics.com/blog/2006/03/15/conversion-practices-and-usability/</link>
	<description>Traffic, Analysis, Action</description>
	<lastBuildDate>Sat, 11 Feb 2012 09:49:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Randy Ziegler</title>
		<link>http://www.lunametrics.com/blog/2006/03/15/conversion-practices-and-usability/comment-page-1/#comment-111</link>
		<dc:creator>Randy Ziegler</dc:creator>
		<pubDate>Thu, 16 Mar 2006 15:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://72.22.16.69/blog/?p=94#comment-111</guid>
		<description>To continue the friendly debate, I&#039;d like to respond from a designer&#039;s persepctive to your points.&lt;BR/&gt;&lt;BR/&gt;1. RE: Don&#039;t write long text, people don&#039;t read it&quot;&lt;BR/&gt;While I agree that readers will tolerate long narrative if it&#039;s valuable content, my concern has to do more with chunking information to provide multiple points of accessâ€”and better at-a-glance understanding. It&#039;s a usability and access issue. Long narrative doesn&#039;t provide visual handles for readers to skim and quickly find information that really matters to them.&lt;BR/&gt;&lt;BR/&gt;2. RE: Blue, underline links. And Lots of hyperlinks.&lt;BR/&gt;You&#039;re right. We&#039;ve been conditioned. Blue, underline links are commonly understood as links. My concern is more of an issue of quantity. Don&#039;t go overboard. Be judicious. Don&#039;t get sloppy with throwing links on everything. Otherwise the page look will look like it has blue chicken pox. We&#039;ve all seen it before. The overall affect is confusion. I think even Spool&#039;s research has demonstrated that too many navigation choices affect usability. Each link interrupts the reader&#039;s thought process, if only for a moment, to consider the value and utility of the link.&lt;BR/&gt;&lt;BR/&gt;Glad you enjoyed the conference!</description>
		<content:encoded><![CDATA[<div style="clear: both; background-color: #E7EDFE; padding: 1em 1em 0.5em 1em;">
<p>To continue the friendly debate, I&#8217;d like to respond from a designer&#8217;s persepctive to your points.</p>
<p>1. RE: Don&#8217;t write long text, people don&#8217;t read it&#8221;<br />While I agree that readers will tolerate long narrative if it&#8217;s valuable content, my concern has to do more with chunking information to provide multiple points of accessâ€”and better at-a-glance understanding. It&#8217;s a usability and access issue. Long narrative doesn&#8217;t provide visual handles for readers to skim and quickly find information that really matters to them.</p>
<p>2. RE: Blue, underline links. And Lots of hyperlinks.<br />You&#8217;re right. We&#8217;ve been conditioned. Blue, underline links are commonly understood as links. My concern is more of an issue of quantity. Don&#8217;t go overboard. Be judicious. Don&#8217;t get sloppy with throwing links on everything. Otherwise the page look will look like it has blue chicken pox. We&#8217;ve all seen it before. The overall affect is confusion. I think even Spool&#8217;s research has demonstrated that too many navigation choices affect usability. Each link interrupts the reader&#8217;s thought process, if only for a moment, to consider the value and utility of the link.</p>
<p>Glad you enjoyed the conference!</p>
</div>
]]></content:encoded>
	</item>
</channel>
</rss>

