<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Quiz 4.1.4: JavaScript - Part 1: Navigating links</title>
	<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Wed, 08 Sep 2010 13:47:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: vikas</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-108582</link>
		<pubDate>Sat, 23 Feb 2008 03:28:07 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-108582</guid>
					<description>Would u tell me how to test javascript working (test cases) as a software tester</description>
		<content:encoded><![CDATA[<p>Would u tell me how to test javascript working (test cases) as a software tester
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: JavaScript and Screenreaders - The Web Standards Project</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-1576</link>
		<pubDate>Wed, 10 May 2006 06:46:27 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-1576</guid>
					<description>[...] In the first test case exploring JavaScript and screen readers, we&#8217;re looking at some basic events. We&#8217;re not exactly sure what we&#8217;ll find - and that&#8217;s the point, really. We need to start with the basics before we can get very far into the advanced stuff. Hopefully this test will serve as a baseline for comparison as we move forward. This information will be incredibly useful to both the DOM Scripting Task Force and the Accessibility Task Force. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] In the first test case exploring JavaScript and screen readers, we&#8217;re looking at some basic events. We&#8217;re not exactly sure what we&#8217;ll find - and that&#8217;s the point, really. We need to start with the basics before we can get very far into the advanced stuff. Hopefully this test will serve as a baseline for comparison as we move forward. This information will be incredibly useful to both the DOM Scripting Task Force and the Accessibility Task Force. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Fernando</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-1035</link>
		<pubDate>Fri, 03 Mar 2006 02:14:55 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-1035</guid>
					<description>Not a screen reader, but- Lynx for windows displays both the hidden labels and the hidden paragraph. Both appear as if they were normal in every possible way.</description>
		<content:encoded><![CDATA[<p>Not a screen reader, but- Lynx for windows displays both the hidden labels and the hidden paragraph. Both appear as if they were normal in every possible way.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: programming</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-969</link>
		<pubDate>Thu, 09 Feb 2006 02:33:19 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-969</guid>
					<description>Hi, I thought I'd just leave this message on your blog. I hope you don't mind. I've been trying to find blogs where people are talking about &lt;a href="http://smartcards.info-1.org/smartcards/7/programming-ntl-smart-cards.html" rel="nofollow"&gt;programming&lt;/a&gt; and when I was looking, I found this one on you article. thought I would say hi, before I go off to find some more info on this field.</description>
		<content:encoded><![CDATA[<p>Hi, I thought I&#8217;d just leave this message on your blog. I hope you don&#8217;t mind. I&#8217;ve been trying to find blogs where people are talking about <a href="http://smartcards.info-1.org/smartcards/7/programming-ntl-smart-cards.html" rel="nofollow">programming</a> and when I was looking, I found this one on you article. thought I would say hi, before I go off to find some more info on this field.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Che Martin</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-568</link>
		<pubDate>Wed, 31 Aug 2005 01:40:08 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-568</guid>
					<description>Hi all.  I am particularly interested in your findings here.  I am a blind php programmer using jaws, and programming games and database functions for the blind.  I have recently finished a dice game for the blind, and was hoping to use onKeyDown functions on the page to focus the Jaws cursor to particular lines.  For instance, I have a set of headings that show the other players scores, and it would be very useful to the blind player using a screenreader to be able to jump focus to those listings with a keystroke, then back to their own roll with another.
  I would be very happy to help with this project as much as I can, which could include asking other blind users to provide feedback or run tests as needed.
  I did try some experimentation with the onKeyDown functionality of JS, but with little success so far.  It would appear that a Jaws script would have to be embedded for this to work properly, which would mean altering the default browser scripts for jaws users, and that would be a hard sell to say the least.
  I look forward to hearing from any and all of you, and thanks for looking into this complication of screenreader usage.
  Sincerely,
  Che Martin</description>
		<content:encoded><![CDATA[<p>Hi all.  I am particularly interested in your findings here.  I am a blind php programmer using jaws, and programming games and database functions for the blind.  I have recently finished a dice game for the blind, and was hoping to use onKeyDown functions on the page to focus the Jaws cursor to particular lines.  For instance, I have a set of headings that show the other players scores, and it would be very useful to the blind player using a screenreader to be able to jump focus to those listings with a keystroke, then back to their own roll with another.<br />
  I would be very happy to help with this project as much as I can, which could include asking other blind users to provide feedback or run tests as needed.<br />
  I did try some experimentation with the onKeyDown functionality of JS, but with little success so far.  It would appear that a Jaws script would have to be embedded for this to work properly, which would mean altering the default browser scripts for jaws users, and that would be a hard sell to say the least.<br />
  I look forward to hearing from any and all of you, and thanks for looking into this complication of screenreader usage.<br />
  Sincerely,<br />
  Che Martin
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bob Easton</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-517</link>
		<pubDate>Thu, 04 Aug 2005 18:54:13 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-517</guid>
					<description>Kristin, that's an interesting behavior, and I might have an explanation.  Link #8 (well, actually all the links) is coded as a reference to "#", essentially the top of the page.  If you travel, or are transported to the top of the page and then  activate the first link on the page, you fall onto the Accessibility Statement page.</description>
		<content:encoded><![CDATA[<p>Kristin, that&#8217;s an interesting behavior, and I might have an explanation.  Link #8 (well, actually all the links) is coded as a reference to &#8220;#&#8221;, essentially the top of the page.  If you travel, or are transported to the top of the page and then  activate the first link on the page, you fall onto the Accessibility Statement page.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kristin</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-516</link>
		<pubDate>Thu, 04 Aug 2005 02:00:11 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-516</guid>
					<description>On the second part of the test VoiceOver went to the Accessibility Statement page, so when I hit the back button, I had to scroll through the page again to get to the next test. I am, admittedly, a novice on using screen reader technology. So it may have been an simply an issue of me not knowing the right keystrokes.
</description>
		<content:encoded><![CDATA[<p>On the second part of the test VoiceOver went to the Accessibility Statement page, so when I hit the back button, I had to scroll through the page again to get to the next test. I am, admittedly, a novice on using screen reader technology. So it may have been an simply an issue of me not knowing the right keystrokes.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Becky</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-511</link>
		<pubDate>Mon, 01 Aug 2005 14:20:46 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-511</guid>
					<description>This was interesting. I got very different results using the WindowEyes 5.0L beta with IE and with Firefox (Deer Park Alpha 2 beta dated 7/21/05).  The Firefox page worked better than the IE one in Firefox!  I did have a bit of difficulty with link 8 - alt-enter in FF with WE made me lose focus to I had to tab back to link 8 to complete the shift-enter test.  </description>
		<content:encoded><![CDATA[<p>This was interesting. I got very different results using the WindowEyes 5.0L beta with IE and with Firefox (Deer Park Alpha 2 beta dated 7/21/05).  The Firefox page worked better than the IE one in Firefox!  I did have a bit of difficulty with link 8 - alt-enter in FF with WE made me lose focus to I had to tab back to link 8 to complete the shift-enter test.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bob Easton</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-509</link>
		<pubDate>Fri, 29 Jul 2005 13:47:10 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-509</guid>
					<description>Yvette, Yes, you're right.  Going back clears that field.  Sorry for the poor advice.  You can always look at (listen to) the field before pressing the submot botton.  I'll edit the page.  Thanks for bringing it to my attention.</description>
		<content:encoded><![CDATA[<p>Yvette, Yes, you&#8217;re right.  Going back clears that field.  Sorry for the poor advice.  You can always look at (listen to) the field before pressing the submot botton.  I&#8217;ll edit the page.  Thanks for bringing it to my attention.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Yvette</title>
		<link>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-508</link>
		<pubDate>Fri, 29 Jul 2005 12:04:39 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/28/quiz-414-how-do-javascript-operations-affect-accessibility-part-1/#comment-508</guid>
					<description>At the end of the test it says to use the back-button to review the logs collected during the test, but when I return to the previous page the text area has been deleted and all is has is a document.focus. 

I use FF 1.0 on WinXP pro</description>
		<content:encoded><![CDATA[<p>At the end of the test it says to use the back-button to review the logs collected during the test, but when I return to the previous page the text area has been deleted and all is has is a document.focus. </p>
<p>I use FF 1.0 on WinXP pro
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
