<?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: Explaining whitespace</title>
	<atom:link href="http://www.onenaught.com/posts/24/explaining-whitespace/feed" rel="self" type="application/rss+xml" />
	<link>http://www.onenaught.com/posts/24/explaining-whitespace</link>
	<description>A blog on web standards, accessibility, css, javascript, xslt, and more</description>
	<pubDate>Fri, 29 Aug 2008 03:12:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Anup Shah</title>
		<link>http://www.onenaught.com/posts/24/explaining-whitespace#comment-283</link>
		<dc:creator>Anup Shah</dc:creator>
		<pubDate>Fri, 12 Oct 2007 17:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/24/explaining-whitespace#comment-283</guid>
		<description>Sam: you make a good point. I think this is a common problem, too.

A large client I worked with suffered from this problem all the time. It was their &lt;em&gt;marketing&lt;/em&gt; department that complained to me when I was giving them a training course on accessibility that other parts of the business were demanding all the pixels be used up!

When the accessibility and usability benefits of white space was explained to them, or additional points given (as many appreciated the importance), they felt better armed with information to go back to their business with.

In about a year or so (quick time for such a large organisation!) I was pleasantly surprised at the changes they made to their various home/landing pages. Less certainly felt like more in that case.</description>
		<content:encoded><![CDATA[<p>Sam: you make a good point. I think this is a common problem, too.</p>
<p>A large client I worked with suffered from this problem all the time. It was their <em>marketing</em> department that complained to me when I was giving them a training course on accessibility that other parts of the business were demanding all the pixels be used up!</p>
<p>When the accessibility and usability benefits of white space was explained to them, or additional points given (as many appreciated the importance), they felt better armed with information to go back to their business with.</p>
<p>In about a year or so (quick time for such a large organisation!) I was pleasantly surprised at the changes they made to their various home/landing pages. Less certainly felt like more in that case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sam</title>
		<link>http://www.onenaught.com/posts/24/explaining-whitespace#comment-280</link>
		<dc:creator>sam</dc:creator>
		<pubDate>Fri, 12 Oct 2007 09:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/24/explaining-whitespace#comment-280</guid>
		<description>The problem I've found when working on sites for a big organisations is that every dept wants their spot on the homepage and wants it above the fold. I've had this debate for a while, but I generally end up losing, which ends up with over complex homepages. 

It also raises the issue of who owns a site, how much should a designer answer to marketing or to the CEO. Unfortunately designers are often bottom of the pecking order.</description>
		<content:encoded><![CDATA[<p>The problem I&#8217;ve found when working on sites for a big organisations is that every dept wants their spot on the homepage and wants it above the fold. I&#8217;ve had this debate for a while, but I generally end up losing, which ends up with over complex homepages. </p>
<p>It also raises the issue of who owns a site, how much should a designer answer to marketing or to the CEO. Unfortunately designers are often bottom of the pecking order.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
