Accessibility/qa: Difference between revisions

Revision as of 22:33, 20 February 2007

The Mozilla accessibility testing strategy is still under development.

Here are some thoughts on what kind of testing we need:

Testing need	Possible tools as a starting point	Possible integration points for automated test tools	Possible integration into interactive dev tools
XUL	WebAIM XUL checker XUL validator	Tinderbox/buildbots addons.mozilla.org auto review process	DOM Inspector XUL Explorer
ATK & AT-SPI	Dogtail RAVEN AT-Poke Pypoke	Tinderbox/buildbots	None (use AT-Poke/Pypoke as standalone)
IAccessible2	IA2-Poke RAVEN	Tinderbox/buildbots	IA2-Poke is standalone, not sure if RAVEN can be interactive
ARIA	RAVEN	Unknown	Firebug, Composer (would require RAVEN to be open source, which it currently is not)

@@ Line 34: / Line 34: @@
 * [http://www.alphaworks.ibm.com/tech/raven RAVEN]
 | [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots
-| None (use any of the above as standalone)
+| IA2-Poke is standalone, not sure if RAVEN can be interactive
 |-
 | [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA]
+| [http://www.alphaworks.ibm.com/tech/raven RAVEN]
 | Unknown
-| Unknown
+| Firebug, Composer (would require RAVEN to be open source, which it currently is not)
-| Firebug, Composer
 |}