What do you do when the coder’s haven’t included WAI-ARIA in the AJAX. Option 1, ignore it and quote the guidelines; Option 2, try to manually flag it and fix it; or Option 3 try to automatically fix it by programmatically injecting the correct WAI-ARIA directly into content – client side. We discuss Option 3!
Simply we saw a need for a way of identifying AJAX in RIAs, deciding on the type of Widget the AJAX represented – calendar picker, tab bar, etc – and deciding if WAI-ARIA was included. If not we capture best practice from te guidelines and programmatically alter the content client-side, so that the user experiences a fixed page.
Thanks to Google for fully funding the ‘Accessibility Catch-Up: Techniques for Disseminating Accessibility Research (ACup)’ project which produced this work and investigates the possibility of using scripting technology, as used by AxsJAX, to bring developments in accessibility research to users more quickly.