<?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: Tab Order Diagram</title>
	<atom:link href="http://wireframes.linowski.ca/2009/03/tab-order-diagram/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/</link>
	<description>Because every IA has something funky up their sleeve</description>
	<lastBuildDate>Mon, 06 Feb 2012 15:18:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Erik Hagborg</title>
		<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/comment-page-1/#comment-630</link>
		<dc:creator>Erik Hagborg</dc:creator>
		<pubDate>Sun, 29 Mar 2009 21:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=600#comment-630</guid>
		<description>Its definitely a good idea and I think that having the client see it (but in context) is not a bad idea.  However, I agree that with complex forms a single arrow, whether curved or zigzagging will simply become unmanageable.  I am going to start doing this when appropriate but I think I will use some numbered transparent icons. That way they are less intusive and can be adapted for each form regardless of its complexity. </description>
		<content:encoded><![CDATA[<p>Its definitely a good idea and I think that having the client see it (but in context) is not a bad idea.  However, I agree that with complex forms a single arrow, whether curved or zigzagging will simply become unmanageable.  I am going to start doing this when appropriate but I think I will use some numbered transparent icons. That way they are less intusive and can be adapted for each form regardless of its complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Schechterman</title>
		<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/comment-page-1/#comment-586</link>
		<dc:creator>Andrew Schechterman</dc:creator>
		<pubDate>Mon, 23 Mar 2009 18:08:12 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=600#comment-586</guid>
		<description>This is particularly important per users with access limitations (visual, auditory, tactile limitations) which our teams saw a lot of in, for example, self-service medical applications.  We used lightweight arrows, but if too numerous, we numbered them and them placed them on separate pages. We kept our teams very small, as such, our development colleague(s) very quickly helped us determine what would be easiest for them.  - Andrew Schechterman, PhD </description>
		<content:encoded><![CDATA[<p>This is particularly important per users with access limitations (visual, auditory, tactile limitations) which our teams saw a lot of in, for example, self-service medical applications.  We used lightweight arrows, but if too numerous, we numbered them and them placed them on separate pages. We kept our teams very small, as such, our development colleague(s) very quickly helped us determine what would be easiest for them.  &#8211; Andrew Schechterman, PhD</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Linowski</title>
		<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/comment-page-1/#comment-585</link>
		<dc:creator>Jakub Linowski</dc:creator>
		<pubDate>Mon, 23 Mar 2009 15:02:43 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=600#comment-585</guid>
		<description>Zigzagging arrows could work, or even less distracting would be flowing curved lines. Perhaps this is also a type of information which could be somehow layered separately and only shown to a certain viewers such as developers (and not clients or users). </description>
		<content:encoded><![CDATA[<p>Zigzagging arrows could work, or even less distracting would be flowing curved lines. Perhaps this is also a type of information which could be somehow layered separately and only shown to a certain viewers such as developers (and not clients or users).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bnunnally</title>
		<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/comment-page-1/#comment-584</link>
		<dc:creator>bnunnally</dc:creator>
		<pubDate>Mon, 23 Mar 2009 14:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=600#comment-584</guid>
		<description>I think the overall concept still hold Adam. Rather than having a straight arrow going down the page, using a non-invasive visual que to communicate the order would still work. In my head I see zig-zags of arrows, but if done correct they don&#039;t have to distract from the rest of the mock up. </description>
		<content:encoded><![CDATA[<p>I think the overall concept still hold Adam. Rather than having a straight arrow going down the page, using a non-invasive visual que to communicate the order would still work. In my head I see zig-zags of arrows, but if done correct they don&#039;t have to distract from the rest of the mock up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/comment-page-1/#comment-583</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 23 Mar 2009 13:14:30 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=600#comment-583</guid>
		<description>what if the order were more complex (if you had more controls and some to the right?) 
 
What if, for example, on a login page you wanted the &quot;remember password&quot; checkbox to be tabbed before the login button that visually came first? </description>
		<content:encoded><![CDATA[<p>what if the order were more complex (if you had more controls and some to the right?) </p>
<p>What if, for example, on a login page you wanted the &quot;remember password&quot; checkbox to be tabbed before the login button that visually came first?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walter Aprile</title>
		<link>http://wireframes.linowski.ca/2009/03/tab-order-diagram/comment-page-1/#comment-582</link>
		<dc:creator>Walter Aprile</dc:creator>
		<pubDate>Mon, 23 Mar 2009 12:50:27 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=600#comment-582</guid>
		<description>Mmm... if the tab order is not as straightforward as this one that arrow could end up zigzagging all over the place, and being a bit painful to behold. But perhaps if it is zigzagging, it means that your tab order is messed up!</description>
		<content:encoded><![CDATA[<p>Mmm&#8230; if the tab order is not as straightforward as this one that arrow could end up zigzagging all over the place, and being a bit painful to behold. But perhaps if it is zigzagging, it means that your tab order is messed up!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

