40
edits
QA/Firefox3/TestPlan/UIAccessibility: Difference between revisions
Jump to navigation
Jump to search
QA/Firefox3/TestPlan/UIAccessibility (view source)
Revision as of 21:23, 14 September 2007
, 14 September 2007→Overview
| Line 4: | Line 4: | ||
= Overview = | = Overview = | ||
This will outline the process to verify the accessibility of the Firefox 3 user interface. Tests will be designed to protect against regressions in the accessibility code, as well as to ensure the accessibility of new UI elements as they are added during the beta process. Testing will primarily be done through manual Litmus test cases, supplemented by | This will outline the process to verify the accessibility of the Firefox 3 user interface. Tests will be designed to protect against regressions in the accessibility code, as well as to ensure the accessibility of new UI elements as they are added during the beta process. Testing will primarily be done through manual Litmus test cases, supplemented by object inspection and event testing using the rellevant Linux and Windows tools. Gecko rendering of websites (AJAX/ARIA, web forms, etc.) will be tested using dogfooding of nightly builds and specific test cases. | ||
= Scope of planned testing = | = Scope of planned testing = | ||
The accessible UI will be tested with a combination of Litmus test cases using assistive technology products as well as testing tools such as Accerciser. Due to the current differences between assistive technologies across platforms, automated testing would have limited effectiveness. | The accessible UI will be tested with a combination of Litmus test cases using assistive technology products as well as testing tools such as Inspect32, Accevent and Accerciser. Due to the current differences between assistive technologies across platforms, automated testing would have limited effectiveness. | ||
= Platforms = | = Platforms = | ||