Visual feedback
Visual feedback is feedback that arrives with an annotated screenshot of the page attached, so the report shows the problem instead of describing it.
On a documentation or marketing site, a text-only report reads "the install page is confusing" and the person who has to fix it starts by guessing which paragraph. Visual feedback removes that step. The reader marks the sentence, the button, or the broken layout on a capture of the page they were reading, and the fixer opens the report already knowing where to look.
The capture also carries context nobody types voluntarily: the page URL, the viewport size, the browser and operating system, and often the state the page was in. That is the difference between a report a developer can reproduce and a report that needs two rounds of follow-up before work can start.
Visual feedback does not replace a rating or a comment box. It is the escalation path for reports where the location is the point. Across the 200+ documentation sites running PushFeedback, roughly 6 percent of submissions include a screenshot, and those are the ones that reach a developer without a follow-up question.
Frequently asked questions
What is the difference between visual feedback and a feedback form?
A form collects words. Visual feedback collects words plus an annotated image of the page and the technical context of the session, so the recipient can see what the reporter saw without asking.
Do readers actually use screenshot capture?
A minority do. About 6 percent of submissions across the documentation sites we run include a screenshot. The value is not volume: annotated reports are the ones that need no follow-up round.
Is visual feedback only for bug reports?
No. Design reviews, content reviews, and QA passes use the same capture. Anywhere a comment refers to a specific spot on a page, an annotated screenshot removes the ambiguity.