Comments on: Simple AJAX Test 1 http://www.access-matters.com/2007/01/22/simple-ajax-test-1/ Seeking Best Accessibility Practices Wed, 14 May 2008 15:52:52 +0000 http://wordpress.org/?v=2.1 By: Ron Graham http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-23247 Ron Graham Tue, 23 Jan 2007 03:22:44 +0000 http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-23247 I read about your site through a Google alert for the term "assistive technology." I was interested enough by the short blurb in the email to come here and read more. I then followed the instructions, clicking the link, which then updated to read the response, "Hello World." It went smoothly with no problems. I am using JAWS 8.0 and IE7 on a home pc running Win XP Home with SP2. I read about your site through a Google alert for the term “assistive technology.” I was interested enough by the short blurb in the email to come here and read more. I then followed the instructions, clicking the link, which then updated to read the response, “Hello World.” It went smoothly with no problems.

I am using JAWS 8.0 and IE7 on a home pc running Win XP Home with SP2.

]]> By: Adrian Higginbotham http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-23285 Adrian Higginbotham Tue, 23 Jan 2007 12:29:27 +0000 http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-23285 jfw 8 and ie7, pressing enter on the Link does provoke the intended response however the next problem is that many screenreader users would expect activating a link to cause a transition to a new page, generate an audible click from the browser, cause the screenreader to undertake the default new page actions, in the case of jaws this includes announce introductory info about the new page (number of links etc), and begin to read the page. In The example there is no distinguishable action caused by activating the link until you read beyond the Link. if you have already read beyond the link and know what is there then when revisiting this text you are of course then aware that it has changed. the complexity is that in this example the screenreader does not inform the user that clicking the link has provoked a response, nor does it indicate what or where this change is. What is desirable is that the screenreader recognise the function of the link and report back on the effect of activating it as in the case of 'mouseover' actions. when using the activate on mouseover keystroke within jfw (when an item with applicable action is selected) jfw echos 'page chaged at line xx'. The downside here is that it is yet another keystroke to remember, and the change is not always decernible e.g if it is a colour change then it has no material impact on the screenreader users perception of the content. jfw 8 and ie7, pressing enter on the Link does provoke the intended response however the next problem is that many screenreader users would expect activating a link to cause a transition to a new page, generate an audible click from the browser, cause the screenreader to undertake the default new page actions, in the case of jaws this includes announce introductory info about the new page (number of links etc), and begin to read the page. In The example there is no distinguishable action caused by activating the link until you read beyond the Link. if you have already read beyond the link and know what is there then when revisiting this text you are of course then aware that it has changed. the complexity is that in this example the screenreader does not inform the user that clicking the link has provoked a response, nor does it indicate what or where this change is. What is desirable is that the screenreader recognise the function of the link and report back on the effect of activating it as in the case of ‘mouseover’ actions. when using the activate on mouseover keystroke within jfw (when an item with applicable action is selected) jfw echos ‘page chaged at line xx’. The downside here is that it is yet another keystroke to remember, and the change is not always decernible e.g if it is a colour change then it has no material impact on the screenreader users perception of the content.

]]> By: steve faulkner http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-23395 steve faulkner Wed, 24 Jan 2007 11:29:12 +0000 http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-23395 Adrian wrote: <blockquote>many screenreader users would expect activating a link to cause a transition to a new page</blockquote> Links are also commonly used for navigating within a document. <blockquote>when using the activate on mouseover keystroke within jfw (when an item with applicable action is selected) jfw echos ‘page chaged at line xx’. </blockquote> Freedom Scientific have not chosen to implement this functionality for dynamic updates other than those triggered by the mouseover event. Adrian wrote:

many screenreader users would expect activating a link to cause a transition to a new page

Links are also commonly used for navigating within a document.

when using the activate on mouseover keystroke within jfw (when an item with applicable action is selected) jfw echos ‘page chaged at line xx’.

Freedom Scientific have not chosen to implement this functionality for dynamic updates other than those triggered by the mouseover event.

]]> By: 38e162dd025b http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-126719 38e162dd025b Tue, 13 May 2008 19:56:42 +0000 http://www.access-matters.com/2007/01/22/simple-ajax-test-1/#comment-126719 <strong>38e162dd025b...</strong> 38e162dd025bf37a1947... 38e162dd025b…

38e162dd025bf37a1947…

]]>