<?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: Improving Accessibility Through Focus Management</title>
	<atom:link href="http://www.yuiblog.com/blog/index.php/2009/02/23/managing-focus/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/</link>
	<description>The official blog of the YUI Project.</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:46:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Tracy - Property Management</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-594141</link>
		<dc:creator>Tracy - Property Management</dc:creator>
		<pubDate>Fri, 03 Sep 2010 05:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-594141</guid>
		<description>I must admit that I have been quite lax in making sure my sites are accessablet to keyboard only users. I should probably do something about this.</description>
		<content:encoded><![CDATA[<p>I must admit that I have been quite lax in making sure my sites are accessablet to keyboard only users. I should probably do something about this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geek is a Lift-Style. &#187; Developing Sites With AJAX: Design Challenges and Common Issues</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-592297</link>
		<dc:creator>Geek is a Lift-Style. &#187; Developing Sites With AJAX: Design Challenges and Common Issues</dc:creator>
		<pubDate>Fri, 18 Jun 2010 09:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-592297</guid>
		<description>[...] by using JavaScript tricks, you can make any element keyboard accessible. And if you build widgets, go even further by following the rules of keyboard navigation. You could [...]</description>
		<content:encoded><![CDATA[<p>[...] by using JavaScript tricks, you can make any element keyboard accessible. And if you build widgets, go even further by following the rules of keyboard navigation. You could [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Developing Sites With AJAX: Design Challenges and Common Issues &#124; BestWebMagazine</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-588336</link>
		<dc:creator>Developing Sites With AJAX: Design Challenges and Common Issues &#124; BestWebMagazine</dc:creator>
		<pubDate>Thu, 18 Feb 2010 11:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-588336</guid>
		<description>[...] by using JavaScript tricks, you can make any element keyboard accessible. And if you build widgets, go even further by following the rules of keyboard navigation. You could [...]</description>
		<content:encoded><![CDATA[<p>[...] by using JavaScript tricks, you can make any element keyboard accessible. And if you build widgets, go even further by following the rules of keyboard navigation. You could [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Developing Sites With AJAX: Design Challenges and Common Issues &#124; XtremelySocial.com</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-588191</link>
		<dc:creator>Developing Sites With AJAX: Design Challenges and Common Issues &#124; XtremelySocial.com</dc:creator>
		<pubDate>Sat, 13 Feb 2010 20:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-588191</guid>
		<description>[...] by using JavaScript tricks, you can make any element keyboard accessible. And if you build widgets, go even further by following the rules of keyboard navigation. You could [...]</description>
		<content:encoded><![CDATA[<p>[...] by using JavaScript tricks, you can make any element keyboard accessible. And if you build widgets, go even further by following the rules of keyboard navigation. You could [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Some links for light reading (24/2/09) &#171; Max Design</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-587921</link>
		<dc:creator>Some links for light reading (24/2/09) &#171; Max Design</dc:creator>
		<pubDate>Fri, 29 Jan 2010 11:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-587921</guid>
		<description>[...] Improving Accessibility Through Focus Management [...]</description>
		<content:encoded><![CDATA[<p>[...] Improving Accessibility Through Focus Management [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Find The Right JavaScript Solution With A 7-Step Test &#171; Designers&#39; Digest</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-587900</link>
		<dc:creator>Find The Right JavaScript Solution With A 7-Step Test &#171; Designers&#39; Digest</dc:creator>
		<pubDate>Thu, 28 Jan 2010 11:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-587900</guid>
		<description>[...] some great examples of how widgets should react to keyboard use, and Todd Kloots of Yahoo does a great job of explaining the techniques behind good keyboard usability (also as a video and using YUI3 and focusing on WAI-ARIA). Patrick Lauke of Opera also wrote a [...]</description>
		<content:encoded><![CDATA[<p>[...] some great examples of how widgets should react to keyboard use, and Todd Kloots of Yahoo does a great job of explaining the techniques behind good keyboard usability (also as a video and using YUI3 and focusing on WAI-ARIA). Patrick Lauke of Opera also wrote a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor Tsaran</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-583367</link>
		<dc:creator>Victor Tsaran</dc:creator>
		<pubDate>Mon, 10 Aug 2009 17:36:16 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-583367</guid>
		<description>@Todd: actually, the behavior you are describing comes from NVDA, http://www.nvda-project.org, and not JAWS, http://www.freedomscientific.com, screen reader. At least I do not remember seeing JAWS toggle virtual buffer off when an ARIA-enabled widget receives focus. NVDA, however, does so for sure.

@David: the only way to force a screen reader to toggle virtual buffer is to place your widget inside a role of application. This is what we have done inside the &quot;search assist&quot; widget of the Yahoo! Search, http://www.ysearch.com.</description>
		<content:encoded><![CDATA[<p>@Todd: actually, the behavior you are describing comes from NVDA, <a href="http://www.nvda-project.org" rel="nofollow">http://www.nvda-project.org</a>, and not JAWS, <a href="http://www.freedomscientific.com" rel="nofollow">http://www.freedomscientific.com</a>, screen reader. At least I do not remember seeing JAWS toggle virtual buffer off when an ARIA-enabled widget receives focus. NVDA, however, does so for sure.</p>
<p>@David: the only way to force a screen reader to toggle virtual buffer is to place your widget inside a role of application. This is what we have done inside the &#8220;search assist&#8221; widget of the Yahoo! Search, <a href="http://www.ysearch.com" rel="nofollow">http://www.ysearch.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Kloots</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-583364</link>
		<dc:creator>Todd Kloots</dc:creator>
		<pubDate>Mon, 10 Aug 2009 17:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-583364</guid>
		<description>Hi John -

You are correct by default the virtual buffer is enabled in JAWS, meaning that the arrow keys are intercepted by the screen reader.  This is the case for all screen readers.  However, in the more recent versions of ARIA-enabled screen readers, the screen reader will automatically toggle the virtual buffer off by default when focus is given to an element with an ARIA role applied.  And the last time I checked this was the behavior for JAWS 10 as well.  If you are finding that not to be the case, perhaps you have your installation of JAWS configured differently.

- Todd</description>
		<content:encoded><![CDATA[<p>Hi John -</p>
<p>You are correct by default the virtual buffer is enabled in JAWS, meaning that the arrow keys are intercepted by the screen reader.  This is the case for all screen readers.  However, in the more recent versions of ARIA-enabled screen readers, the screen reader will automatically toggle the virtual buffer off by default when focus is given to an element with an ARIA role applied.  And the last time I checked this was the behavior for JAWS 10 as well.  If you are finding that not to be the case, perhaps you have your installation of JAWS configured differently.</p>
<p>- Todd</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Snyders</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-583283</link>
		<dc:creator>John Snyders</dc:creator>
		<pubDate>Fri, 07 Aug 2009 19:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-583283</guid>
		<description>This article was very helpful. I have one point of general confusion. Clearly being keyboard accessible is good for both non mouse users and sight impaired users. The examples often point to having a one tab stop widget and then using arrow keys. However my testing so far with JAWS 10 shows that the browser never receives the arrow keys because JAWS treats them as special reading keys. So now my widget is no longer keyboard accessible. 
Anyone have thoughts on this catch-22?</description>
		<content:encoded><![CDATA[<p>This article was very helpful. I have one point of general confusion. Clearly being keyboard accessible is good for both non mouse users and sight impaired users. The examples often point to having a one tab stop widget and then using arrow keys. However my testing so far with JAWS 10 shows that the browser never receives the arrow keys because JAWS treats them as special reading keys. So now my widget is no longer keyboard accessible.<br />
Anyone have thoughts on this catch-22?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bolter</title>
		<link>http://www.yuiblog.com/blog/2009/02/23/managing-focus/comment-page-1/#comment-582406</link>
		<dc:creator>David Bolter</dc:creator>
		<pubDate>Tue, 07 Jul 2009 15:56:01 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/02/23/managing-focus/#comment-582406</guid>
		<description>Yep, I strongly recommend roaming tabindex too. Nice post.</description>
		<content:encoded><![CDATA[<p>Yep, I strongly recommend roaming tabindex too. Nice post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

