AJAX Accessibility for Websites

By Brigitte Simard
2008-03-10


Accessibility issues caused by AJAX

AJAX and JavaScript are usually used to update page content. When this happens screen readers respond in a variety of different ways, depending on both the screen reader and the browser:

• Screen readers aren't aware of the changes so will read out the unmodified version of the page. This means screen reader users don't get the updated content of the page.
• Screen readers are aware of the changes but will only read the modified content when they naturally reach it. This is fine unless the modified content precedes users' current location. If this happens, they're unlikely to hear this content.
• Screen readers start reading the modified page but from the very top. This means that users have to essentially listen to all of the page content again. It can be difficult for these users to know which content has been updated and where in the page this content is.
• Screen readers are automatically taken to the modified content so users instantly know that page content has been updated - this can however severely disorientate users.

Screen magnifier users might not notice changes that have occurred outside the areas they're interacting with. They can therefore miss out on important information especially if the changed content takes place above their current location on the page.

Finally, AJAX requires JavaScript to be enabled. Although assistive technologies can now handle many uses of JavaScript they don't all provide complete support.

Tutorial Pages:
» Introduction
» What is AJAX?
» Accessibility benefits of AJAX
» Accessibility issues caused by AJAX
» Recommendations for AJAX and accessibility

Related Tutorials: » Getting Started with AJAX in jQuery » GWT Basics: AJAX Programming with Java » AJAX and PHP Form Processing » The obligatory 'My Ajax Tutorial' Post » A Designer's Guide to Prototyping Ajax » Ajax Wireframing Approaches