> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brew.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Accessibility Audits

> Run a WCAG 2.1 audit on any design and get a score, a summary, and the specific issues to fix. Brew can apply the fixes for you.

<Note>
  **July 2026** · Available on all plans.
</Note>

## What Shipped

Brew can now audit any email design against WCAG 2.1 before it goes out. The audit checks the rendered HTML: color contrast, image alt text, link text, heading structure, font size, and language. Back comes a **score** from 0 to 100, a plain-English **summary**, and the specific **issues**, each tied to its WCAG criterion.

It runs everywhere Brew does: in the app, over [MCP](/api-reference/mcp/overview), and on the [Public API](/api-reference/api/api-introduction). An audit costs a fixed **5 credits** and is charged only when it completes.

<Frame>
  <img src="https://0edx89zhjrasqnjf.public.blob.vercel-storage.com/docs/accessibility_audit.webp" alt="Brew running an accessibility audit on an email, returning a 91/100 score with contrast and link issues, then applying the fixes" width="3146" height="2160" />
</Frame>

## In the Brew UI

<Steps>
  <Step title="Add the email to chat">
    Open the email you want to check and click **Add to chat**, so the audit
    runs against that design.
  </Step>

  <Step title="Ask for an audit">
    Prompt the chat:

    > *"Can you do an accessibility audit of this email?"*

    Brew confirms the 5-credit cost first, then runs the audit and replies
    with the score and each issue it found, like a text and background
    pairing below the 4.5:1 contrast minimum, or links that rely on color
    alone.
  </Step>

  <Step title="Let Brew apply the fixes">
    Say yes when Brew offers to fix what it found. It darkens low-contrast
    text, underlines links, and fills in the other flagged issues, then you
    can re-run the audit to verify the new score.
  </Step>
</Steps>

## From MCP

If Brew is [connected to your AI client](/api-reference/mcp/quickstart), audits
run from any chat. Reference the email and ask:

> *"Audit the welcome email for accessibility."*

The agent calls `audit_email_accessibility` and replies with the score,
summary, and issue list, and it can apply the fixes in the same conversation.

## From the API

The same audit is available at `POST /v1/emails/{emailId}/accessibility-audit`
and as `brew.emails.auditAccessibility(...)` in the TypeScript SDK. The call
is value-aligned: if the audit can't complete you get a retryable `503` and
are not billed. See [Credits](/api-reference/api/credits) for how metering
works.

## Related

* [The Interface](/create-emails/the-interface)
* [Prompt Guide](/create-emails/prompt-guide)
* [API Changelog](/changelog/api)