Accessibility/qa: Difference between revisions

Revision as of 14:26, 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 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 content	RAVEN	Unknown	Firebug, Composer (would require RAVEN to be open source, which it currently is not)

@@ Line 9: / Line 9: @@
 ! Possible integration into interactive dev tools
 |-
-| [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL]
+| [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL content]
 |
 * [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker]
@@ Line 36: / Line 36: @@
 | IA2-Poke is standalone, not sure if RAVEN can be interactive
 |-
-| [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA]
+| [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA content]
 | [http://www.alphaworks.ibm.com/tech/raven RAVEN]
 | Unknown
 | Firebug, Composer (would require RAVEN to be open source, which it currently is not)
 |}