Accessibility compliance for Rich Internet apps

Accessibility compliance for Rich Internet apps

{Punk girl in a wheelchair descending a escalator in London underground tube}

How to treat accessibility in rich internet applications ?

There are much more powerful, time saving UI patterns and JavaScript frameworks, ajax libraries than before. But where & how accessibility will be nurtured between all these hoopla ? So far validating accessibility of semantic code was quite easier but may not be that easy when a content is wrapped in intelligent UI widgets rendered by rich internet apps. In one way, web 2.0 backed UI patterns are very intuitive and user friendly but how 'disabled person' is going to access such advanced applications ?

w3.org has come come with new way of looking at rich internet applications accessibility. I was quite keen to understand what's this all about WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications)

WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications) is a set of documents published by the World Wide Web Consortium that specify how to increase the accessibility of dynamic content and user interface components developed with Ajax, HTML, JavaScript and related technologies.

WAI-ARIA describes how to add semantics and other metadata to HTML content in order to make user interface controls and dynamic content more accessible. For example, with WAI-ARIA it is possible to identify a list of links as a navigation menu and to state whether it is expanded or collapsed.

I found an interesting read on 'importance of the ARIA presentation'. The article discusses about bottlenecks of WAI-ARIA. I am sure, WAI-ARIA is the way to go when section 508 standards and WAI's are the necessity in quasi govt and federal linked companies.

>> Read more on the WAI-ARIA here