> For the complete documentation index, see [llms.txt](https://docs.beefree.io/beefree-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/beefree-sdk/qa-tools/qa-tools-overview.md).

# QA Tools overview

Beefree SDK's QA tools help your end users catch content problems and confirm their designs meet quality, accessibility, and brand standards before they ship. This page is your starting point for every QA feature in the SDK.

Use the sections below to find the right tool for what you need, or jump straight to a specific feature.

Beefree SDK offers two QA tools. Each adds a shield icon to the builder that opens a dedicated results panel when clicked. Quality Check flags whether designs **function** like they should, while Brand Check flags whether they **look** like they should.

## Quality Check: built-in content quality and accessibility

[Quality Check](https://docs.beefree.io/beefree-sdk/qa-tools/quality-check.md) evaluates email and page designs against quality and accessibility best practices. It flags things like missing alt text, insufficient color contrast, missing links, and oversized images or HTML.

Quality Check is available on all paid plans (Essentials and above) at no extra cost. Advanced customization, including custom thresholds and check selection, requires a Superpowers or Enterprise plan.

[Learn more about Quality Check](https://docs.beefree.io/beefree-sdk/qa-tools/quality-check.md)

## Brand Check: your own brand rules

Quality Check applies a single, fixed set of rules to every design. [Brand Check](https://docs.beefree.io/beefree-sdk/qa-tools/brand-check.md) lets your users define their own design rules as presets: single values or combinations (like background and text color together) covering color, typography, spacing, buttons, links, and headings. Every email is checked against those presets after creation. Anything off-brand is flagged along with a suggested fix, and your users decide whether to apply it with a single click.&#x20;

Brand Check is available for email designs on Superpowers and Enterprise plans.

[Learn more about Brand Check](https://docs.beefree.io/beefree-sdk/qa-tools/quality-check.md)

## Build your own

Brand Check and Quality Check are ready to use: activate them with a single click and get a built-in UI, with no implementation effort and no additional usage cost. Both tools are backed by the [Check CSAPI endpoint](https://docs.beefree.io/beefree-sdk/apis/content-services-api/check.md). If you'd rather build a fully custom QA experience, you can build it from scratch on top of the Check CSAPI endpoint and develop your own UI, additional CSAPI usage costs will apply.

<br>

<br>

<br>

\[Learn more about Quality Check]\(/beefree-sdk/qa-tools/quality-check)

\ <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.beefree.io/beefree-sdk/qa-tools/qa-tools-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
