File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes HTML, CSS and JavaScript and the fly likes ajax and blind users Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » HTML, CSS and JavaScript
Bookmark "ajax and blind users" Watch "ajax and blind users" New topic

ajax and blind users

Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33124

This article talks about Ajax and accessiblity for blind users. Does anyone have views on how Ajax will affect accessiblity?

There is the potential to have any screen element change dynamically at runtime without the user knowing where to look. On a non-Ajax website, a blind user listens as the screen reader starts from the beginning of each page as it loads. With Ajax, there would have to be some sort of mechanism for informing the user to tell the screen tool to start over. Maybe a hidden textual clue?

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Eric Pascarello

Joined: Nov 08, 2001
Posts: 15385
The 508 stuff can be a problem, I think the vendors of screen readers need to look more into the W3C standards!

But this may help develoers see the light:

Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33124

Thanks for answering my real question even though I didn't mention 508 explictly. [For those who don't know Section 508 is a US federal law requiring accessibility to disabled users on all government applications.]

re: fang - Cool! Cool! Cool!

I'll have to try Fangs at work next week. It's frustrating trying to test through Jaws as I don't have the patience to listen to my screens. That and the license is so expensive it isn't on all our desks. This looks really promising.
Stephen Cote

Joined: Nov 11, 2005
Posts: 9
Fangs is a nice idea, but the trouble with using it to develop accessible Web applications is that you have to place a certain level of trust in Fangs to reproduce exactly what other software, such as JAWS, would produce for the accessibility-minded user. I used Fangs for about five minutes, four of which were "neat, nice, way-cool", and the last minute was, "uh, wait, this isn't exactly what JAWS is producing".

I don't think AJAX is going to affect blind users any more or less than before. If a Web application is developed with accessibility in mind, then the end result of any AJAX tranaction would include the requisite markup to be accessible, or otherwise it wouldn't.

Either the developers and/or business is accessiblility-minded, or it's not, and that will be reflected in the product, regardless of how that product is delivered, be it brick-and mortal, HTTP, Javascript + XML + HTTP (AJAX), or otherwise.

Stephen W. Cote<br /><br />
I agree. Here's the link:
subject: ajax and blind users
It's not a secret anymore!