<?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: Building a Better Lightbox</title>
	<atom:link href="http://www.habdas.org/2009/03/29/building-a-better-lightbox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.habdas.org/2009/03/29/building-a-better-lightbox/</link>
	<description>The technical blog of Josh Habdas</description>
	<lastBuildDate>Sun, 05 Sep 2010 20:28:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Josh</title>
		<link>http://www.habdas.org/2009/03/29/building-a-better-lightbox/comment-page-1/#comment-2464</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Wed, 11 Aug 2010 01:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.habdas.org/?p=375#comment-2464</guid>
		<description>Thanks for your comment. Both the current ColorBox and Lightview implementations allow for use of the arrow keys to navigate through slides, when available, but do not always meet some of the other guidance I mentioned. For example, ColorBox does not prevent the user from tabbing to content behind the modal dialog and Lightview does not seem to allow the user to tab to content within.

I checked on what might be a more accessible option, the &lt;a href=&quot;http://jqueryui.com/demos/dialog/#modal-form&quot; rel=&quot;nofollow&quot;&gt;modal dialog in jQuery UI&lt;/a&gt;. That one allows users to tab into content within the modal dialog but then traps the tab, rendering it useless for further navigation instead of moving focus back up to the location bar. The jQuery UI implementation also begins using the ARIA role attribute on the dialog container, which should add some value from an accessibility standpoint.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment. Both the current ColorBox and Lightview implementations allow for use of the arrow keys to navigate through slides, when available, but do not always meet some of the other guidance I mentioned. For example, ColorBox does not prevent the user from tabbing to content behind the modal dialog and Lightview does not seem to allow the user to tab to content within.</p>
<p>I checked on what might be a more accessible option, the <a href="http://jqueryui.com/demos/dialog/#modal-form" rel="nofollow">modal dialog in jQuery UI</a>. That one allows users to tab into content within the modal dialog but then traps the tab, rendering it useless for further navigation instead of moving focus back up to the location bar. The jQuery UI implementation also begins using the ARIA role attribute on the dialog container, which should add some value from an accessibility standpoint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Detlev Fischer</title>
		<link>http://www.habdas.org/2009/03/29/building-a-better-lightbox/comment-page-1/#comment-2451</link>
		<dc:creator>Detlev Fischer</dc:creator>
		<pubDate>Tue, 10 Aug 2010 14:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.habdas.org/?p=375#comment-2451</guid>
		<description>Hi Josh Habdas,

thanks for the informative article. While you cover the keyboard accessibility issues, I noticed that both your recommended lightbox scripts at the end of the article have demos that are not keyboard accessible except for responding to the escape key (a shortcut that in order to meet WCAG 2.0 success criterion 2.1.1 &quot;Keyboard&quot; would at least need to be clearly documented). 

Links / controls in both lightbox implementations recommended don&#039;t show any keyboard focus and don&#039;t seem to respond to keyboard input either. Maybe this can be customised, but I guess there will be more accessible default implementations around?

Regards,
Detlev</description>
		<content:encoded><![CDATA[<p>Hi Josh Habdas,</p>
<p>thanks for the informative article. While you cover the keyboard accessibility issues, I noticed that both your recommended lightbox scripts at the end of the article have demos that are not keyboard accessible except for responding to the escape key (a shortcut that in order to meet WCAG 2.0 success criterion 2.1.1 &#8220;Keyboard&#8221; would at least need to be clearly documented). </p>
<p>Links / controls in both lightbox implementations recommended don&#8217;t show any keyboard focus and don&#8217;t seem to respond to keyboard input either. Maybe this can be customised, but I guess there will be more accessible default implementations around?</p>
<p>Regards,<br />
Detlev</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colorblind, Law, and Lightboxes &#171; AccessTech News</title>
		<link>http://www.habdas.org/2009/03/29/building-a-better-lightbox/comment-page-1/#comment-893</link>
		<dc:creator>Colorblind, Law, and Lightboxes &#171; AccessTech News</dc:creator>
		<pubDate>Thu, 29 Oct 2009 15:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.habdas.org/?p=375#comment-893</guid>
		<description>[...] Building a Better Lightbox by Josh Habdas. [...]</description>
		<content:encoded><![CDATA[<p>[...] Building a Better Lightbox by Josh Habdas. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
