AI VISUAL QA
How to turn website feedback into a useful AI handoff
A useful review tells the next person where the issue is, what should change and what evidence supports it. This workflow keeps those details together, from a live website to the files you choose to share.
1. Start on the page you want to review
Open the AI Visual QA icon on a supported website. Start a new review or continue one from History, then allow access to that website when Chrome asks. Access lets the notes return when you navigate or reload that site.
Chrome internal pages, the Chrome Web Store and restricted PDF viewers are unavailable. Capture is limited to the current viewport. If Chrome needs fresh capture authorization on a new or restored tab, click the extension icon again.
2. Write one actionable note per issue
Select the target element and describe the specific change. For example: ‘The primary action wraps to two lines at this width. Keep its label readable and prevent it from overlapping the adjacent control.’ Add an expected result, issue type or priority when it helps the developer decide what to do.
Save the note to create its numbered marker and screenshot evidence. Add a reference image when a visual example is more useful than extra prose. Avoid including account details, private conversations or unrelated content.
3. Review the list and its evidence
Open the review panel to search, filter, edit or resolve notes. Keep related pages in the same review. If the page has changed and a target cannot be located reliably, check that issue again before exporting.
Viewport screenshots and reference images may contain private text beyond the default masks. Inspect the evidence. Recognized secret fields and visible form fields are masked by default, but images are not automatically OCR-redacted.
4. Choose the smallest useful export
Use Simple for a prompt.md file and relevant images. This is the shortest handoff for a developer or AI coding tool. Use Detailed when someone also needs report.html, the offline human-readable review, or optional structured context.
The export preview shows the exact prompt, images and download size. Optimized images can reduce size; original quality remains available. Duplicate images are stored once, and authored notes are preserved. HTML, Markdown, JSON and image-only ZIP formats serve other workflows.
5. Share with the right context
Attach prompt.md and its images to the coding tool or project workspace you choose. Keep the filenames so numbered issues still refer to the correct image. Include the relevant repository or working branch separately if the tool needs source access; a screenshot export does not contain your codebase.
For a human reviewer, open report.html or share the full detailed package with its images directory intact. AI Visual QA does not send the package to any AI service. Sharing outside the extension is your decision and follows that service's privacy practices.
6. Keep the next pass clear
Return to the review, update the note after checking the fix and mark it resolved when appropriate. Duplicate the review when you need a separate follow-up. History keeps local reviews available after a restart.
Delete finished reviews in History to remove their saved records and images. Settings can clear all local review data and preferences. Chrome manages granted site permissions separately.