Document-viewer UI evidence for your product

Review document previews without losing the page or surrounding task

Review page controls, zoomed states, and returning to the originating record with a harmless document fixture.

  • ✓Zoom hides the page indicator
  • ✓Closing loses the original record
  • ✓An unavailable preview looks unfinished

Make preview interaction findings specific and bounded

Reading controls in context

Show the page indicator and toolbar at the zoom setting that creates the problem.

Return path kept separate

Give lost record-list context its own observable acceptance boundary.

Unavailable states included

Review the approved fallback without suggesting every document can be previewed.

Review the preview inside its surrounding task

A customer opens a synthetic policy document from your application's record list, moves to a later page, and zooms in. The toolbar covers the page number, and closing the preview returns to a different list position. Review reading controls and return context as observable behaviors. Retick reviews screenshots or recordings of your preview; it does not promise to render arbitrary documents or replace the application's document viewer.

Choose an authorized sample document

Use a harmless fixture with distinct page headings and no personal information, signatures, or private metadata. Record opening the preview, navigating pages, zooming, closing, and returning to the original record. Note file type, sample page count, browser, viewport, and build. Capture through the supported browser extension or upload authorized media. Keep local filenames and unrelated files out of any operating-system picker shown during setup.

Separate reading and return defects

An example issue is Preview toolbar obscures the current page indicator at increased zoom. Annotate the overlap with the relevant controls visible. Review Retick's AI candidate findings, correcting mistaken page identities and rejecting claims about missing document content unless the fixture confirms them. Treat the lost list position as a separate finding with its own steps. A cropped page, slow loading feedback, and an unavailable preview may need different evidence.

Example acceptance criteria

At the reported viewport and approved zoom setting, the current page indicator and navigation controls should remain readable and usable without covering essential content. Closing should restore the agreed originating record context. For an unsupported sample type, the application should show its approved unavailable-preview message and any permitted next action. Check navigation and closing directly; a readable captured page does not prove every page can be reached.

Revisit page boundaries and alternate states

Keep opening, zoomed, closed, and unavailable states in a review cycle. Follow up on the first and last pages, a narrow viewport, and reopening the same sample document. Download reviewed findings or create Trello cards from selected individual-media issues. Retick does not validate document fidelity, embedded content handling, access permissions, or viewer security. Those need separate technical checks. The visual review can clarify control placement and task continuity without claiming the document is complete, safe, or correctly rendered in every environment.

Review the reading state and the way back

Capture a safe sample preview and define page controls and return context together.