InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

The State of Accessibility with Ajax

Posted by Scott Delap on Oct 16, 2006

Sections
Development
Topics
Rich Internet Apps ,
Java
Tags
AJAX
One of the items of concern as a result of the Ajax revolution is accessibility. Screen reading technology has found it difficult to keep pace with advancements in application design.  Access Matters has published a roundup of articles to serve as a starting point for further discussions on accessibility in Ajax applications:
Making Ajax Work with Screen Readers - Perhaps the single most enlightening current article that helps us understand the difficulties with AJAX ... This article is a must read for anyone who is really interested in why all the current fuss about AJAX accessibility. Bottom line, screen readers are not yet capable of reliably recognizing when dynamically updated content has changed...

AJAX and Screenreaders: When Can it Work? - [author James Edwards] has invested a tremendous amount of hard work understanding how JavaScript and screen readers interact. His tests and results are posted right here on this blog. James investigates at a level of detail that would try the patience of most. His SitePoint article explores an how various approaches work and fail (too often) with a dizzying selection of screen readers...

AJAX Accessibility Overview - ... Becky [Gibson] offers a number of very reasonable ideas which improve the likelihood that the material will be discovered and handled by screen readers. Such as: Place dynamically updated material after the trigger event, later in the reading order. Write new material into an existing div instead of creating a new one...

In closing, the article mentions that a number of people including the authors of the above three pieces are working on longer term solutions.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.