Accessibility/qa: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(15 intermediate revisions by 2 users not shown) | |||
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 | {| summary="Mozilla accessibility testing needs and possible tools for the job" border="1" cellspacing="1" cellpadding="8" | ||
! Testing need | ! Testing need | ||
! Possible tools as a starting point | ! Possible tools as a starting point | ||
! | ! Possible integration points for automated test tools | ||
! | ! Possible integration into interactive dev tools | ||
|- | |- | ||
| | | [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL content] | ||
| WebAIM XUL checker | | | ||
| Tinderbox/buildbots | * [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker] | ||
* [http://starkravingfinkle.org/blog/2007/02/xul-validator-beta/ XUL validator] | |||
| | |||
* [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots | |||
* addons.mozilla.org auto review process | |||
| | |||
* [http://www.mozilla.org/projects/inspector/ DOM Inspector] | |||
* [http://starkravingfinkle.org/blog/xul-explorer/ 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] | ||
| Dogtail | | | ||
| Tinderbox/buildbots | * [http://people.redhat.com/zcerza/dogtail/ Dogtail] | ||
* [http://www.alphaworks.ibm.com/tech/raven RAVEN] | |||
* [http://developer.gnome.org/projects/gap/testing/at-poke-test-cases.html AT-Poke] | |||
* [http://live.gnome.org/Accerciser Accerciser] | |||
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots | |||
| None (use AT-Poke/Accerciser as standalone) | |||
|- | |- | ||
| IAccessible2 | | [http://www.linux-foundation.org/en/Accessibility/IAccessible2 IAccessible2] | ||
| IA2-Poke | | | ||
| Tinderbox/buildbots | * IA2-Poke | ||
| | * [http://www.alphaworks.ibm.com/tech/raven RAVEN] | ||
| [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox Tinderbox]/buildbots | |||
| IA2-Poke is standalone, not sure if RAVEN can be interactive | |||
|- | |- | ||
| [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA] | | [http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications ARIA content] | ||
| | | [http://www.alphaworks.ibm.com/tech/raven RAVEN] | ||
| | | Unknown | ||
| | | Firebug, Composer (would require RAVEN to be open source, which it currently is not) | ||
|} | |} |
Latest revision as of 14:46, 21 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 content |
|
||
ATK & AT-SPI | Tinderbox/buildbots | None (use AT-Poke/Accerciser as standalone) | |
IAccessible2 |
|
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) |