James Edwards presents his findings having looked at how AJAX interacts (or fails to) with various screen readers. The results aren’t exactly inspiring.Skip to comment form
There’s something of an oxymoron going on there in the heading. Can you spot it? The words ‘accessibility’ and ‘AJAX’. They really are not the best of bed fellows, as many people have discovered. However, although many of us web professionals just ‘kinda know’ that AJAX is bad for web accessibility, when pushed many would not be able to say exactly why or how certain screen readers cope with content that’s been changed using AJAX (or using DOM Scripting methods that don’t make use of AJAX at all). One man who can claim to know a bit about it is James Edwards (aka Brothercake):
The above is an excerpt from an article that James has published on Sitepoint entitled AJAX and Screenreaders: When Can it Work? which I strongly advise all web professionals to read and absorb. Even if you’re not currently doing ‘cool’ things with AJAX, you should read it so that you are aware of the impact of any future development work, should you choose to go down that road. Top work, James.
- #1 On May 4th, 2006 4:54 am