Login Register

Dijit A11y Testing Requirements

We need to provide a list of requirements for automated accessibility requirements. Here is an initial list gathered from some of the a11y folks. Feel free to add other requirements and or solutions:

  • keyboard synthesis in order to invoke and check for proper keyboard implementation. Example: focus is on a closed tree item, issue the "open item" key (this is a right arrow in left to right languages) and verify that the tree item is now in the open state and the "next item" key (a down arrow) focuses the first item in the newly opened list.
  • event capture/tracking to determine if focus has been set properly. For example, when a dialog or menu is opened/displayed.
  • a mechanism to verify text equivalents for all images. Not sure how to accomplish this. Visual comparisons via screen capture are very hard to implement and keep up to date enough to be useful.
  • A mechanism to verify that all focusNodes have a ARIA role. This could be accomplished using DOH.
  • A mechanism to verify that ARIA states are updated properly in response to events. In the tree example above verify that the treeitem state changed from expanded=false to expanded=true.

Simulating clicks and keypress in testing

This was asked about in the dijit support forum: http://www.dojotoolkit.org/forum/dijit-dijit-0-9/dijit-support/simulatin...

Contrast audits

Before I forget, I think we might be able to find something to help us automate checking for contrast issues. Perhaps omething like: http://www.paciellogroup.com/resources/contrast-analyser.html

But ideally as a web service: http://juicystudio.com/services/csstest.php#csscheck

I don't have the cycles for a deeper investigation just yet.

cheers,
David