Accessibility/qa: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 9: Line 9:
! Possible integration into interactive dev tools
! Possible integration into interactive dev tools
|-
|-
| [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL]
| [http://developer.mozilla.org/en/docs/XUL_accessibility_guidelines XUL content]
|
|
* [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker]
* [http://www.xulplanet.com/aaron/files/xultool0.1.xpi WebAIM XUL checker]
Line 25: Line 25:
* [http://www.alphaworks.ibm.com/tech/raven RAVEN]
* [http://www.alphaworks.ibm.com/tech/raven RAVEN]
* [http://developer.gnome.org/projects/gap/testing/at-poke-test-cases.html AT-Poke]
* [http://developer.gnome.org/projects/gap/testing/at-poke-test-cases.html AT-Poke]
* Pypoke
* [http://live.gnome.org/Accerciser Accerciser]
| [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/Accerciser as standalone)
|-
|-
| [http://www.linux-foundation.org/en/Accessibility/IAccessible2 IAccessible2]
| [http://www.linux-foundation.org/en/Accessibility/IAccessible2 IAccessible2]
Line 36: Line 36:
| IA2-Poke is standalone, not sure if RAVEN can be interactive
| 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]
| [http://www.alphaworks.ibm.com/tech/raven RAVEN]
| Unknown
| Unknown
| Firebug, Composer (would require RAVEN to be open source, which it currently is not)
| 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
  • Tinderbox/buildbots
  • addons.mozilla.org auto review process
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)