What ArbiterQA can check

A leaked {{first_name}} or [COMPANY NAME] tells every recipient the send was a mistake; subject line, preheader and body must contain no unfilled merge tags or placeholder text.

Marketing email without a working unsubscribe is a legal exposure and a spam-complaint magnet; the message must offer one — a List-Unsubscribe header or a visible link — and that link must not write the recipient's email address into its URL.

Commercial email without the sender's physical postal address breaks CAN-SPAM and CASL on every send; the message must carry a real mailing address (an ambiguous match is recorded, never failed).

A dead link in a sent email cannot be recalled — the traffic you paid for lands on an error page; every link must be a well-formed URL that resolves, follows a sane redirect chain and lands on a destination you approve (bot-walled links are reported as unverifiable, never failed).

Most inboxes clip a long subject mid-thought; the subject line must stay within your character limit.

The preview snippet beside the subject line is the second thing a reader judges you by; it must be intentional — no "view in browser" boilerplate, no leaked merge tokens, required content within the visible window and nothing in the source that garbles the preview.

With images blocked, an image without usable alternative text disappears along with whatever it said; every image needs real alt text (or an empty alt when decorative), and an image-only link must keep an accessible name.

Broken tracking makes a campaign invisible in analytics after the money is spent; every link's tracking must be intact — no unresolved merge tags, empty or misspelled UTM values, duplicate parameters, ad-platform click IDs or raw email addresses — and, when you configure tracked domains, the parameters you require must be present and survive redirects.

Gmail cuts off a message whose HTML source runs past roughly 102 KB, hiding the footer, the unsubscribe link and the tracking pixel behind "View entire message"; the HTML body must stay under your byte limit.

Marketing email without a working unsubscribe is a legal exposure and a spam-complaint magnet; the message must offer one — a List-Unsubscribe header or a visible link — and that link must not write the recipient's email address into its URL.

Commercial email without the sender's physical postal address breaks CAN-SPAM and CASL on every send; the message must carry a real mailing address (an ambiguous match is recorded, never failed).

A footer missing its address or unsubscribe link is a compliance exposure on every send; the footer must carry every element you require (by default, a physical address and an unsubscribe link).

Without a plain-text part, text-only clients, some accessibility tools and some spam filters see nothing; an HTML email must ship a plain-text alternative the sender wrote.

A leaked {{first_name}} or [COMPANY NAME] tells every recipient the send was a mistake; subject line, preheader and body must contain no unfilled merge tags or placeholder text.

A dead link in a sent email cannot be recalled — the traffic you paid for lands on an error page; every link must be a well-formed URL that resolves, follows a sane redirect chain and lands on a destination you approve (bot-walled links are reported as unverifiable, never failed).

A call-to-action nobody can see is a campaign with no click; at least one button must be visible and fully rendered at every selected viewport.

A layout that collapses at one width is the version some of your list actually sees; the email must hold its layout at every selected viewport.

An image stretched past its own pixels looks soft or blocky on the high-resolution screens most email is read on; every image must load and be displayed at a size its file can actually fill.

A dead image is a broken box in the inbox and an image served from the wrong host is a brand or security exposure; every image source must resolve to a real image over a secure path on a host you allow.

With images blocked, an image without usable alternative text disappears along with whatever it said; every image needs real alt text (or an empty alt when decorative), and an image-only link must keep an accessible name.

The preview snippet beside the subject line is the second thing a reader judges you by; it must be intentional — no "view in browser" boilerplate, no leaked merge tokens, required content within the visible window and nothing in the source that garbles the preview.

Most inboxes clip a long subject mid-thought; the subject line must stay within your character limit.

A reader who cannot see who sent the email treats it as junk; the brand logo must be present and clearly visible in the header at every selected viewport.

An image cropped mid-headline or mid-face says something you did not intend; no image may be clipped, cropped or scaled in a way that damages its message in any rendered client.

Broken tracking makes a campaign invisible in analytics after the money is spent; every link's tracking must be intact — no unresolved merge tags, empty or misspelled UTM values, duplicate parameters, ad-platform click IDs or raw email addresses — and, when you configure tracked domains, the parameters you require must be present and survive redirects.

