<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Accessibility on our site</title>
	<link>http://www.coactivate.org/projects/opencore/blog/2008/03/24/accessibility-on-our-site/</link>
	<description>Just another  weblog</description>
	<pubDate>Sun, 21 Mar 2010 15:29:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.5</generator>

	<item>
		<title>By: ianb</title>
		<link>http://www.coactivate.org/projects/opencore/blog/2008/03/24/accessibility-on-our-site/#comment-92</link>
		<dc:creator>ianb</dc:creator>
		<pubDate>Mon, 24 Mar 2008 16:58:16 +0000</pubDate>
		<guid>http://www.coactivate.org/projects/opencore/blog/2008/03/24/accessibility-on-our-site/#comment-92</guid>
		<description>Well, I thought I'd try leaving a comment on this page using NVDA with the screen turned off.  Total disaster.  But not our fault.  The screen reader is just totally messed up.  It kept swallowing my keys, but speaking the keys -- if I couldn't read the page I could never have detected this bug.  It reads crazy things, like reading out the edit href instead of just "Edit".  It was messing everything up.  I tried it in IE, thinking maybe it would work better, but it totally messes up the keyboard focus, so you have to tab through a half dozen stupid IE controls to get to the links on the page.

I might try another one of the screen readers that is noted, but at this point NVDA is so unusable (at least on the machine I tried it on) that I can't even get to any of the problems with our site in particular.  And it's working badly enough that it feels like we'd just be doing workarounds specific to this one product.  Are they all messed up in the same way?</description>
		<content:encoded><![CDATA[<p>Well, I thought I&#8217;d try leaving a comment on this page using NVDA with the screen turned off.  Total disaster.  But not our fault.  The screen reader is just totally messed up.  It kept swallowing my keys, but speaking the keys &#8212; if I couldn&#8217;t read the page I could never have detected this bug.  It reads crazy things, like reading out the edit href instead of just &#8220;Edit&#8221;.  It was messing everything up.  I tried it in IE, thinking maybe it would work better, but it totally messes up the keyboard focus, so you have to tab through a half dozen stupid IE controls to get to the links on the page.</p>
<p>I might try another one of the screen readers that is noted, but at this point NVDA is so unusable (at least on the machine I tried it on) that I can&#8217;t even get to any of the problems with our site in particular.  And it&#8217;s working badly enough that it feels like we&#8217;d just be doing workarounds specific to this one product.  Are they all messed up in the same way?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
