Implementing Screen Reader in Ajax

Screen Readers are one of the most efficient tools a developer could add in an application whether the application is Ajax based or not. With the use of screen readers, the application would have proper interaction with the browser. Using screen readers will even open a lot more options for developers in providing more interactive experience for their users.

Ajax has always been challenging when it will be dealt with screen reader. The main reason for this is the fact that Ajax is a client side programming technique. By loading everything in the client side before the actual interaction, the screen reader will have no way on reading the updates.

But there are actually ways in enabling screen readers in Ajax:

Tip # 1: It is all about the virtual buffer

As already indicated, the main reason why an Ajax based application can’t be read by screen readers is that the client side don’t seem to provide any interaction at all that could be interpreted by the screen reader. But if the developer implements virtual buffer in the functions and user interactions, the screener reader would then be alerted that something has happened in the client side.

This would mean that the application should not be loaded prematurely in the client side. Virtual buffer would have to be done in each data and function so that it could be noticed by screen readers.

Tip # 2: Proper Use of Focus

Fortunately, ECMAScript updates have opened up a lot of possibilities to further enhance the experience of users. They have provided additional tools and functions developers could use to work with screen readers. Among the functions added is “focus”. It’s a simple but highly useful function developers could use.

“Focus” could be implemented by developers in their respective screen readers so that it would focus on the specific change. Without focus, screen readers will naturally sweep the entire application for changes which could take a while.

Tip # 3: Using Forms

Another way to ensure that your Ajax based application is screen reader friendly is to build it as a screen reader friendly application. This could be done by developing an Ajax based application through forms. In using forms – the functions, data and other essential elements that will need to interact with the application would be placed in groups. Since they are already placed in groups, tagging them with screen readers will be a lot easier.

Tip # 4: Choosing the Right Screen Reader Mode

There are four types of screen reader modes: JAWS (Job Access With Speech) Virtual PC Cursor, JAWS PC Cursor, JAWS Forms and Window-Eyes Browse Mode.

JAWS Virtual PC Cursor is highly recommended when you’re building an Ajax application with strong HTML content. Its counterpart is the JAWS PC Cursor wherein it can easily interact when the application even with less to no HTML content.

JAWS Forms on the other hand, could be used if you do not want to intensify virtual buffer in your Ajax based application. Window-Eyes Browse is the final option for a screen reader mode when the Ajax based application is limited in functions or rendered as lightweight.