<?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: Setting up a screen reader test environment</title>
	<atom:link href="http://www.iheni.com/screen-reader-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iheni.com/screen-reader-testing/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 10:38:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/screen-reader-testing/comment-page-1/#comment-51886</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Tue, 29 Mar 2011 10:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=855#comment-51886</guid>
		<description>Hi harsit - while not about Jaws 12 itself perhaps this article on&lt;a href=&quot;http://www.iheni.com/flash-and-keyboard-access-across-browsers/&quot; rel=&quot;nofollow&quot;&gt; Flash and keyboard focus across browsers&lt;/a&gt; will be useful. 

In general (aside from just Flash support) Jaws is for Windows wont work with Safari. Chrome has pretty poor support for screen readers and &lt;a href=&quot;http://www.iheni.com/using-opera-10-beta-with-voiceover/&quot; rel=&quot;nofollow&quot;&gt;Opera only supports VoiceOver on Mac&lt;/a&gt;. 

Marco Zehe from Mozilla has the latest on &lt;a href=&quot;http://www.marcozehe.de/2010/10/04/new-in-accessibility-in-firefox-4-0/&quot; rel=&quot;nofollow&quot;&gt;accessibility support for Firefox 4&lt;/a&gt; and will be able to answer questions about Jaws 12.</description>
		<content:encoded><![CDATA[<p>Hi harsit &#8211; while not about Jaws 12 itself perhaps this article on<a href="http://www.iheni.com/flash-and-keyboard-access-across-browsers/" rel="nofollow"> Flash and keyboard focus across browsers</a> will be useful. </p>
<p>In general (aside from just Flash support) Jaws is for Windows wont work with Safari. Chrome has pretty poor support for screen readers and <a href="http://www.iheni.com/using-opera-10-beta-with-voiceover/" rel="nofollow">Opera only supports VoiceOver on Mac</a>. </p>
<p>Marco Zehe from Mozilla has the latest on <a href="http://www.marcozehe.de/2010/10/04/new-in-accessibility-in-firefox-4-0/" rel="nofollow">accessibility support for Firefox 4</a> and will be able to answer questions about Jaws 12.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: harshit</title>
		<link>http://www.iheni.com/screen-reader-testing/comment-page-1/#comment-51793</link>
		<dc:creator>harshit</dc:creator>
		<pubDate>Mon, 28 Mar 2011 10:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=855#comment-51793</guid>
		<description>hi,
Is Flash accessible to JAWS-12 in below browsers?
ie.  IE (All version) 
      Firefox (Versions 3.0 onwards)
      Chrome
      Safari
      Opera</description>
		<content:encoded><![CDATA[<p>hi,<br />
Is Flash accessible to JAWS-12 in below browsers?<br />
ie.  IE (All version)<br />
      Firefox (Versions 3.0 onwards)<br />
      Chrome<br />
      Safari<br />
      Opera</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gildas</title>
		<link>http://www.iheni.com/screen-reader-testing/comment-page-1/#comment-47799</link>
		<dc:creator>Gildas</dc:creator>
		<pubDate>Fri, 18 Feb 2011 18:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=855#comment-47799</guid>
		<description>I want to also note that testing with a screen reader is an _interoperability_test_ and is fine to determine if the specific assistive technology (AT) you are using works for people with disabilities, but since it is assistive technology, sometimes it &#039;cheats&#039; and provides more accessibility to the end user than is properly coded into the application or content under review. Testing with AT should not be the primary mode of inspecting for accessibility! Inspecting the platform APIs, e.g., via Inspect32 on Windows, or JavaFerret for Java applications and the document markup via Web Accessibility Toolbar and other API/Document object model inspection-based approaches should be used. Not only does this eliminate confusion in determining if the technologies under inspection are coded properly, it allows clarification if AT has defects or simply doesn&#039;t yet support the standard APIs or interfaces available, so that can be taken back to the AT vendor for a fix or feature request. It also really helps developers who may not know AT, but who can determine if it is coded properly.</description>
		<content:encoded><![CDATA[<p>I want to also note that testing with a screen reader is an _interoperability_test_ and is fine to determine if the specific assistive technology (AT) you are using works for people with disabilities, but since it is assistive technology, sometimes it &#8216;cheats&#8217; and provides more accessibility to the end user than is properly coded into the application or content under review. Testing with AT should not be the primary mode of inspecting for accessibility! Inspecting the platform APIs, e.g., via Inspect32 on Windows, or JavaFerret for Java applications and the document markup via Web Accessibility Toolbar and other API/Document object model inspection-based approaches should be used. Not only does this eliminate confusion in determining if the technologies under inspection are coded properly, it allows clarification if AT has defects or simply doesn&#8217;t yet support the standard APIs or interfaces available, so that can be taken back to the AT vendor for a fix or feature request. It also really helps developers who may not know AT, but who can determine if it is coded properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Mills</title>
		<link>http://www.iheni.com/screen-reader-testing/comment-page-1/#comment-42798</link>
		<dc:creator>Rob Mills</dc:creator>
		<pubDate>Sun, 09 Jan 2011 20:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=855#comment-42798</guid>
		<description>Some great instructions.  Thank you.

I wasn&#039;t aware you could demo Jaws for 40 mins before a reboot.</description>
		<content:encoded><![CDATA[<p>Some great instructions.  Thank you.</p>
<p>I wasn&#8217;t aware you could demo Jaws for 40 mins before a reboot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.iheni.com/screen-reader-testing/comment-page-1/#comment-42116</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Tue, 04 Jan 2011 07:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=855#comment-42116</guid>
		<description>Thank you for an interesting post. However, I would like to point out that the license for the free JAWS &quot;40 minute version&quot; is for product evaluation purposes only. The license explicitly states that development and testing is not permitted. You will have to buy a full license if you want use JAWS to test and develop.</description>
		<content:encoded><![CDATA[<p>Thank you for an interesting post. However, I would like to point out that the license for the free JAWS &#8220;40 minute version&#8221; is for product evaluation purposes only. The license explicitly states that development and testing is not permitted. You will have to buy a full license if you want use JAWS to test and develop.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

