<?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: iTunes 7.1: Finally supports Full Keyboard Access</title>
	<atom:link href="http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/</link>
	<description>Notes from an unfinished world…</description>
	<lastBuildDate>Mon, 06 Feb 2012 13:29:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/comment-page-1/#comment-6866</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Sat, 24 Mar 2007 20:28:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/#comment-6866</guid>
		<description>Interesting. It looks like it might be intentional, because if you continue to tab back, it does take you back to the Info tab, but only after taking you back through the other bottom buttons. So maybe the idea is that the tab between the &quot;Info&quot; tab and the &quot;Cancel&quot; button is actually a tab between the tab bar and the bottom row of buttons, rather than to a specific button in that row. The default one is Cancel, but once you are there, it takes you through the other buttons before going back up to the tab bar. So it looks like there is some kind of hierarchy in the tab order.

Anyway, you might want to submit this as a bug report and see what they say about it.</description>
		<content:encoded><![CDATA[<p>Interesting. It looks like it might be intentional, because if you continue to tab back, it does take you back to the Info tab, but only after taking you back through the other bottom buttons. So maybe the idea is that the tab between the &#8220;Info&#8221; tab and the &#8220;Cancel&#8221; button is actually a tab between the tab bar and the bottom row of buttons, rather than to a specific button in that row. The default one is Cancel, but once you are there, it takes you through the other buttons before going back up to the tab bar. So it looks like there is some kind of hierarchy in the tab order.</p>
<p>Anyway, you might want to submit this as a bug report and see what they say about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Pollock</title>
		<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/comment-page-1/#comment-6865</link>
		<dc:creator>Richard Pollock</dc:creator>
		<pubDate>Sat, 24 Mar 2007 12:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/#comment-6865</guid>
		<description>They still haven&#039;t got it quite right, though. Try tabbing, for example, to the Cancel button on the Info tab. Now press tab twice to tab through the tab bar and get to the &quot;Name&quot; text field. And now shift-tab to go back to the tab bar at the top... Oh no, that takes you back to the Cancel button. Ah well, to be fair, it is only a very minor complaint – 9/10 overall for FKA.</description>
		<content:encoded><![CDATA[<p>They still haven&#8217;t got it quite right, though. Try tabbing, for example, to the Cancel button on the Info tab. Now press tab twice to tab through the tab bar and get to the &#8220;Name&#8221; text field. And now shift-tab to go back to the tab bar at the top&#8230; Oh no, that takes you back to the Cancel button. Ah well, to be fair, it is only a very minor complaint – 9/10 overall for FKA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/comment-page-1/#comment-6814</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Fri, 16 Mar 2007 12:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/#comment-6814</guid>
		<description>Martin: Very useful tip. Thanks a lot!</description>
		<content:encoded><![CDATA[<p>Martin: Very useful tip. Thanks a lot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/comment-page-1/#comment-6813</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Fri, 16 Mar 2007 00:03:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/#comment-6813</guid>
		<description>You can use option-Tab to tab through just the text fields, skipping the check boxes.</description>
		<content:encoded><![CDATA[<p>You can use option-Tab to tab through just the text fields, skipping the check boxes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/comment-page-1/#comment-6812</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Thu, 15 Mar 2007 19:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/#comment-6812</guid>
		<description>Actually, most of the applications that I use now provide FKA support. Microsoft and Adobe applications are the big exceptions, of course, but most of the Apple applications that I use work fine with FKA. iTunes was &lt;em&gt;the&lt;/em&gt; big sore point. (There is still the Finder, of course, but thankfully there are few dialog boxes in that particular application. You still can browse the Finder&#039;s preference panes with the keyboard, though.)</description>
		<content:encoded><![CDATA[<p>Actually, most of the applications that I use now provide FKA support. Microsoft and Adobe applications are the big exceptions, of course, but most of the Apple applications that I use work fine with FKA. iTunes was <em>the</em> big sore point. (There is still the Finder, of course, but thankfully there are few dialog boxes in that particular application. You still can browse the Finder&#8217;s preference panes with the keyboard, though.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Ingraham</title>
		<link>http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/comment-page-1/#comment-6810</link>
		<dc:creator>Paul Ingraham</dc:creator>
		<pubDate>Thu, 15 Mar 2007 18:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/03/15/itunes-71-finally-supports-full-keyboard-access/#comment-6810</guid>
		<description>That&#039;s some good news in the &quot;About #@!!&amp; Time&quot; category.  I imagine a few other significant Apple apps are still awaiting the same functionality.  But I sure wouldn&#039;t know, because I gave up trying to use the keyboard for everything long ago: it&#039;s just not worth it, support is so spotty. Thanks for the report, though, it&#039;s good to know that it&#039;s slowly changing.</description>
		<content:encoded><![CDATA[<p>That&#8217;s some good news in the &#8220;About #@!!&amp; Time&#8221; category.  I imagine a few other significant Apple apps are still awaiting the same functionality.  But I sure wouldn&#8217;t know, because I gave up trying to use the keyboard for everything long ago: it&#8217;s just not worth it, support is so spotty. Thanks for the report, though, it&#8217;s good to know that it&#8217;s slowly changing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

