<?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 for Coolfields Consulting</title>
	<atom:link href="http://www.coolfields.co.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coolfields.co.uk</link>
	<description>effective accessible websites</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:49:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>Comment on WordPress Keyboard Accessible Dropdown Menus Plugin Version 0.1 by Ton van Leest</title>
		<link>http://www.coolfields.co.uk/2011/12/wordpress-keyboard-accessible-dropdown-menus-plugin-version-0-1/comment-page-1/#comment-3120</link>
		<dc:creator>Ton van Leest</dc:creator>
		<pubDate>Wed, 08 Feb 2012 16:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1470#comment-3120</guid>
		<description>Beste Graham Armfield,

Thank you for sharing this plugin. I have a website (http://www.ict4vip.nl) for people with visual impairments who use screenreading software. By using your plugin, I can now use the default WordPress theme and sub menus.

It would be nice as this technology is included by default in WordPress.

Sincerely,
Ton van Leest</description>
		<content:encoded><![CDATA[<p>Beste Graham Armfield,</p>
<p>Thank you for sharing this plugin. I have a website (<a href="http://www.ict4vip.nl" rel="nofollow">http://www.ict4vip.nl</a>) for people with visual impairments who use screenreading software. By using your plugin, I can now use the default WordPress theme and sub menus.</p>
<p>It would be nice as this technology is included by default in WordPress.</p>
<p>Sincerely,<br />
Ton van Leest</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Specification for an Accessible Lightbox by Sophie Schuermans</title>
		<link>http://www.coolfields.co.uk/2011/12/specification-for-an-accessible-lightbox/comment-page-1/#comment-3073</link>
		<dc:creator>Sophie Schuermans</dc:creator>
		<pubDate>Mon, 06 Feb 2012 20:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1529#comment-3073</guid>
		<description>Thanks for this very usefull summary. 
Another thing I also noticed in a lot of lightboxes is that the links used to navigate between pictures don&#039;t have meaningfull linktexts. This is usually due tu a picture missing alt text or an empty link with background image serving as a button.</description>
		<content:encoded><![CDATA[<p>Thanks for this very usefull summary.<br />
Another thing I also noticed in a lot of lightboxes is that the links used to navigate between pictures don&#8217;t have meaningfull linktexts. This is usually due tu a picture missing alt text or an empty link with background image serving as a button.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Specification for an Accessible Lightbox by Vincent Young</title>
		<link>http://www.coolfields.co.uk/2011/12/specification-for-an-accessible-lightbox/comment-page-1/#comment-2613</link>
		<dc:creator>Vincent Young</dc:creator>
		<pubDate>Fri, 06 Jan 2012 16:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1529#comment-2613</guid>
		<description>Excellent article and topic.  I really like the idea of closing the lightbox if an &quot;outside&quot; element is focused. A few extra mentions below:  

Instead of closing the lightbox when an &quot;outside&quot; link is focused, what about automatically focusing the last or first focusable item (or lightbox container)?  

I feel that because the user did not directly close the lightbox, it should not be closed for them.  A possible solution is to add an empty focusable item at the top and bottom of the BODY and when they are focused, throw focus to lightbox.  This of course solves the problem if a user goes to the browser chrome and then tries to TAB back into the page.  This does not solve the problem if a user focuses a link within the page which can be done with screen readers by pulling up a list of controls and then instructing the screen reader to move to any of them.  You could add listeners to each of these &quot;outside&quot; conrtrols and once again throw focus to the lightbox, but this could be a bit too involved for some pages.  

Another problem I find with lighboxes and this pertains to mostly screen reader users, is that it can be unclear when the lightbox starts and stops when arrowning throw the lighbox content.  A possible solutions is to add off-screen text to the start and end of the lightbox that would read somthing like:

Dialog Start

(content)

Dialog End

or whatever you feel appropriate.  


Thoughts on user experience?</description>
		<content:encoded><![CDATA[<p>Excellent article and topic.  I really like the idea of closing the lightbox if an &#8220;outside&#8221; element is focused. A few extra mentions below:  </p>
<p>Instead of closing the lightbox when an &#8220;outside&#8221; link is focused, what about automatically focusing the last or first focusable item (or lightbox container)?  </p>
<p>I feel that because the user did not directly close the lightbox, it should not be closed for them.  A possible solution is to add an empty focusable item at the top and bottom of the BODY and when they are focused, throw focus to lightbox.  This of course solves the problem if a user goes to the browser chrome and then tries to TAB back into the page.  This does not solve the problem if a user focuses a link within the page which can be done with screen readers by pulling up a list of controls and then instructing the screen reader to move to any of them.  You could add listeners to each of these &#8220;outside&#8221; conrtrols and once again throw focus to the lightbox, but this could be a bit too involved for some pages.  </p>
<p>Another problem I find with lighboxes and this pertains to mostly screen reader users, is that it can be unclear when the lightbox starts and stops when arrowning throw the lighbox content.  A possible solutions is to add off-screen text to the start and end of the lightbox that would read somthing like:</p>
<p>Dialog Start</p>
<p>(content)</p>
<p>Dialog End</p>
<p>or whatever you feel appropriate.  </p>
<p>Thoughts on user experience?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Specification for an Accessible Lightbox by Graham Armfield</title>
		<link>http://www.coolfields.co.uk/2011/12/specification-for-an-accessible-lightbox/comment-page-1/#comment-2569</link>
		<dc:creator>Graham Armfield</dc:creator>
		<pubDate>Tue, 03 Jan 2012 10:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1529#comment-2569</guid>
		<description>Thanks James for your useful additions. The inevitable onward march of touch devices - eg smartphones and iPads - brings new challenges to design. It is no longer safe just to assume your users are sitting at a desk.</description>
		<content:encoded><![CDATA[<p>Thanks James for your useful additions. The inevitable onward march of touch devices &#8211; eg smartphones and iPads &#8211; brings new challenges to design. It is no longer safe just to assume your users are sitting at a desk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Specification for an Accessible Lightbox by James Royal-Lawson</title>
		<link>http://www.coolfields.co.uk/2011/12/specification-for-an-accessible-lightbox/comment-page-1/#comment-2555</link>
		<dc:creator>James Royal-Lawson</dc:creator>
		<pubDate>Mon, 02 Jan 2012 12:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1529#comment-2555</guid>
		<description>Two points i&#039;d like to add to the mix: touch devices, and responsive web design.

Touch devices more often than not don&#039;t have a keyboard or a mouse. Title attributes aren&#039;t visible either.

Add to that the smaller viewport size - numerous lightboxes i&#039;ve seen are bigger than the width (or hight) of common handheld viewports.

Responsive web design further complicates the situation - any lightbox would need to retain its accessability throughout the various design breakpoints.</description>
		<content:encoded><![CDATA[<p>Two points i&#8217;d like to add to the mix: touch devices, and responsive web design.</p>
<p>Touch devices more often than not don&#8217;t have a keyboard or a mouse. Title attributes aren&#8217;t visible either.</p>
<p>Add to that the smaller viewport size &#8211; numerous lightboxes i&#8217;ve seen are bigger than the width (or hight) of common handheld viewports.</p>
<p>Responsive web design further complicates the situation &#8211; any lightbox would need to retain its accessability throughout the various design breakpoints.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress Keyboard Accessible Dropdown Menus Plugin Version 0.1 by charlies</title>
		<link>http://www.coolfields.co.uk/2011/12/wordpress-keyboard-accessible-dropdown-menus-plugin-version-0-1/comment-page-1/#comment-2038</link>
		<dc:creator>charlies</dc:creator>
		<pubDate>Fri, 02 Dec 2011 15:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1470#comment-2038</guid>
		<description>Keyboard Accessible Dropdown Menus Plugin is a very useful plugin ,I like it ,thank you for sharing</description>
		<content:encoded><![CDATA[<p>Keyboard Accessible Dropdown Menus Plugin is a very useful plugin ,I like it ,thank you for sharing</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible Forms &#8211; Grouping Elements Together With Fieldset by Toon</title>
		<link>http://www.coolfields.co.uk/2011/10/accessible-forms-grouping-elements-together-with-fieldset/comment-page-1/#comment-1931</link>
		<dc:creator>Toon</dc:creator>
		<pubDate>Sat, 26 Nov 2011 21:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=1393#comment-1931</guid>
		<description>A benefit of properly associated label tags is also that they&#039;re clickable shortcuts for the form fields. Especially in the case of radiobuttons and checkboxes that can really come in handy, not just for screenreaders.</description>
		<content:encoded><![CDATA[<p>A benefit of properly associated label tags is also that they&#8217;re clickable shortcuts for the form fields. Especially in the case of radiobuttons and checkboxes that can really come in handy, not just for screenreaders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Text for Screen Readers Only by Graham Armfield</title>
		<link>http://www.coolfields.co.uk/2009/12/text-for-screen-readers-only/comment-page-1/#comment-1562</link>
		<dc:creator>Graham Armfield</dc:creator>
		<pubDate>Fri, 26 Aug 2011 09:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/blog/?p=75#comment-1562</guid>
		<description>You&#039;re welcome.</description>
		<content:encoded><![CDATA[<p>You&#8217;re welcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Text for Screen Readers Only by Wyrdbeard</title>
		<link>http://www.coolfields.co.uk/2009/12/text-for-screen-readers-only/comment-page-1/#comment-1560</link>
		<dc:creator>Wyrdbeard</dc:creator>
		<pubDate>Thu, 25 Aug 2011 12:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/blog/?p=75#comment-1560</guid>
		<description>Very useful - many thanks!</description>
		<content:encoded><![CDATA[<p>Very useful &#8211; many thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible Forms – Should Every Input Have a Label? by lavanya</title>
		<link>http://www.coolfields.co.uk/2011/04/accessible-forms-should-every-input-have-a-label/comment-page-1/#comment-1554</link>
		<dc:creator>lavanya</dc:creator>
		<pubDate>Tue, 23 Aug 2011 05:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.coolfields.co.uk/?p=944#comment-1554</guid>
		<description>I hav HTML embeded in JSP files. When i add a legend to radio button question. Its reading the question twice.</description>
		<content:encoded><![CDATA[<p>I hav HTML embeded in JSP files. When i add a legend to radio button question. Its reading the question twice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

