Accessibility/qa: Difference between revisions
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" border="1" cellspacing="1" cellpadding=" | {| 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 | ||
Revision as of 22:28, 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 |
|
||
| ATK & AT-SPI | Tinderbox/buildbots | None (use AT-Poke/Pypoke as standalone) | |
| IAccessible2 |
|
Tinderbox/buildbots | None (use any of the above as standalone) |
| ARIA | Unknown | Unknown | Firebug, Composer |