Issues with Testing ARIA-based Interfaces for Accessibility

Events happening in the community are now at Drupal community events on www.drupal.org.
Posted by cliff on April 24, 2010 at 6:51pm

Not much to say here, but perhaps this would be a good place to hash out what we know and need to know about doing accessibility tests on ARIA-based interfaces. It's a real challenge.

A good place for background information is Jared Smith's presentation at the November 2009 Accessing Higher Ground Conference, Accessibility of Rich Internet Applications.

Comments

Hard work

Posted by Everett Zufelt on April 27, 2010 at 8:47pm

Hey Cliff,

What I can say is that it is hard work to test ARIA interfaces, or accessible web-apps, for accessibility. Primarily this s because, due to the draft nature of ARIA 1.0, and it's inconsistent implementation by browser and AT vendors, there is a lot of testing to be done.

A couple of thoughts.

  1. Decide upon the supported browsers and ATs. This narrows the testing.

  2. Test components and interfaces. I can't stress enough that along with testing UIs we should start by testing UI components. If a UI component (toggle button, dialog, inline edit) is working properly, then it will * likely * continue to work properly when implemented as part of a UI.

  3. See the ARIA test cases and examples on the CodeTalks wiki at http://wiki.codetalks.org/wiki/index.php/Main_Page

Accessibility Consultant & Web Developer - Zufelt.ca
@ezufelt on Twitter | LinkedIn profile

Accessibility

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

AltStyle によって変換されたページ (->オリジナル) /