| title | description | ms.assetid | keywords | ms.topic | ms.date | ||
|---|---|---|---|---|---|---|---|
Testing with AccChecker |
Describes the typical testing workflow that incorporates AccChecker. |
18C2DDEE-D199-4C22-9ADF-1E07B1325A06 |
|
article |
05/31/2018 |
The following scenario describes the steps that you typically follow when testing with AccChecker.
Note
When AccChecker verification routines are running, user interaction with the host machine can interfere with some routines. We recommend that no further user interaction occur until AccChecker notifies the user that all tasks are complete.
-
Run AccChecker verifications on a particular target application or control. For more information, see Verifications Tab.
[!Note]
AccChecker doesn't explore all UI permutations in an application. Elements hidden within controls such as windows, panes, tabs, and menus must be exposed manually. -
Examine the AccChecker error log and assess or triage the results. Fix trivial issues and log severe bugs as appropriate.
-
Generate a suppression file for bugs and errors that can be ignored until regression testing.
-
Re-run AccChecker verifications with the suppression file and initial bug fixes. This provides a snapshot of the issues in the current implementation of Microsoft Active Accessibility and establishes a baseline for regression testing.
-
Integrate the AccChecker APIs and suppression file into an automated test framework for regression testing on bugs logged from the initial AccChecker verifications.
[!Note]
As bugs are fixed, the suppression file should be modified as required. -
Confirm that no regressions or new accessibility bugs have been introduced into the application or control.