Accessible Email Design: Practical Requirements
Most email accessibility failures are not exotic. They are the predictable result of building an email that looks correct in one client, on one screen, at one zoom level, and assuming that generalizes. It doesn’t. A subscriber reading your campaign in Outlook 2019 on Windows with 200% zoom, a screen reader, and high-contrast mode enabled is not an edge case you can deprioritize. They are a real user with a real inbox, and your email either works for them or it doesn’t.
This article covers the specific design requirements that separate an email that technically renders from one that actually functions: contrast ratios with real numeric thresholds, semantic structure that survives client stripping, alt text that does a job, dark mode behavior you can predict, and the structural reasons image-only emails fail. Every section includes at least one thing that catches experienced designers out.
None of this requires a rebuild. It requires knowing which numbers matter, which HTML survives, and where the trade-offs actually are.
Start With the Numbers: Contrast Ratios That Hold Up
WCAG 2.1 sets the baseline. Normal body text needs a contrast ratio of at least 4.5:1 against its background. Large text, defined as 18pt (24px) regular or 14pt (18.66px) bold, needs 3:1. Non-text elements that convey meaning, including icons, form field borders, and focus indicators, need 3:1. Those are the numbers. Memorize them and stop guessing.
Here is what catches people out. The ratio is calculated between the text color and the actual rendered background, not the background declared in your CSS. If you place dark gray text on a light gray panel, and that panel’s background color gets stripped by Outlook’s Word rendering engine, your text is now sitting on white. It might pass. It might not. Test the worst-case pairing, not the intended one.
Two more practical points:
- Pure gray on white is a trap. #767676 on white lands almost exactly at 4.54:1. It passes, barely. Shift one step lighter and you fail. If your brand palette includes mid-grays for secondary text, check each one against every background it will actually appear on.
- Colored buttons need checking in both directions. White text on a mid-tone brand color often fails. So does dark text on a saturated accent. Compute the ratio before you ship, not after a complaint.
Contrast also interacts with dark mode, which we’ll get to. A pairing that passes at 5:1 in light mode can collapse to 1.8:1 if the client inverts your background but not your text color. That is a design decision you need to make deliberately, not one you inherit by accident.
Semantic Structure: What Actually Survives the Trip
Semantic HTML in email is a negotiation, not a guarantee. You write <h2> and <p> and <ul>, and then Outlook.com, Gmail, and a dozen mobile clients decide what to do with them. Some preserve structure. Some flatten it. Some rewrite it entirely.
The practical rule: use real semantic tags, because assistive technology and clients that respect them will benefit, but never rely on semantics alone to communicate hierarchy. A screen reader user navigating by heading (a very common pattern, since it lets them skim long emails the way sighted users do) depends on actual heading tags being present and correctly nested. If your “headline” is a styled <p> or a table cell with large bold text, it is invisible to that navigation.
Heading order matters more than people think
Do not skip levels for visual reasons. If your email’s top headline is an <h1>, the next section heading should be <h2>, not <h3> because the <h3> happens to be the size you want. Control size with CSS, control structure with tags. Screen reader users navigating by heading level expect a logical outline, and a broken outline is disorienting.
One contested point: there is no universal agreement on whether every marketing email needs an <h1>. Some practitioners argue the subject line serves that role and the email body should start at <h2>. Both approaches are defensible. What is not defensible is a document with no heading structure at all, or one where headings are chosen by font size.
Lists, tables, and reading order
Use <ul> and <ol> for actual lists. Screen readers announce list length (“list, four items”), which helps users decide whether to engage. A stack of <p> tags with bullet characters typed in manually gives them none of that.
For layout tables, which remain unavoidable in email, add role="presentation" so assistive technology skips the table semantics. Without it, a screen reader may announce “table, three columns, twelve rows” for what is purely a visual grid, forcing the user through meaningless structure. Keep content tables (actual data) semantic, and mark layout tables as presentational. The distinction is whether the table conveys relationships between cells.
Alt Text: Doing the Job, Not Filling the Field
Alt text is the most commonly botched accessibility feature in email, and the failure is rarely a missing attribute. It is a present attribute filled with something useless: the filename, a duplicate of the button label, or a generic “banner image.”
The test for alt text is simple. If the image disappeared and were replaced by the alt text, would the email still make sense? If yes, it’s doing its job. If the alt text just says “hero image,” it isn’t.
Three categories, three treatments
- Informative images (a product photo, a chart, a person) need alt text that conveys the information the image conveys. For a chart, that means the trend or the key number, not “chart.” For a product, the product name and the detail that matters.
- Functional images (a button, a linked logo, an icon that triggers an action) need alt text describing the destination or action: “Shop the spring collection,” not “button.”
- Decorative images (a divider, a background flourish, a spacer) should have empty alt text:
alt="". This tells the screen reader to skip it. Omitting the alt attribute entirely is worse thanalt="", because some screen readers will then announce the filename.
Two details experienced practitioners get right and beginners miss. First, do not start alt text with “image of” or “picture of” — screen readers already announce that it’s an image. Second, keep alt text under roughly 125 characters where possible, because some clients truncate and screen readers read the whole thing; if the image needs more, the information probably belongs in body copy near the image rather than in the alt attribute.
If the image is the only place a piece of information appears, and the alt text doesn’t carry it, that information is simply gone for a screen reader user. There is no fallback.
Where to host the site behind the list
None of the tactics in this article matter if the infrastructure behind them is slow,
poorly configured, or capped at a mailbox size you outgrow in a month. If you are setting up
a site, a landing page, or a sending domain from scratch, Hostinger is a sensible starting point: entry plans are cheap enough to
experiment with, the control panel exposes DNS records for SPF, DKIM and DMARC without a support
ticket, and the VPS tier is there when you outgrow shared hosting. What matters more than the
headline price is that it scales predictably as the list grows.
Why Image-Only Emails Fail Real Users
A single image with no live text is the most reliable way to break an email for the largest number of people at once. The reasons stack up:
- Images are blocked by default in many clients. Outlook desktop and several others block remote images until the user opts in. An image-only email shows as a blank rectangle with a “download images” prompt. A meaningful share of recipients will never click it.
- Screen readers get nothing. Text baked into a JPG or PNG is not text. It cannot be read, searched, or resized. Alt text on the whole image is a poor substitute for actual copy, because you cannot put a paragraph of readable content into a reasonable alt attribute.
- Zoom and reflow break. A user at 200% zoom or on a narrow screen cannot reflow an image. Text in the image scales as pixels and either blurs or forces horizontal scrolling.
- Dark mode inverts it unpredictably. A light-background image may be auto-inverted or left alone, producing jarring results, and text inside the image can become unreadable.
- Translation and search fail. Image text is invisible to translation tools and to the recipient’s search.
The fix is not complicated: live text for all content, images as enhancement. If a design absolutely requires text-in-image for a headline treatment, duplicate that text as live, visually hidden text or as a nearby caption, and give the image appropriate alt text. This is a compromise, not a solution, and it should be rare.
Dark Mode: Predictable Behavior Beats Perfect Appearance
Dark mode handling is genuinely contested, and anyone who tells you there’s one correct approach is oversimplifying. Different clients do different things. Apple Mail and Outlook mobile may partially invert colors. Gmail app on Android applies its own transformations. Some clients respect prefers-color-scheme media queries; many do not. Outlook.com historically ignored them entirely.
You cannot control every client. You can make the outcome predictable. The practical requirements:
- Never rely on transparent PNGs with dark text. If a logo or icon has dark text on a transparent background, a client that darkens the background will render it invisible. Use images with their own solid, intentional background, or supply a light-on-dark variant.
- Set explicit background colors on containers. When a client inverts, it inverts what it can see. Explicit backgrounds give it something to work with and reduce unpredictable results.
- Test the inverted state as a real state. Put your email through a client that inverts (Apple Mail dark mode is the common test) and check every text/background pairing again. A 5:1 ratio in light mode can become 1.8:1 inverted.
- Use
prefers-color-schemewhere supported, as progressive enhancement. Add dark-mode styles for clients that honor them, but design the default to survive inversion for clients that don’t.
The trade-off is real: aggressive dark-mode optimization for one client can produce worse results in another. The goal is no unreadable text and no invisible logos across the major clients, not a pixel-perfect dark theme everywhere.
Tap Targets, Zoom, and the Mobile Reality
Accessibility guidance converges on a minimum tap target size of 44×44 CSS pixels (Apple’s Human Interface Guidelines) or 48×48 (Material Design). For email, this matters because the majority of opens happen on mobile, and a 20px-tall text link is genuinely hard to hit for anyone with limited dexterity or a tremor. Give buttons padding to reach the target size even if the visible button looks smaller; the tappable area is what counts.
Also respect zoom. Do not lock viewport scaling with user-scalable=no or a fixed maximum-scale. Users who zoom in to read need that ability, and disabling it is a direct accessibility failure. Design for reflow at 200% zoom: single-column layouts, no fixed widths that force horizontal scroll, and text that wraps rather than clips.
A Short Pre-Send Checklist
The requirements above compress into a checklist you can run before every send:
| Check | Threshold or standard |
|---|---|
| Body text contrast | ≥ 4.5:1 against rendered background |
| Large text contrast | ≥ 3:1 (18pt regular / 14pt bold) |
| Icon and border contrast | ≥ 3:1 |
| Heading structure | Real heading tags, no skipped levels |
| Layout tables | role="presentation" applied |
| Informative alt text | Conveys the information, not the filename |
| Decorative images | alt="" present |
| Live text | All content is text, not baked into images |
| Tap targets | ≥ 44×44 CSS pixels |
| Zoom | Scaling not locked; reflows at 200% |
| Dark mode | Tested in at least one inverting client |
Related reading
Conclusion
Accessible email design is not a separate discipline bolted onto your existing process. It is a set of specific, checkable requirements: numeric contrast thresholds, real semantic tags that survive client stripping, alt text that carries information, deliberate dark-mode decisions, and live text instead of image-only content. Each one has a concrete test and a concrete failure mode.
The practitioners who get this right treat accessibility as a build constraint, the same way they treat table-based layout or the 600px width. They check contrast before approving a palette. They write alt text as they place images, not afterward. They test the inverted state the way they test the mobile state. None of it is glamorous. All of it is the difference between an email that reaches everyone and one that quietly excludes a meaningful share of its audience.
Disclosure: this article contains an affiliate link. If you buy through it we may earn a commission at no extra cost to you. We only link to services we would recommend on merit.
Pingback: Moosend vs Sendinblue (Brevo): Which Is Better for Transactional Emails in 2026? – emailversus.com
Pingback: Mobile-First Email Design Without Losing Desktop – emailversus.com
Pingback: HTML vs Plain Text Email: What the Evidence Says – emailversus.com