Gmail cuts off a message whose HTML source runs past roughly 102 KB, hiding the footer, the unsubscribe link and the tracking pixel behind "View entire message"; the HTML body must stay under your byte limit.

A leaked {{first_name}} or [COMPANY NAME] tells every recipient the send was a mistake; subject line, preheader and body must contain no unfilled merge tags or placeholder text.

A dead link in a sent email cannot be recalled — the traffic you paid for lands on an error page; every link must be a well-formed URL that resolves, follows a sane redirect chain and lands on a destination you approve (bot-walled links are reported as unverifiable, never failed).

Without a plain-text part, text-only clients, some accessibility tools and some spam filters see nothing; an HTML email must ship a plain-text alternative the sender wrote.

With images blocked, an image without usable alternative text disappears along with whatever it said; every image needs real alt text (or an empty alt when decorative), and an image-only link must keep an accessible name.

An image stretched past its own pixels looks soft or blocky on the high-resolution screens most email is read on; every image must load and be displayed at a size its file can actually fill.

A dead image is a broken box in the inbox and an image served from the wrong host is a brand or security exposure; every image source must resolve to a real image over a secure path on a host you allow.

A layout that collapses at one width is the version some of your list actually sees; the email must hold its layout at every selected viewport.

An image cropped mid-headline or mid-face says something you did not intend; no image may be clipped, cropped or scaled in a way that damages its message in any rendered client.

Most inboxes clip a long subject mid-thought; the subject line must stay within your character limit.

The preview snippet beside the subject line is the second thing a reader judges you by; it must be intentional — no "view in browser" boilerplate, no leaked merge tokens, required content within the visible window and nothing in the source that garbles the preview.

Commercial email without the sender's physical postal address breaks CAN-SPAM and CASL on every send; the message must carry a real mailing address (an ambiguous match is recorded, never failed).

A reader who cannot see who sent the email treats it as junk; the brand logo must be present and clearly visible in the header at every selected viewport.

Gmail cuts off a message whose HTML source runs past roughly 102 KB, hiding the footer, the unsubscribe link and the tracking pixel behind "View entire message"; the HTML body must stay under your byte limit.

A leaked {{first_name}} or [COMPANY NAME] tells every recipient the send was a mistake; subject line, preheader and body must contain no unfilled merge tags or placeholder text.

A dead link in a sent email cannot be recalled — the traffic you paid for lands on an error page; every link must be a well-formed URL that resolves, follows a sane redirect chain and lands on a destination you approve (bot-walled links are reported as unverifiable, never failed).

Without a plain-text part, text-only clients, some accessibility tools and some spam filters see nothing; an HTML email must ship a plain-text alternative the sender wrote.

With images blocked, an image without usable alternative text disappears along with whatever it said; every image needs real alt text (or an empty alt when decorative), and an image-only link must keep an accessible name.

An image stretched past its own pixels looks soft or blocky on the high-resolution screens most email is read on; every image must load and be displayed at a size its file can actually fill.

A dead image is a broken box in the inbox and an image served from the wrong host is a brand or security exposure; every image source must resolve to a real image over a secure path on a host you allow.

A layout that collapses at one width is the version some of your list actually sees; the email must hold its layout at every selected viewport.

An image cropped mid-headline or mid-face says something you did not intend; no image may be clipped, cropped or scaled in a way that damages its message in any rendered client.

Most inboxes clip a long subject mid-thought; the subject line must stay within your character limit.

The preview snippet beside the subject line is the second thing a reader judges you by; it must be intentional — no "view in browser" boilerplate, no leaked merge tokens, required content within the visible window and nothing in the source that garbles the preview.

Commercial email without the sender's physical postal address breaks CAN-SPAM and CASL on every send; the message must carry a real mailing address (an ambiguous match is recorded, never failed).

A reader who cannot see who sent the email treats it as junk; the brand logo must be present and clearly visible in the header at every selected viewport.

Gmail cuts off a message whose HTML source runs past roughly 102 KB, hiding the footer, the unsubscribe link and the tracking pixel behind "View entire message"; the HTML body must stay under your byte limit.

