Accessibility/qa: Difference between revisions

Revision as of 22:20, 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	None (use any of the above as standalone)
ARIA	Unknown	Unknown	Firebug, Composer

@@ Line 6: / Line 6: @@
 ! Testing need
 ! Possible tools as a starting point
-! Integration points for automated test tools
+! Possible integration points for automated test tools
-! Integration into interactive dev tools
+! Possible integration into interactive dev tools
 |-
 | [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL]
 | [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker], [http://starkravingfinkle.org/blog/xul-explorer/ XUL validator]
 | [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots, addons.mozilla.org auto review process
-| DOM Inspector, XUL Explorer
+| [http://www.mozilla.org/projects/inspector/ DOM Inspector], [http://starkravingfinkle.org/blog/2006/12/xul-explorer-02/ XUL Explorer]
 |-
 | [http://developer.gnome.org/doc/API/2.0/atk/ ATK]/[http://developer.gnome.org/doc/API/2.0/at-spi/ AT-SPI]
@@ Line 27: / Line 27: @@
 | Unknown
 | Unknown
-| Unknown
+| Firebug, Composer
 |}