# Reviews

A review is the sign-off surface on a [visual pull request](/cloud/visual-pull-request/overview).
Reviewers inspect the changed scenarios in a browser, comment on them, and approve or request changes.
The decision is reported back to your Git provider as a commit status.
A pull request collects one review per reviewer.

<Image theme="light" src="/assets/cloud/review.light.png" />
<Image theme="dark" src="/assets/cloud/review.dark.png" />

## What a Review Shows

A review compares the `base` and the `head` build and reports three kinds of findings:

| Finding | Compares |
| --- | --- |
| [**Visual changes**](/cloud/visual-tests/overview) | The snapshots of a scenario |
| [**Accessibility regressions**](/cloud/accessibility/regressions) | The semantics trees of a scenario, such as a dropped label or a changed role |
| [**Accessibility violations**](/cloud/accessibility/violations) | Broken [guidelines](/testing/accessibility), split into introduced, pre-existing, and resolved |

## Workflow

<Info>
  **Prerequisite:** Widgetbook Cloud is set up for
  [GitHub](/cloud/guides/github/upload),
  [GitLab](/cloud/guides/gitlab/upload),
  [Azure DevOps](/cloud/guides/azure/upload), or
  [Bitbucket](/cloud/guides/bitbucket/upload).
</Info>

1. Open a pull request in your Git provider.
2. Widgetbook Cloud creates the visual pull request automatically and posts its URL as a commit status.
3. Reviewers inspect the changed scenarios and [submit a decision](/cloud/reviews/submit).
4. The decision updates the commit status.
5. Requested changes block the merge until they are addressed, which can be disabled in the project settings.

<YouTube id="CalXXyThDi4" />

## Case Study: 1KOMMA5°

Before Widgetbook Cloud, designers were not part of the review at all.

<Card
  icon="bolt"
  title="How 1KOMMA5º builds a custom design system and maintainable Flutter apps with Widgetbook"
  href="https://www.widgetbook.io/blog/1komma5%C2%BA-custom-flutter-design-system-with-widgetbook"
>
  > As developers, we were not sure if we fully met the design requirements.
  > Since designers were not involved in our review processes, it was hard to get their feedback.
  > So, we had misalignment between design and code, and wrong implementations could be shipped to our customers.
  >
  > Widgetbook provides us with a process to build and maintain our design system, prevent visual bugs, and align design and development.
  > We notice that our designers and developers save 20% of their time through this process.
  >
  > Anton Borries, Senior Software Engineer at 1KOMMA5º and Google Developer Expert for Flutter & Dart
</Card>

Since adopting Widgetbook Cloud, 1KOMMA5° has shipped **0 visual bugs** to production across 3 Flutter apps.

## Next

- [Submit a review](/cloud/reviews/submit): inspect a diff, comment, and publish a decision.
- [Decide when to review](/cloud/reviews/when-to-review): three policies for pulling a designer in.
- [Figma Reviews](/cloud/reviews/figma): link a story to its Figma component.
- [Notifications](/cloud/reviews/notifications/slack): email and Slack alerts so reviews do not sit unnoticed.
- [For Designers](/cloud/for-designers/overview): the guide for reviewers who do not read Dart.