Friday, May 5th, 2006
One of the largest complaints that people have about Ajax these days is the lack of standards support in the sites developed with it. Since all of the data is dynamic, there’s problems caused with several different types of applications used for “alternative browsing” – such as screen readers. Developers know this and are trying to take steps to improve the situation, but it’s a slow road so far. In this new article on SitePoint, you can check in on one developer’s quest to get a simple Ajax script to be correctly read in a common screen reading application.
We’ve all heard a great deal of buzz about AJAX in the last few months, and with this talk has come a legion of articles, tips, presentations and practical APIs designed to explore the possibilities and try to arrive at best-practice techniques. But, for all of the excitement and hype, still very little has been said on the subject of AJAX and accessibility.
And that’s why I’ve written this article: to present some of the data and analysis I’ve compiled, and see if it points to a useful conclusion.
He gives a little background first, noting that he’s been at this for a while, working for a few months before on how screen-readers parse through a web site and do their thing. He’s found methods to get the applications to read certain parts of the site better than just the default, but the real problem is the update of the page via the DOM. There’s just not a reliable way he’s seen to let the software know the page has been changed.
Posted by Chris Cornutt at 7:08 pm