Accessibility Feedback Form Template

Remediation purpose: Use this form to capture the affected page, barrier type, user context, and optional reply request so a team can reproduce and fix an accessibility problem.

Let visitors report a barrier with enough context for the team to investigate.

Download the field schema

Preview the barrier report

Page and barrier type route the issue. Description and technology context help the team reproduce it without requiring the reporter to diagnose the cause.

Affected experience

Page URL Required
Barrier type RequiredKeyboardScreen readerContrastCaptionsContentOther

Barrier context and reply choice

Describe the barrier Required
Browser, device, or assistive technology
I would like a reply
Report accessibility barrier

Details that help reproduce a barrier

Page and barrier type route the issue. Description and technology context help the team reproduce it without requiring the reporter to diagnose the cause.

  • Email addressProvides an optional reply channel without making identity a condition of reporting.
  • Page URLIdentifies the exact page or form where the barrier occurred.
  • Barrier typeHelps route the report while preserving an Other choice for unlisted problems.
  • Describe the barrierCaptures the blocked task and observed behavior in the visitor's words.
  • Browser, device, or assistive technologyAdds optional reproduction context when the reporter is comfortable sharing it.
  • I would like a replySeparates a request for follow-up from anonymous issue reporting.

Offer access, reproduce, and verify

The accessibility owner can offer an alternative, investigate the affected task, and regression-test the repair.

Offer an alternative

Acknowledge and offer an accessible alternative for the blocked task.

Reproduce the barrier

Reproduce with the supplied context without demanding extra diagnosis.

Report and regression-test the fix

Report the fix or workaround and add the defect to regression tests.

Use this as an accessible support route

Use this to let visitors report a barrier with enough page and technology context for reproduction.

Publish an equivalent contact method

  • Publish email or phone fallback beside the form.
  • Make contact details optional unless a reply is requested.
  • Do not require the reporter to know technical terminology.

The alternative and repair decision

This template helps a visitor report an accessibility barrier with the affected page, barrier type, observed problem, and optional technology context. Contact details remain optional unless the person asks for a reply, and another accessible contact route should always be available.

Use the guidance for accessible form validation and errors so a person reporting a barrier can recover from another barrier in the form itself.

Following one keyboard barrier to a fix

Investigating a keyboard navigation barrier. An accessibility owner can use the page URL and barrier description to reproduce the blocked task, offer an immediate alternative, and add the confirmed defect to regression testing. The reporter is not required to diagnose the technical cause.

Accessibility feedback questions

Answers about the choices, limits, and handoff shown on this page.

What should an accessibility feedback form ask?

Ask for the affected page, blocked task or barrier, and optional reproduction context. Make contact information optional unless a reply is requested.

Why provide another contact method?

The reported barrier may also prevent use of the feedback form. Publish an accessible email, phone, or equivalent alternative beside it.

Create a barrier-reporting route that works

Provide an alternative channel, keep contact optional, and test the form itself with keyboard, zoom, and error recovery.

Compare form workflows