Annotation cards

Last updated
February 5, 2026

Annotation cards show the details of visual issues directly on the canvas while you’re reviewing probe results.

They appear when you select a marker and explain what differs between the Figma design and the live webpage, without requiring you to leave the area you’re inspecting.

(Visual reference: Annotation card shown on the canvas after selecting a marker.)

What an annotation card shows

An annotation card presents a detected issue in a compact format. It typically includes:

  • a short description of the visual difference
  • a brief explanation of the difference
  • a comparison between the expected (design) and actual (webpage) values

This information is shown alongside the affected element on the canvas.

(Visual reference: Annotation cards showing different issue categories with expected → actual comparisons.)

Annotation cards and issue variants

Annotation cards adapt based on the type of issue being reviewed.

When a marker represents a single issue, the annotation card focuses on that individual difference.

When multiple issues are detected, annotation cards can represent different types of groups, for example:

  • multiple issues on the same element
  • multiple different issues within a segment

(Visual reference: Grouped annotation cards showing different grouping patterns.)

Grouping allows related differences to be reviewed together without cluttering the canvas with multiple overlapping cards.

Annotation card footer actions

The footer of an annotation card contains controls that support reviewing and navigating issues.

Depending on the issue and context, the footer may include:

  • Previous / Next
    Lets you step through issues sequentially without clicking markers on the canvas.
  • Thumbs up / Thumbs down
    Allows you to quickly indicate whether the detected issue is valid or not. This helps during review without turning the card into a task or comment system.

These actions are designed to support fast review workflows while keeping the card focused on visual inspection.

(Visual reference: Annotation card footer showing navigation and feedback controls.)

How annotation cards behave during review

Annotation cards are integrated with the canvas:

  • selecting a marker opens the annotation card near the affected area
  • the canvas adjusts to keep the relevant element visible
  • navigating between issues updates the active annotation card

Annotation cards behave consistently across view modes, even as the visual presentation of the comparison changes.

What annotation cards are not

Annotation cards are designed for visual review only.

They do not:

  • assign ownership or responsibility
  • track resolution status
  • replace tickets, comments, or task management tools

Their role is to surface visual differences so teams can decide what action—if any—is needed.

Related concepts

Close Modal