Audit operations
Retest an Accessibility Repair
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Verify a repair against the original reproduction steps and the surrounding user process. Record the exact build and environment. Keep the original evidence so a reviewer can see what changed.
A practical example
A form error summary now receives focus, but the linked field and success state still need checking.
How to check it
- Reproduce the original issue on the repaired build using the documented environment. Compare actual behavior with the stated acceptance condition.
- Test adjacent states and another representative use of the shared component. Check that the repair has not introduced a new focus, naming or visual problem.
- Record the result, evidence and remaining limitations. Close the issue only when the acceptance condition is met, or describe why more work is needed.
What can be missed
A code change or a developer's screenshot is not the same as a verified result. Retest the user task, especially when the repair affects shared behavior.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.