Accessibility/qa: Difference between revisions

Revision as of 14:35, 21 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 content	WebAIM XUL checker XUL validator	Tinderbox/buildbots addons.mozilla.org auto review process	DOM Inspector XUL Explorer
ATK & AT-SPI	Dogtail RAVEN AT-Poke Accerciser	Tinderbox/buildbots	None (use AT-Poke/Accerciser as standalone)
IAccessible2	IA2-Poke RAVEN	Tinderbox/buildbots	IA2-Poke is standalone, not sure if RAVEN can be interactive
ARIA content	RAVEN	Unknown	Firebug, Composer (would require RAVEN to be open source, which it currently is not)

@@ Line 25: / Line 25: @@
 * [http://www.alphaworks.ibm.com/tech/raven RAVEN]
 * [http://developer.gnome.org/projects/gap/testing/at-poke-test-cases.html AT-Poke]
-* Pypoke
+* [http://live.gnome.org/Accerciser Accerciser]
 | [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots
-| None (use AT-Poke/Pypoke as standalone)
+| None (use AT-Poke/Accerciser as standalone)
 |-
 | [http://www.linux-foundation.org/en/Accessibility/IAccessible2 IAccessible2]