Provide a useful route for website access feedback

The decision this workflow supports

A guest who encounters a website barrier needs a practical contact route. The restaurant should be able to record the problem and offer an approved alternative without asking the guest to diagnose the technology or disclose a disability.

Put the review process in place

Publish a clear feedback contact and assign a reviewer. Ask which task the guest was trying to complete and where the difficulty occurred. Keep website access feedback separate from assumptions about physical venue suitability, which staff must discuss directly.

Worked example for your team

A fictional guest reports that they cannot reach the event form’s submit control. The response should ask for the page or task and offer the approved alternative inquiry route. It should not require the guest to name their assistive technology or disclose a disability before receiving help. Send the reproducible issue to the maintainer and keep the operational request with the events team. Those are related but separate tasks: one fixes the website, while the other helps the guest make the inquiry they were trying to complete.

Sample wording to approve

“Please tell us which page or task was difficult to use and how you would prefer a response. You do not need to share medical details. Staff can discuss an alternative way to make your inquiry.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need page or task, barrier described, preferred response, approved alternative, and feedback owner. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The feedback route itself is reachable. The guest is not asked for a diagnosis. The issue reaches a person who can coordinate a correction. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides