Audit operations
Handle an Accessibility Feedback Report
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Turn a visitor's report into a respectful support response and a reproducible product issue. Collect only the information needed to understand the barrier. Keep personal or disability information out of public issue records.
A practical example
A visitor says the booking calendar cannot be used with their screen reader and needs to complete a time-sensitive task.
How to check it
- Acknowledge the report through the established support process and identify the task, page and barrier. Offer a practical accessible route when one is available.
- Ask for optional technical details only when needed to reproduce the problem. Test the reported state and record the user impact without requiring a diagnosis.
- Assign the issue, track the repair and verify the result. Follow the organization's process for informing the reporter and updating any published known limitation.
What can be missed
A request for excessive proof can make support another barrier. The immediate task and the long-term product repair both need an owner.
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.