Why retesting matters
A developer may make a technically reasonable change that does not fully resolve the original accessibility problem or that introduces another problem.
Retesting closes the evidence loop by checking the actual result.
Good retesting practice
- Repeat the test that originally failed.
- Use the same relevant conditions where practical.
- Confirm that the expected accessibility behaviour now occurs.
- Record the new evidence.
- Only mark the work resolved when the retest supports that conclusion.
Related articles
Developer ActionsTurn confirmed accessibility problems into clear, trackable work for developers.Using Fix StudioUse AAI's developer-oriented remediation workspace to support accessibility fixes.GitHub source and pull requestsUnderstand how AAI uses GitHub as a source of truth, why repository provenance matters and when a repair can be sent through the GitHub workflow.
Was this article helpful?
We will add article feedback capture in the next Help Centre iteration. For now, please tell AAI Support if anything here is unclear or incomplete.
Contact AAI →