<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blagophilia &#187; design</title>
	<atom:link href="http://www.blagosphere.org/larry/tag/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blagosphere.org/larry</link>
	<description>For the Love of Blagging</description>
	<lastBuildDate>Sat, 02 Jan 2010 07:21:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>On Color and User Interfaces &#8211; My Personal Do&#8217;s and Don&#8217;ts</title>
		<link>http://www.blagosphere.org/larry/92-on-color-and-user-interfaces-my-personal-dos-and-donts/</link>
		<comments>http://www.blagosphere.org/larry/92-on-color-and-user-interfaces-my-personal-dos-and-donts/#comments</comments>
		<pubDate>Sun, 12 Oct 2008 19:42:00 +0000</pubDate>
		<dc:creator>larry</dc:creator>
				<category><![CDATA[Drunken Blogging]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Teh Internets]]></category>
		<category><![CDATA[color]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[list]]></category>
		<category><![CDATA[user interface]]></category>

		<guid isPermaLink="false">http://www.blagosphere.org/larry/92-on-color-and-user-interfaces-my-personal-dos-and-donts/</guid>
		<description><![CDATA[I was recently reminded of the importance of color, contrast, and placement in a user interface from some things I have seen at work. That is the importance of of using correct color combinations. I mean really it is not that hard to figure out what colors go together. When I lived in San Diego [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Arial;">I was recently reminded of the importance of color, contrast, and placement in a user interface from some things I have seen at work. That is the importance of of using correct color combinations. I mean really it is not that hard to figure out what colors go together. When I lived in San Diego I was involved with UI design from mostly a web perspective but was also a part of studies to figure out what worked.</span></p>
<p><span style="font-family: Arial;">Based on the stellar examples from work and elsewhere I wrote down my own personal list of do&#8217;s and don&#8217;ts regarding color and UI elements in general.</span></p>
<ol>
<li><strong><span style="font-family: Arial;">Don&#8217;t use colors that are similar in tone or brightness.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">This one seems pretty straightforward you&#8217;d think. But please.</span></span> <span style="color: #EDE326;"><span style="font-family: Arial;">Yellow</span></span> <span style="font-weight: normal;"><span style="font-family: Arial;">text on a white background? That&#8217;s pretty damn obvious you would think? At work in their awesome wisdom they decided to output the search results in that lovely combination. It&#8217;s the revenge of Colonel Mustard on Mrs. White. Lighthouse.org has a <a title="Color and Useability" href="http://www.lighthouse.org/accessibility/effective-color-contrast/" target="_blank">great article</a> about color.</span></span></strong></li>
<li><strong><span style="font-family: Arial;">Don&#8217;t rely on color for visual cues.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">This one is harder to pin down. I admit the only reason I am so sensitive to it is because I worked with someone who was color blind. I also saw a great example of this the other day when someone printed the page out in black and white and misread the intentions. Folks it is simple, color can be used to help cue but give other ways as well. Be it a symbol, a key, or say text style on top of color.</span></span> </strong></li>
<li><strong><span style="font-family: Arial;">Do use zebra strips for tables of information.<br />
</span><span style="font-size: 13px; font-weight: normal;"><span style="font-family: Arial;">Zebra striping, the use of alternating colors on a table of information is very important. The human eye uses color changes to help sort information. Taking this into account can allow for the display of lots of information in a readable format.</span></span></strong></li>
<li><strong><span style="font-family: Arial;">Do use icons that make sense.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">This is one that many overlook. If you want say a print icon, use a printer not some fancy paper thing. We all love a pretty interface but make it one that can be figured out.</span></span> </strong></li>
<li><strong><span style="font-family: Arial;">Do give people an alternative with icons.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">This really ties into the above do. Things like a mouse over or some text with the icon help people learn the interface quickly. There is nothing more annoying than playing &#8220;guess the icon.&#8221;</span></span> </strong></li>
<li><strong><span style="font-family: Arial;">Do recall Fitt&#8217;s Law<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">To quote the <a title="wiki entry - Fitt's Law" href="http://en.wikipedia.org/wiki/Fitts's_law" target="_blank">wiki entry</a>:</span> <em><span style="font-family: Arial;">&#8220;</span></em></span><span style="font-size: 16px; font-weight: normal;"><span style="font-size: 13px; line-height: 19px;"><strong><em><span style="font-family: Arial;">Fitts&#8217;s law</span></em></strong> <em><span style="font-family: Arial;">(often cited as</span></em> <strong><em><span style="font-family: Arial;">Fitts&#8217; law</span></em></strong><em><span style="font-family: Arial;">) is a model of human movement which predicts the time required to rapidly move to a target area, as a function of the distance to the target and the size of the target.&#8221;</span></em><br />
<span style="font-size: 12px;"><span style="font-family: Arial;">This is often overlooked. Size does matter as does screen real estate. Make things easy to get to and easy to click on. Small can look nice but too small is just a frustration.</span></span> </span></span></strong></li>
<li><strong><span style="font-family: Arial;">Do take into account navigation conventions.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">This is fairly straightforward. While I like innovate use of an interface I also know that I like to know what to expect. Norms develop over time because they work. Don&#8217;t ignore these lightly. While your whizzbang new interface might be awesome to look at if I can&#8217;t figure out how to find where I should save then it has failed me. Things like top and right/left side navigation work because of how we, as humans, organize and interact with things. Don&#8217;t take the human side out of the equation when designing your interface.</span></span></strong></li>
<li><strong><span style="font-family: Arial;">Do minimize the clickyness.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">We all like organization, we all like knowing where to get to a menu option. We don&#8217;t like having to click four times for a common function. Think hard about what you users will do and organize the layout according to that. i should not have to dig for something that you expect me to be doing. I should not need to backtrack either.</span></span></strong></li>
<li><strong><span style="font-family: Arial;">Don&#8217;t crowd the screen.<br />
</span><span style="font-weight: normal;"><span style="font-family: Arial;">Pretty simple this one, but often overlooked. Too much of a good thing is worse than too little. Don&#8217;t go nuts with information.<br />
<img style="margin-right:0px; margin-left:0px; padding-top:5px; padding-right:5px; padding-bottom:5px; padding-left:5px;" src="http://www.blagosphere.org/larry/wp-content/uploads/2008/10/word.jpg" alt="word.jpg" width="376" height="244" /></span></span></strong></li>
<li><span style="font-family: Arial;"><strong>Do make your user feedback clear, concise, and have it make sense.<br />
<span style="font-weight: normal;">The infamous Windows &#8220;Abort, Retry, Fail&#8221; is a great example. Have your feedback use natural language and be concise. When asking someone to do something or not it&#8217;s better to say &#8220;Do this&#8221; versus &#8220;OK&#8221;.<br />
<em>Edit:  As pointed out by Lenna the commonality of &#8220;OK&#8221; and &#8220;Cancel&#8221; on dialog boxes.  People please.  Not everything in this world can be answered by OK/Cancel or Yes/No.  If something fails an &#8220;OK/CANCEL&#8221; dialog is nonsensical.  Is it ok that it failed?  Do I want to cancel the failure?  </em></span></strong></span></li>
</ol>

<!-- start wp-tags-to-technorati 1.01 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/color' rel='tag' target='_blank'>color</a>, <a class='technorati-link' href='http://technorati.com/tag/design' rel='tag' target='_blank'>design</a>, <a class='technorati-link' href='http://technorati.com/tag/internet' rel='tag' target='_blank'>internet</a>, <a class='technorati-link' href='http://technorati.com/tag/list' rel='tag' target='_blank'>list</a>, <a class='technorati-link' href='http://technorati.com/tag/user+interface' rel='tag' target='_blank'>user interface</a></p>

<!-- end wp-tags-to-technorati -->
]]></content:encoded>
			<wfw:commentRss>http://www.blagosphere.org/larry/92-on-color-and-user-interfaces-my-personal-dos-and-donts/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.198 seconds -->
