Example context. Preview only. Nothing is submitted.
When to sendSomeone encounters an accessibility barrier in your website or product.
- 01
What was difficult?
Capture the intended action and what made it difficult. A page description is welcome; the person does not need to know a URL or accessibility standard.
See the questions
- Where did you encounter the problem?
- A page name or description can locate the problem when a URL is unavailable.
- What were you trying to do?
- The intended action explains the effect of the barrier.
- What made that difficult or impossible?
- Ask what stopped or made the action difficult, without requiring technical terminology.
- 02
Details that may help
Offer optional technical context and a way to follow up. Neither is required to report a barrier.
See the questions
- Anything useful about your device or setup?
- Optional browser, assistive technology, or settings can help reproduce the issue.
- Email for follow-up
- A reply address is useful only when the person is happy to be contacted about this report.
Using the answers
Recreate the barrier in the stated context, and consider its effect on the person’s task. A report is evidence to investigate, not a conformance audit or a diagnosis of the respondent.
When to choose another form
As the only way to get help. Someone blocked by a form may need email, phone, or another accessible route.
Before you publish
Provide an accessible alternative contact route and assign someone to review reports. Test this form with keyboard navigation and relevant assistive technology.
Ask only for relevant technical information. Do not require a disability diagnosis, screenshot, or software-version lookup before accepting a report.