Guides
Email QA, written down.
Short, practical guides from the workflow SendLint automates. No fluff, no invented statistics, no gated PDFs.
The email QA checklist: every check before you send
Every check a bank-grade email QA pass covers, why each exists, and which ones humans consistently miss.
Read the guide →The email accessibility checklist: WCAG 2.1 AA for HTML email
Which criteria actually apply to email, the checks for structure, text, contrast, images, links and motion, what fails most in real campaigns, and how to test with a screen reader.
Read the guide →How to QA an email against the copy deck, line by line
The shapes a deck arrives in, both directions, per version and per language, the parts everyone skips (subject line, alt text, links, tokens), what counts as different, and what to do when the deck is revised mid-campaign.
Read the guide →Bilingual email QA: how EN/FR campaigns actually go wrong
Language leaks, links that don't switch languages, lost accents, unequal legal copy, and the pass that catches each one.
Read the guide →How to prove the email you sent is the email that was approved
Approval usually lives in a screenshot and a thread. Here's how to bind it to the exact bytes instead, and verify any file against it later.
Read the guide →Pre-send verification in Salesforce Marketing Cloud
What to check in the test send (wrapped links, subject line per version, unsubscribe, dynamic content), then a Script Activity that hashes the approved HTML and stops the automation if a byte changed after sign-off.
Read the guide →How to turn a brand guide PDF into email QA rules
What the guide actually says about email, the rulebook field by field (palette, type, widths, logos, trademarks, links, CTA and copy conventions), two ways to get the rules in, and what fails most.
Read the guide →How to QA personalization tokens and merge tags in email
Fallbacks that never fire, tokens that push the subject past the cut, values that differ per version, tokens the deck defines and the email never fills, and the pass that checks each one.
Read the guide →An email approval workflow that holds up: rounds, variance log, sign-off
Who checks what in each round, how the developer gets a numbered fix list instead of a thread, what the client actually signs off on, and the record that proves it afterwards.
Read the guide →QA for pharma approved email: the build against the approved rendition
What the regulatory PDF carries (subject options, Upon click links, ALT TEXT callouts), where builds drift from it, and a pass that checks every element against the approved rendition.
Read the guide →Comparisons
A Litmus alternative for email QA: verify the email, not just preview it
Rendering previews and verification are different jobs. An honest side-by-side of which tool fits which one, with both price lists.
Read the comparison →An Email on Acid alternative for email QA: verify the email, not just preview it
Email on Acid is now Mailgun Inspect. Where it is strong, what a preview can't tell you, both price lists, and which to pick.
Read the comparison →Tools
Tools for copy decks, links, images, alt text and inbox previews
Prepare and compare decks, follow every link, check every image, write alt text, and see where inboxes cut the subject line.
See the tools →Using SendLint
SendLint for agencies
One rulebook per client, rounds that hand the developer a variance log, free Reviewer seats, and a client sign-off with a public certificate.
See how agencies use SendLint →Help centre: every setting, explained
Brand rules and check policies, copy-deck import, creative compare, real Outlook rendering, SendLint Approved certificates and the verification API — the product documentation, searchable.
Open the help centre →