Accessibility/qa

The Mozilla accessibility testing strategy is still under development.

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

{! summary="Mozilla accessibility testing needs and possible tools for the job" width="90%" border="1" cellspacing="1" cellpadding="1" ! Testing need ! Possible tools as a starting point | Integration points for automated test tools | Integration into interactive dev tools |- | Automated testing for XUL | WebAIM XUL checker, XUL validator | Tinderbox/buildbots, DOM Inspector, XUL Explorer, addons.mozilla.org auto review process |- | ATK/AT-SPI | Dogtail, RAVEN (if open sourced) | Tinderbox/buildbots |- | IAccessible2 | IA2-Poke, Accessibility Tools Framework from IBM Tokyo labs (if open sourced) | Tinderbox/buildbots (via Accessibility Tools Framework | None (use any of the above as standalone) |- | ATK/AT-SPI interactive testing | AT-Poke, PyPoke | None | None (use AT-Poke/Pypoke as standalone) |- ARIA | Accessibility Tools Framework from IBM Tokyo labs (if open sourced) | ? | ? |}