Report a web accessibility barrier
Describe the blocked task, page and reproduction steps. Send actionable feedback and ask for an alternative when a deadline is approaching.
Follow the method ↓
The answer in 30 seconds
Precise feedback helps a team locate a barrier without asking you to repeat the entire task. You do not need a technical criterion number to explain a real difficulty.
Provide the URL, task, attempted steps, expected outcome and actual barrier. Mention your browser, device and assistive technology when relevant. Use the accessibility statement or website contact. If a deadline is near, also ask for another way to complete the task.
Examples to adapt
Identify the unreachable control, keys used and impact on submission.
Give its title, URL and relevant page; request an accessible version or equivalent information.
State the deadline and request a suitable alternative channel immediately.
Follow the method
- 1Explain the blocked action
State a concrete goal such as sending a form, reading a document or selecting a date. Describe its impact without unnecessary medical or personal case details.
- 2Record reproducible steps
Keep the URL and date, then list actions in order. For example: open the form, navigate with Tab, reach the button and press Enter. Explain what happens next.
- 3Add relevant context
Mention the browser and, where useful, screen reader, zoom or keyboard navigation. A screenshot may help but cannot replace text. Remove personal information.
- 4Find the appropriate contact
Look for an accessibility statement, feedback link or website contact. Send one structured message. Never include a password or authentication code.
- 5Ask for an actionable response
Request acknowledgement, an alternative route and, where possible, a correction update. Keep the message. An individual workaround does not establish that the entire website has been fixed.
A checklist to keep
Use these checks to record your observations. They are a reading aid, not an automatic assessment.
| Check | What to examine | Action |
|---|---|---|
| Page | URL and title | Identify the content |
| Task | Goal and steps | Enable reproduction |
| Barrier | Expected and observed | Explain the impact |
| Follow-up | Deadline and alternative | Request useful action |
Free, no sign-up. UTF-8 text with semicolon-separated columns.
What to check
Automated checks do not cover every usability barrier.
Clear feedback can help without a complete WCAG assessment.
Remove personal information from screenshots and attachments.
Separate an individual workaround from a lasting correction.
Common questions
Must I prove technical non-conformance?
Start by explaining the task and outcome. The website team can then investigate and classify the issue.
What should I ask for with an inaccessible document?
Request an accessible version or equivalent route to the same task, explaining your need and deadline.
Can I use this approach for WWC?
Yes. Use our Contact page with the URL and useful steps, without sending credentials or confidential content.
Sources and documentation
- W3C WAI — Developing an accessibility statement ↗
- W3C WAI — Contacting organizations about inaccessible websites ↗
Documentation consulted on . Examples are illustrative; interfaces and results may change.
Reference record for this resource
Identify the publisher, official destination and practical checks before using the service.
Read the W3C Web Accessibility Initiative record →