# Accessible Email: Newsletters Everyone Can Read

Source: https://allyway.ai/glossary/accessible-email

Accessible email is a newsletter, transactional email or campaign built so that people with disabilities can read and use it: real text instead of text in images, alt text, a declared language, headings, sufficient contrast, descriptive links and layout tables hidden from screen readers.

Accessible email means your newsletters, order confirmations and campaigns can be read with a screen reader, enlarged without breaking and understood without seeing the images. Many marketing emails are one big picture with a "Shop now" button – for a blind reader that email is empty, and for everyone whose email program blocks images until they allow them, it's a gray box.

## What it means

There is no separate standard for email. The W3C note [WCAG2ICT](https://www.w3.org/TR/wcag2ict/), which explains how WCAG applies outside websites, lists emails as an example of documents. In practice, an HTML email is a small web page, so the same [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2) principles apply. The difference: you don't control how it is displayed. Email programs strip styles, block images, add their own dark mode and render it on screens from 320 pixels wide to a desktop monitor.

The most important rules for HTML email:

| Rule | Why it matters | WCAG criterion |
|---|---|---|
| Real text, not text in images | Screen readers read it, it scales, it shows when images are blocked | 1.4.5 Images of Text |
| [Alt text](https://allyway.ai/glossary/alt-text) for every meaningful image, `alt=""` for decorative ones | Blind readers hear what the image says | 1.1.1 Non-text Content |
| `lang` on the `<html>` element | The screen reader uses the right pronunciation | 3.1.1 Language of Page |
| Real headings (`<h1>`, `<h2>`) | Readers can jump between sections | 1.3.1 Info and Relationships |
| Layout tables with `role="presentation"` | Screen readers don't announce rows and columns | 1.3.1 Info and Relationships |
| [Color contrast](https://allyway.ai/glossary/color-contrast) of at least 4.5:1, large text 3:1 | Readable in sunlight and with low vision | 1.4.3 Contrast (Minimum) |
| Descriptive link and button text | "View your invoice" instead of "Click here" | 2.4.4 [Link Purpose](https://allyway.ai/glossary/link-purpose) |

> **Note:** > **Send a plain-text part as well**
> Multipart emails contain an HTML and a plain-text version. Some people set their email program to show only plain text, for example because it works better with their screen reader. Write that version properly instead of letting a tool generate an unreadable dump of links.

## Examples

```html title="Example"
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Your order has shipped</title>
</head>
<body>
  <table role="presentation" width="100%">
    <tr><td>
      <h1>Your order has shipped</h1>
      <p>Order 10482 is on its way and should arrive on Thursday.</p>
      <img src="logo.png" alt="Northlight Coffee" width="120">
      <img src="divider.png" alt="" width="600">
      <a href="https://example.com/track/10482">Track your parcel</a>
    </td></tr>
  </table>
</body>
</html>
```

The layout table is hidden from screen readers, the heading is a real `<h1>`, the logo has a name, the divider is marked as [decorative](https://allyway.ai/glossary/decorative-images), and the link says where it goes. Using [semantic HTML](https://allyway.ai/glossary/semantic-html) like this also makes the email easier for email programs to display.

**Do:** Do

Put the main message in live text at the top, use one column that works on small screens, at least 14–16 px body text, short paragraphs, underlined links and buttons with a clear label. Keep the subject line meaningful – it is the title of the email.

**Don't:** Don't

Send a single image with all text baked in, use pale gray text, rely on color alone ("click the green button"), use "here" as a link text or leave `alt` out so screen readers read the file name.

## How to check an accessible email



## Questions

Q: What makes an email accessible?
A: Real text instead of images of text, alt text, a declared language, headings, sufficient contrast, descriptive links, layout tables with `role="presentation"` and a single-column layout that works when zoomed or on a phone.

Q: Does WCAG apply to emails?
A: WCAG was written for web content, but the W3C note WCAG2ICT names emails as an example of documents it can be applied to. Because HTML email is built like a web page, the WCAG criteria are the accepted yardstick.

Q: Should emails have alt text on every image?
A: Every image needs an `alt` attribute. Meaningful images such as a logo, a product photo or a banner with an offer get a short description; spacers, dividers and pure decoration get `alt=""` so screen readers skip them.

Q: What font size should an email use?
A: WCAG sets no minimum font size, but text must stay readable when enlarged. Many senders use 14–16 px for body text and larger headings; what matters most is strong contrast and a layout that reflows.

Q: How do I check the contrast of my email colors?
A: Enter your text and background colors into the free [contrast checker](https://allyway.ai/free-wcag-contrast-checker). Normal text needs at least 4.5:1, large text 3:1.
