Skip to content
Kaarne Superstore⌕
AI & Digital Tools

Make Website Feedback Accessible to Different Reviewers

The same review question can travel through text, a call or a guided task. Someone still needs to carry the finding into the project record.

Three reviewers follow writing, telephone and footprint routes toward one shared paper page.

A reviewer understands the service better than anyone else on the project, but cannot comfortably use your chosen comment interface. If participation requires dragging a pin onto a screenshot, their knowledge may never reach the review. Start with the question they need to answer and offer a workable way to answer it.

Ask about the review route before the session

For this fictional example, a community organisation is reviewing its service enquiry page. One contributor prefers written questions, another uses keyboard navigation and a third would rather discuss the wording in a short call. Do not infer everyone’s needs from a job title, age or disability label. Ask what arrangement would help each person contribute to the assigned task.

A simple invitation can say: “We need your view on whether these enquiry instructions describe the service accurately. You can send written comments naming the section, discuss them with me in a scheduled call, or work through the page with a facilitator. Tell me if another arrangement is needed.” Offer only routes you can actually support, with an owner for transferring the findings.

Keep the question consistent across channels

Prepare one short review question and enough context to understand it outside the visual interface. For example: “On Project Enquiry, does the paragraph under ‘Before you contact us’ explain what information a new customer should prepare?” Include the relevant wording in a readable text format where appropriate, alongside the page reference and review version.

The task should not become harder for the person using the alternative route. If the visual interface shows surrounding instructions that affect the answer, supply that context too. Conversely, do not bury the person in an export of the whole project board when they need one paragraph. Check whether the alternative preserves the substance of the same review, rather than merely providing a place to send a message.

Use a facilitator without replacing the reviewer

In a call, ask the question, allow the reviewer time to answer and read back the observation. Establish whether they want a particular statement captured in their words. Separate what they said from your interpretation and proposed treatment. A facilitator can help locate the element without becoming the person who decides what the contributor ought to have meant.

An illustrative transfer note might say: “Reviewer reports that ‘project details’ does not explain whether a plan is required. They expect the instruction to say what is optional. Facilitator located the wording in the opening enquiry paragraph. The proposed wording remains to be agreed.” The note preserves authorship and uncertainty without requiring a visual pin.

Check the feedback method itself

Before inviting several people, attempt the actual supported route with suitable authorised access. Can a person reach the page, understand the assignment, send a finding and recognise what happened afterwards? Check the alternative route as well: who receives the telephone note, and how will the reviewer know it was captured?

If you are examining technical accessibility, use an appropriate evaluation method and expertise. W3C’s user-evaluation guidance explains why experience with disabled users complements evaluation against standards. A single contributor’s successful review does not establish that the method works for all disabled people. Record whose experience and which conditions your observations concern.

Separate participation support from a conformance conclusion

Making a call available is a practical participation option. It does not prove that the website or comment interface conforms to an accessibility standard. W3C’s preliminary checks explicitly cover only a limited set of issues; a page can appear to pass those checks and still contain significant barriers. Report that limit when sharing findings.

Likewise, an expert assessment does not remove the value of hearing from the people who will use the actual service. Agree the project’s accessibility evaluation work separately from a client’s factual content review. Give each activity its own question, scope and record, rather than calling every helpful conversation an accessibility audit.

Return the captured finding for confirmation

After transferring feedback, send a concise summary through the contributor’s workable channel. Name the issue, the relevant section and the next action. Invite correction if the summary changes their meaning. Participation is complete enough to continue when their knowledge reaches the decision process in a form they can recognise, with its limits intact.

For evaluation planning, consult W3C guidance on involving users and the scope of W3C preliminary checks.

Ask reviewers which way of describing an issue works for them. A visual comment can be one useful route, while a clear alternative keeps participation from depending on a single interface.

Continue with Your Client Does Not Need to Learn Your Entire Tool Stack and The First Website Review Email Should Explain the Job.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.