Accessibility/qa

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