<?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: How To Use Status to Style a List</title>
	<atom:link href="http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/</link>
	<description>Usable Web Applications with Web Standards</description>
	<lastBuildDate>Thu, 18 Feb 2010 14:38:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dean Genco</title>
		<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/comment-page-1/#comment-542</link>
		<dc:creator>Dean Genco</dc:creator>
		<pubDate>Thu, 11 Sep 2008 06:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=122#comment-542</guid>
		<description>Nice article. Thanks for the useful information.</description>
		<content:encoded><![CDATA[<p>Nice article. Thanks for the useful information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey Haines</title>
		<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/comment-page-1/#comment-529</link>
		<dc:creator>Corey Haines</dc:creator>
		<pubDate>Tue, 22 Jul 2008 00:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=122#comment-529</guid>
		<description>Great write-up, Josh. Like Dana, I really like the explanation of why red is bad in this case. I love the idea of de-emphasizing information that the user won&#039;t necessarily have a reason to make use of.</description>
		<content:encoded><![CDATA[<p>Great write-up, Josh. Like Dana, I really like the explanation of why red is bad in this case. I love the idea of de-emphasizing information that the user won&#8217;t necessarily have a reason to make use of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geof Harries</title>
		<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/comment-page-1/#comment-528</link>
		<dc:creator>Geof Harries</dc:creator>
		<pubDate>Mon, 21 Jul 2008 22:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=122#comment-528</guid>
		<description>Nate brings up a good point regarding accessibility, but I&#039;d still be hesitant to include icons, such as the alert graphic, in a data table. If you end up displaying hundreds of rows, the icons will dominate the viewable area. Personally, I&#039;d experiment with subtle colour changes instead, assuming colorblindness tests will be run on the interface.</description>
		<content:encoded><![CDATA[<p>Nate brings up a good point regarding accessibility, but I&#8217;d still be hesitant to include icons, such as the alert graphic, in a data table. If you end up displaying hundreds of rows, the icons will dominate the viewable area. Personally, I&#8217;d experiment with subtle colour changes instead, assuming colorblindness tests will be run on the interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dana Kashubeck</title>
		<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/comment-page-1/#comment-527</link>
		<dc:creator>Dana Kashubeck</dc:creator>
		<pubDate>Mon, 21 Jul 2008 20:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=122#comment-527</guid>
		<description>Great article.  Being a developer and not a designer, I thought at first the red was fine.

I appreciate the way you&#039;ve explained why red isn&#039;t right here and where red &lt;em&gt;would&lt;/em&gt; be right.

I also like Nate&#039;s point about using more than color for cues.  This is something I&#039;m really striving to keep in mind as I work on new features for my company&#039;s site:  not everyone can see the site as well as I can.</description>
		<content:encoded><![CDATA[<p>Great article.  Being a developer and not a designer, I thought at first the red was fine.</p>
<p>I appreciate the way you&#8217;ve explained why red isn&#8217;t right here and where red <em>would</em> be right.</p>
<p>I also like Nate&#8217;s point about using more than color for cues.  This is something I&#8217;m really striving to keep in mind as I work on new features for my company&#8217;s site:  not everyone can see the site as well as I can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Klaiber</title>
		<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/comment-page-1/#comment-526</link>
		<dc:creator>Nate Klaiber</dc:creator>
		<pubDate>Mon, 21 Jul 2008 20:28:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=122#comment-526</guid>
		<description>I couldn&#039;t agree more. Too many times lists are mindlessly populated. I think sometimes there is a disconnect when a designer feels like they don&#039;t have control of the data in the list. They begin to think in binary, and are unaware of how hooks can be created to allow for styling based on different statuses. I have the same pet peeve with Red, too many people use it as a wrong indicator.

Something else that needs to be taken into play, is dealing with a user who has some sort of potential colorblindness. Simply changing color or tone may not always be immediately evident to them, they may require the use of an icon as well. 

I think it&#039;s an overall thought process. Understand how users interact with the list of data, and letting them quickly see/filter things at a glance. I love the way you have visually broken things down.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more. Too many times lists are mindlessly populated. I think sometimes there is a disconnect when a designer feels like they don&#8217;t have control of the data in the list. They begin to think in binary, and are unaware of how hooks can be created to allow for styling based on different statuses. I have the same pet peeve with Red, too many people use it as a wrong indicator.</p>
<p>Something else that needs to be taken into play, is dealing with a user who has some sort of potential colorblindness. Simply changing color or tone may not always be immediately evident to them, they may require the use of an icon as well. </p>
<p>I think it&#8217;s an overall thought process. Understand how users interact with the list of data, and letting them quickly see/filter things at a glance. I love the way you have visually broken things down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Fiorini</title>
		<link>http://www.designinginteractive.com/user-experience/how-to-use-status-to-style-a-list/comment-page-1/#comment-525</link>
		<dc:creator>Joe Fiorini</dc:creator>
		<pubDate>Mon, 21 Jul 2008 20:19:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=122#comment-525</guid>
		<description>Hah, I just dealt with that this weekend.  We created a list of hotels and had to style them based on vacancy status.  Of course, we made the hotels that were full red, which, you&#039;re right, probably should be grayed out instead.  Thanks for the insight!  Great post!</description>
		<content:encoded><![CDATA[<p>Hah, I just dealt with that this weekend.  We created a list of hotels and had to style them based on vacancy status.  Of course, we made the hotels that were full red, which, you&#8217;re right, probably should be grayed out instead.  Thanks for the insight!  Great post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
