Accessibility/qa: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
|- | |- | ||
| [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA] | | [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA] | ||
| | | Unknown | ||
| | | Unknown | ||
| | | Unknown | ||
|} | |} | ||
Revision as of 22:16, 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 | Integration points for automated test tools | 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 (via Accessibility Tools Framework | None (use any of the above as standalone) |
| ARIA | Unknown | Unknown | Unknown |