Accessibility/qa: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 9: Line 9:
! Integration into interactive dev tools
! Integration into interactive dev tools
|-
|-
| XUL
| [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL]
| [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker], [http://starkravingfinkle.org/blog/xul-explorer/ XUL validator]
| [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker], [http://starkravingfinkle.org/blog/xul-explorer/ XUL validator]
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots, DOM Inspector, XUL Explorer, addons.mozilla.org auto review process
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots, addons.mozilla.org auto review process
| DOM Inspector, XUL Explorer
|-  
|-  
| ATK/AT-SPI
| [http://developer.gnome.org/doc/API/2.0/atk/ ATK]/[http://developer.gnome.org/doc/API/2.0/at-spi/ AT-SPI]
| [http://people.redhat.com/zcerza/dogtail/ Dogtail], [http://www.alphaworks.ibm.com/tech/raven RAVEN (if open sourced)], AT-Poke, Pypoke
| [http://people.redhat.com/zcerza/dogtail/ Dogtail], [http://www.alphaworks.ibm.com/tech/raven RAVEN], AT-Poke, Pypoke
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots
| None (use AT-Poke/Pypoke as standalone)
| None (use AT-Poke/Pypoke as standalone)
|-
|-
| IAccessible2
| IAccessible2
| IA2-Poke, Accessibility Tools Framework from IBM Tokyo labs (if open sourced)
| 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 (via Accessibility Tools Framework
| None (use any of the above as standalone)
| None (use any of the above as standalone)

Revision as of 22:14, 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 Accessibility Tools Framework from IBM Tokyo labs (if open sourced) ? ?