Accessibility/qa: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No 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="1" cellpadding="1"
{| summary="Mozilla accessibility testing needs and possible tools for the job" width="90%" border="1" cellspacing=".5em" cellpadding="1"
! Testing need
! Testing need
! Possible tools as a starting point
! Possible tools as a starting point
Line 21: Line 21:
| 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 (via Accessibility Tools Framework
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots  
| None (use any of the above as standalone)
| None (use any of the above as standalone)
|-
|-

Revision as of 22:17, 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 None (use any of the above as standalone)
ARIA Unknown Unknown Unknown