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|
|ATK & AT-SPI||Tinderbox/buildbots||None (use AT-Poke/Accerciser as standalone)|
||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)|