The checks are warnings only. Nothing they find stops a campaign from sending.
Check an email while you edit
1
Open the Accessibility panel
In the email builder, open the Styles tab of the right-hand panel. Accessibility sits under Quick check. For a template written in HTML or MJML, open Accessibility under the code editor instead.
2
Read the score and the issues
The panel shows a score out of 100 and separate scores for Accessibility, Dark mode and Readability. Issues are grouped into Errors, Warnings and Suggestions. Each one names the WCAG criterion it tests, or says Beyond WCAG. The panel checks again a moment after each change. Click Check again to re-run it straight away.
3
Jump to the block
Click an issue to select the block it comes from. This works when the issue can be matched to a block by its image, its link or its text.
4
Apply a one-click fix
Three issues have a fix button:
- Set the language marks hand-written HTML with the workspace’s default language (or the language you are translating into), so screen readers use the right voice. Emails built from blocks get their language automatically (see below), so you rarely see this one there; a language you set before still wins.
- Add the dark-mode metas adds the
color-schemeandsupported-color-schemestags to hand-written HTML. Emails built from blocks always have them. - Mark layout tables adds
role="presentation"to tables used for layout.
What is checked
Beyond WCAG, for dark mode and readability:
- Dark-mode metas missing: no
color-scheme/supported-color-schemestags. - No dark-mode styles: light backgrounds are hard-coded but there are no
prefers-color-scheme: darkrules. - Fails under full or partial colour invert: a text and background pair that passes in light mode but fails when a mail app inverts every colour (Gmail on iOS, Outlook for Windows) or only darkens light backgrounds (Gmail on Android, Outlook.com).
- Button without its own background: a button sets its text colour but leaves the background to whatever is behind it.
- Long all-caps text (over about 40 characters) and long lines (over about 90 characters).
The email’s language
Emails built from blocks are marked with their language automatically, so screen readers read them in the right voice: the language of the translation being sent, otherwise your workspace’s default language (Settings → General), otherwise English. Arabic, Hebrew, Persian, Urdu and Yiddish are also marked right-to-left. Emails you write in HTML keep the language you put in them.Before you send
On the campaign plan page, Ready to send shows one accessibility line per email: its score, how many errors and warnings it has, and Open in the editor, which opens the builder at the Accessibility panel. These lines never change whether the campaign is ready.The accessibility report
Viewing the reports, their page and their exports is on the Essential plan and above. Reports are recorded on every plan, so when you upgrade you see the history of campaigns you sent before. The editor panel and the plan-page lines work on every plan.
From an AI assistant
The MCP toolget_accessibility_report returns a campaign’s report scores and counts per rule for an assistant connected to your workspace. It never returns the email’s HTML or text. See MCP server.