An email a screen reader cannot navigate or a low-vision reader cannot make out is a message part of your list never receives; this checks the accessibility defects decidable from the source — language, table semantics, colour contrast, link names, tap targets, animation — and abstains rather than guesses on the rest.

Gmail writes its own AI summary above your message and a growing share of recipients read that instead of the email; the summary must carry the action you are asking for, the deadline you set and the sender you are, and must not state anything your email does not say.

Mail sent from a domain you do not own reads as spoofing to filters and recipients alike; the From address must belong to one of your approved sender domains.

A hero that fails to load leaves the reader a blank box where the offer should be; the primary banner image must load and render fully.

A subject line that drifts from what was approved is the most visible mistake a send can make; the received subject must match your approved subjects, contain the phrases you require and avoid the patterns you prohibit (skipped until you configure it).

An off-brand font stack is the fastest way an email stops looking like it came from you; every font stack must match an approved brand stack, webfonts must carry an Outlook fallback, and weights and sizes must use vocabulary mail clients honour (skipped until you configure it).

Knowing exactly which tracking parameters each link carries is how you spot the one campaign that will not attribute; this lists every link's query parameters with the UTM keys called out, and always passes — it reports, it does not judge.

When two people tag the same campaign differently, one campaign reports as several and nobody can say what it earned; every tagged link must follow the SchemaFirst UTM Standard — source, medium and campaign all present, the campaign a lowercase underscore slug that does not repeat the source or channel, and every value lowercase with no spaces — on top of the tracking integrity rules for merge tags, click IDs, personal data and dropped parameters.

Outlook shows images blocked to every recipient who has not added you to Safe Senders; the email must still convey its offer and give the reader a way to act with images off (requires the alt-text validation, which covers the other half of the same question).

Body text set too small is unreadable and too large breaks the layout; visible body text on the page must stay within your minimum and maximum pixel sizes.

A missing or mistreated logo undermines every other brand signal on the page; the logo must be present and follow your brand guidelines.

A footer missing a required element is a compliance gap on every page; the page footer must include the brand elements you require.

On a page that should not change, any change is a defect until a human says otherwise; this compares the capture to the previous one at the same URL and viewport and fails on a meaningful difference (the first run always passes).

Lorem ipsum on a live page tells every visitor it shipped unfinished; no placeholder or prohibited phrase may appear in the visible text.

A page that paints its main content late loses visitors before it loads; the largest contentful paint must land within your budget (2.5 s by default), and every other timing and weight metric is reported for context, not judged.

A screen reader announces an image with no text alternative as a file name or not at all, so whatever it showed is lost; every meaningful image must carry alternative text and every decorative one must be marked as such.

Endless carousels, looping backgrounds and spinning graphics make some readers dizzy or ill and pull everyone’s eye away from the words; motion lasting more than five seconds must stop when the reader’s device asks for reduced motion.

A keyboard user who cannot see where focus is cannot tell which link Enter will follow; every element must show a visible change when it receives keyboard focus.

A screen reader announces an unlabelled field as just "edit text", so the visitor cannot tell what to type and abandons the form; every input, select and toggle must carry a programmatic label.

People who cannot use a mouse — and every screen-reader user — move through a page with the keyboard; a control it cannot reach or a spot it cannot leave stops them dead, so every control must be reachable with Tab and focus must never get stuck.

Without a declared language a screen reader reads the page in the listener’s own language and mispronounces every word; the page and any passage in another language must say which language they are in.

A screen-reader user skimming a list of links hears "link" or a row of identical "learn more"s and cannot tell them apart; every link must have a name, and a generic one needs the words around it to say where it goes.

A text box whose outline is a faint grey on white is invisible to people with low vision, who cannot find where to type; the border or fill that shows where a field is must reach a 3:1 contrast with what surrounds it.

A link or button too small to hit gets mis-tapped by anyone with a tremor and by most people on a phone; every target must be at least 24 by 24 pixels or have that much clear space around it.

Text too close in colour to its background is unreadable for people with low vision and for everyone in bright light; normal text must reach a 4.5:1 contrast ratio and large text 3:1.

A video with no captions says nothing to a viewer who is deaf, hard of hearing, or watching with the sound off; every video with sound must offer synchronised captions.