I finally tested this on a few platforms and it worked on all of them: http://esc.curtin.edu.au/testreader.html
The test platforms: 1) JAWS 7.0 with FF1.5 and IE6, on WinXP SP2 2) Window-Eyes 5.5, FF1.5 and IE6, WinXP SP2 3) VoiceOver as distributed with MacOS 10.4, on Safari 2.0.3 In all, the links that get written to the screen by CFAJAX after the initial link is clicked (well after the page loads) are all available to the screen readers. Interestingly, it worked least-well with FF1.5 and Window-Eyes (the screen focus gets messed up). Of course, to make it easier to use I'd add an alert() that said there are new links to see etc, but this at least demonstrates that content can be written to the page after it loads and that content is available to screen readers. On 1/11/06, Sandra Clark <[EMAIL PROTECTED]> wrote: > I'd love to see that James, do you have a link? > > -----Original Message----- > From: James Holmes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 10, 2006 8:42 PM > To: CF-Talk > Subject: Re: I don't know if this is even possible > > Rubbish. I tested all of my stuff in FF pre 1.5 and IE 6, months ago - all > of the new links I was writing to the screen (via AJAX) read out perfectly > in all 3 screen readers I tested. The links were not in a form. > > On 1/11/06, Sandra Clark <[EMAIL PROTECTED]> wrote: > > The problem is that up until Firefox 1.5 dHTML is not totally > > accessible by screen readers. Most screen readers can handle some > > javascript, but not any screen changes after a body onload(). Thus any > > dHTML changes to the screen will not be noticeable to screen readers. > > If a user is in a forms mode, it might work in some screen readers, > > but its not across the board. And if you aren't talking about a form, > > but changing the screen, thats where the problems come in. > > > > Ajax is not inherently inaccessible, its the way of presenting the > > information (dHTML and Javascript changes to the client screen) that > > are problematic. > > > > FireFox 1.5 has incorporated a newer version of Javascript (think Web > > 2.0) which when combined with Window-eyes actually created accessible > javascript. > > I saw a demo by IBM at the CSUN accessibility conference last March. > > Unfortunately most disabled users are using a combination of IE and > > Jaws, neither of which supports it. -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:230463 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
