Audit operations
Write a Reproducible Accessibility Issue
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Turn an observation into a repairable issue with a clear trigger, user impact and expected behavior. Include enough environment detail to reproduce it while removing personal information from evidence.
A practical example
A dialog closes visually, but keyboard focus moves to the start of the page instead of returning to its trigger.
How to check it
- Record the URL, product version, browser and assistive technology. Describe the starting state and the shortest sequence that reproduces the barrier.
- State what happened, what should happen and how the difference affects the task. Attach relevant screenshots, spoken output or a small code excerpt without sensitive data.
- Map the issue to a supported criterion where appropriate and assign an owner. Include a concrete retest procedure rather than only a generic instruction to make it accessible.
What can be missed
A scanner rule name is not a complete issue report. Avoid declaring a legal violation from a technical observation without the relevant applicability analysis.
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.