Accessibility/qa: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
Here are some thoughts on what kind of testing we need: | 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=" | {| summary="Mozilla accessibility testing needs and possible tools for the job" width="90%" border="1" cellspacing="5" cellpadding="1" | ||
! Testing need | ! Testing need | ||
! Possible tools as a starting point | ! Possible tools as a starting point | ||
| Line 19: | Line 19: | ||
| None (use AT-Poke/Pypoke as standalone) | | None (use AT-Poke/Pypoke as standalone) | ||
|- | |- | ||
| IAccessible2 | | [http://www.linux-foundation.org/en/Accessibility/IAccessible2 IAccessible2] | ||
| IA2-Poke, [http://www.alphaworks.ibm.com/tech/raven RAVEN] | | IA2-Poke, [http://www.alphaworks.ibm.com/tech/raven RAVEN] | ||
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots | | [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots | ||
Revision as of 22:22, 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 | 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 |