<?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: Red Face&#8230;book</title>
	<atom:link href="http://www.foviance.com/what-we-think/red-facebook/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.foviance.com/what-we-think/red-facebook/</link>
	<description>Foviance is a ground-breaking customer experience consultancy, providing usability consulting services, web analytics, user experience and accessibility consultancy in London, UK.</description>
	<lastBuildDate>Fri, 20 Jan 2012 10:29:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Chris Holmes</title>
		<link>http://www.foviance.com/what-we-think/red-facebook/comment-page-1/#comment-3051</link>
		<dc:creator>Chris Holmes</dc:creator>
		<pubDate>Fri, 20 Feb 2009 12:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.foviance.com/?p=2065#comment-3051</guid>
		<description>Hi Gunter,

I faced exactly the same dilemma recently when testing a hotel reservation process. When presented with an entire page of terms and conditions users overwhelmingly requested to see just a basic summary of the salient points (cancellation policy, late check in/out, etc.) with a link to read the full terms and conditions if they so desired. The modified design tested extremely well in the next round.

A simple &quot;I have read and agree to the terms and conditions&quot; checkbox which must be ticked before submitting is surely enough to cover you from a legal perspective, but then again I&#039;m not a lawyer.

Thanks for the comment!</description>
		<content:encoded><![CDATA[<p>Hi Gunter,</p>
<p>I faced exactly the same dilemma recently when testing a hotel reservation process. When presented with an entire page of terms and conditions users overwhelmingly requested to see just a basic summary of the salient points (cancellation policy, late check in/out, etc.) with a link to read the full terms and conditions if they so desired. The modified design tested extremely well in the next round.</p>
<p>A simple &#8220;I have read and agree to the terms and conditions&#8221; checkbox which must be ticked before submitting is surely enough to cover you from a legal perspective, but then again I&#8217;m not a lawyer.</p>
<p>Thanks for the comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gunter T Straussman</title>
		<link>http://www.foviance.com/what-we-think/red-facebook/comment-page-1/#comment-3046</link>
		<dc:creator>Gunter T Straussman</dc:creator>
		<pubDate>Thu, 19 Feb 2009 22:57:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.foviance.com/?p=2065#comment-3046</guid>
		<description>Hi Chris

Another entertaining and timely article from a man who can use the phrase &quot;collective panties&quot; in reference to usable design.

I am currently working on the site design for a large multi-national organisation and we are in the midst of a fierce debate between user experience designers and lawyers, directly related to the implementation of a click wrap agreement.

The story...

Our lawyers have drafted three A4 pages of Terms of Use (presented within a small text box similar to the Foviance comments field), with a further requirement to force users into physically scrolling the entire Terms before the &quot;I Accept&quot; button is enabled.

When testing mock-ups of this design with users, the overwhelming feedback was that they are not interested in reading the Terms, find enforced design frustrating (i.e. not enabling the acceptance button until the Terms are &quot;read&quot;), yet still wished to understand the basic messages within the Terms.

Our design recommendation was to place adjacent to the Terms text box a dot-point summary of key information (for example, Your rights, Your responsibilities, Our responsibilities) and not force any scrolling of Terms before the user can click &quot;I Accept&quot;.

This compromise tested extremely well, with users feeling they understood enough of the basic facts to commit to accepting the Terms.

In the final phases of building this design, our lawyers have seen the implementation of the recommended Terms of Use design and deemed it unacceptable.

From a usability point of view, Im not keen on forcing a user to scroll the Terms. If a user wants to read the full Terms, they will read them. Otherwise, it’s just a hindrance to a user who just wants to get the job done.

From experience, lawyers always err on the side of more legal being better than less, regardless of the reality of situation. We can be as legal as we like, but if people don’t use the site cause it’s onerous, complex and confusing, its a fail all round.

Here lies the tension - real world usability or theoretical legal opinion?

You&#039;re thoughts, comments and free advice much appreciated.

Cheers, Gunter</description>
		<content:encoded><![CDATA[<p>Hi Chris</p>
<p>Another entertaining and timely article from a man who can use the phrase &#8220;collective panties&#8221; in reference to usable design.</p>
<p>I am currently working on the site design for a large multi-national organisation and we are in the midst of a fierce debate between user experience designers and lawyers, directly related to the implementation of a click wrap agreement.</p>
<p>The story&#8230;</p>
<p>Our lawyers have drafted three A4 pages of Terms of Use (presented within a small text box similar to the Foviance comments field), with a further requirement to force users into physically scrolling the entire Terms before the &#8220;I Accept&#8221; button is enabled.</p>
<p>When testing mock-ups of this design with users, the overwhelming feedback was that they are not interested in reading the Terms, find enforced design frustrating (i.e. not enabling the acceptance button until the Terms are &#8220;read&#8221;), yet still wished to understand the basic messages within the Terms.</p>
<p>Our design recommendation was to place adjacent to the Terms text box a dot-point summary of key information (for example, Your rights, Your responsibilities, Our responsibilities) and not force any scrolling of Terms before the user can click &#8220;I Accept&#8221;.</p>
<p>This compromise tested extremely well, with users feeling they understood enough of the basic facts to commit to accepting the Terms.</p>
<p>In the final phases of building this design, our lawyers have seen the implementation of the recommended Terms of Use design and deemed it unacceptable.</p>
<p>From a usability point of view, Im not keen on forcing a user to scroll the Terms. If a user wants to read the full Terms, they will read them. Otherwise, it’s just a hindrance to a user who just wants to get the job done.</p>
<p>From experience, lawyers always err on the side of more legal being better than less, regardless of the reality of situation. We can be as legal as we like, but if people don’t use the site cause it’s onerous, complex and confusing, its a fail all round.</p>
<p>Here lies the tension &#8211; real world usability or theoretical legal opinion?</p>
<p>You&#8217;re thoughts, comments and free advice much appreciated.</p>
<p>Cheers, Gunter</p>
]]></content:encoded>
	</item>
</channel>
</rss>

