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:229123 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
