Rules
Part of A field guide to email design that survives every inbox
Email design checklist: what to verify before you send
Email design checklist for task, structure, content, images, typography, color, actions, identity, resilience, data, localization, testing, and privacy review.
What to take away
- Block release when material meaning, action, identity, accessibility, destination, fallback, or rollback remains unknown.
- Mark each item pass, fail, unknown, or not applicable with evidence, owner, correction, and review date.
- Repeat the checklist on the final rendered message after content, code, data, template, client, or destination changes.
An email design checklist should confirm that recipients can recognize, understand, and operate a message across real conditions. Mark each item pass, fail, unknown, or not applicable. Record evidence, test client, device, record, owner, correction, accepted risk, and review date. The same gate applies at every journey stage a message supports — welcome, onboarding, receipts, alerts, and win-back — because each stage carries its own risk.
Task and structure
The W3C Headings tutorial explains how heading ranks communicate organization and support navigation. Verify that the email's marked-up order matches its visual order and remains meaningful when styles, columns, and images are removed. Where a message must meet a formal standard, cite the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and, for US federal agencies, Section 508 of the Rehabilitation Act.
Task and structure checks
- Sender, audience, message type, action defined
- Visual and semantic reading order agree
- One main topic with descriptive subheadings
- Marked-up order matches visual order
- Meaningful hierarchy without relying on size
Content and images
W3C's image alternative tips recommend choosing alternatives from purpose and context, prioritizing essential information, and keeping descriptions concise. Review each image in the exact message because the same asset can be informative, functional, redundant, or decorative in different uses. Published email design examples show how receipts, alerts, and onboarding messages handle the same image and alt text decisions.
- Sender, purpose, price, deadline, account information, security instructions, action, help, and terms remain available as live text. Why it matters: live text survives image blocking, translation, and screen readers.
- Meaningful images have contextual alt text; decorative images avoid noise; complex visuals include accessible conclusions and data. Why it matters: alt text and data summaries carry meaning when images fail or assistive tech reads them.
- Image dimensions, compression, hosting, first frames, dark mode, blocked images, slow networks, and static fallbacks are tested. Why it matters: rendering conditions change how recipients see and trust the message.
Typography, color, and action
- Type size, line height, line length, fallback fonts, sentence case, spacing, zoom, and text expansion support reading. Why it matters: readable type keeps the message usable for low vision and translated content.
- Text, links, controls, logos, boundaries, and states have adequate contrast; color is never the only signal. Why it matters: contrast and non-color cues let people with color vision deficiency operate the message.
- Link and button text names the action or destination, targets are usable, consequences are clear, and text fallbacks work. Why it matters: clear action text prevents accidental clicks and support calls.
Identity and resilience
- Display name, address, logo, subject, preview, style, reply route, and destination accurately represent the sender and message. Why it matters: consistent identity builds trust and reduces phishing reports.
- The layout remains useful when columns stack, styles are stripped, images fail, fonts change, or dark mode transforms colors. Why it matters: recipients open messages in many clients and conditions.
- HTML and plain-text versions communicate the same essential information, terms, actions, help, and preferences. Why it matters: plain text is the fallback when HTML is blocked or stripped.
Data and localization
- Personal fields have sources, freshness, privacy limits, sensitive exclusions, length allowances, and neutral fallbacks. Why it matters: wrong or stale personal data damages trust and may breach privacy rules such as the GDPR and the CCPA/CPRA.
- Missing, stale, shared, malformed, conflicting, wrong-market, translated, right-to-left, and deleted records behave safely. Why it matters: bad records can send the wrong offer or expose another person's data.
- Dates, numbers, currencies, addresses, fonts, links, offers, and terms match the recipient market. Why it matters: mismatched locale details confuse recipients and can invalidate an offer.
Testing and operations
- Client, device, operating system, theme, zoom, screen reader, language, record, network, and destination coverage follows evidence and consequence, and the matrix names what it covers: Gmail, Outlook, Apple Mail, and Yahoo Mail; light and dark themes; and screen readers such as NVDA, JAWS, and VoiceOver. Why it matters: coverage decisions should match the risk of the message and the share of subscribers each client and setting represents.
- Automated checks are supplemented by keyboard, screen-reader, comprehension, link, reply, unsubscribe, and full task tests. Why it matters: automation misses real user barriers that manual tests catch.
- The approved version, coverage, known gaps, exposure, results, incidents, pause authority, rollback, and module retirement are documented. Why it matters: documentation lets a team pause, fix, and learn without guessing.
Review the checklist after a new client, template, module, sender, message type, market, language, data source, destination, provider rule, or incident. Tie the result back to the journey stage the message protects — welcome, onboarding, receipt, alert, or win-back — and record task-success and client-coverage results before comparing them with email design benchmarks.
Checklist decision record
| Status | Meaning | Action |
|---|---|---|
| Pass | Current evidence supports item | Record and review |
| Fail | Design does not meet item | Correct before release |
| Unknown | Evidence is missing | Assign investigation |
| N/A | Outside verified scope | Record rationale |
Example: alt text on a receipt image. Pass when the alt text names the line item and amount, with a screenshot and test client recorded. Fail when the alt text is missing or generic, with the correction assigned to the template owner.
Privacy and acquisition review
The W3C Privacy Principles statement gives web-system designers shared privacy concepts and warns against shifting privacy work to individuals. The CISA software acquisition fact sheet covers development practice, supply-chain exposure, deployment, and vulnerability management. Apply both to the email design checklist, then name the governing law for each list and market — CAN-SPAM for commercial email in the United States, and the GDPR or the CCPA/CPRA where recipients or their data fall under them — and record the notice and consent each one requires.
Common questions
Who should own the checklist?
One design owner should coordinate content, brand, accessibility, development, data, delivery, security, service, and destination owners without replacing their decisions.
Is one screenshot enough for approval?
No. Include semantic, keyboard, assistive-technology, content, link, data, localization, client, theme, device, plain-text, and destination evidence according to risk.
