Perceivable
Information must be presented in ways users can perceive through at least one sense. Provide text alternatives for images, captions for multimedia, and sufficient colour contrast.
The Complete Guide to Email Accessibility
Over 99% of marketing emails contain serious accessibility issues. This guide covers everything you need to know to build inclusive emails — from WCAG compliance and semantic HTML to colour contrast, screen reader optimisation, and a complete pre-send checklist.
Table of Contents
What Is Email Accessibility?
Email accessibility is the practice of writing, designing, and coding HTML emails that everyone can understand and engage with — regardless of physical, cognitive, or situational constraints. It includes optimising emails for people who use assistive technologies such as screen readers, magnifiers, head pointers, and voice control software.
Think of accessibility as an extension of dealing with email clients that have poor rendering support. Just as you add fallbacks for Outlook or Gmail, building accessible emails ensures every subscriber receives a positive experience — helping you reach a wider audience while building trust and loyalty.
The main standard for email accessibility is the Web Content Accessibility Guidelines (WCAG), developed by the W3C. While WCAG isn't a law on its own, it's the widely recognised framework that underpins accessibility regulations such as the Americans with Disabilities Act (ADA), the European Accessibility Act (EAA), and Section 508.
Why Email Accessibility Matters
By 2027 there will be 4.89 billion email users worldwide. Yet over 99% of marketing emails analysed by the Email Markup Consortium contain accessibility issues classified as Serious or Critical. If people have trouble viewing, reading, clicking, or understanding your campaigns, they won't take the actions you expect — and you're leaving revenue on the table.
1 in 4
adults in the US have a disability
2.2B
people globally have vision impairment
8%
of men experience colour blindness
$1T+
annual disposable income controlled by people with disabilities
Beyond the ethical imperative, accessible design also leads to stronger business outcomes. Accessible emails expand your reach, boost engagement, improve deliverability (more engagement means better sender reputation), and help you tap into the significant spending power of people with disabilities.
Accessibility is also a legal requirement. The ADA, the European Accessibility Act (effective 2025), the UK Equality Act, and Section 508 all establish standards for digital accessibility. Failing to meet them can result in lawsuits — website accessibility lawsuits increased 12% year-over-year — but more importantly, it excludes people who rely on accessible experiences.
WCAG Guidelines & POUR Principles
The Web Content Accessibility Guidelines define three conformance levels and are built on four core principles known as POUR. Most organisations target Level AA, which is the standard referenced by the ADA, EAA, and most international accessibility laws.
WCAG Conformance Levels
Level A
The minimum level of accessibility. Addresses the most basic barriers that prevent users from accessing content.
Level AA
The recommended standard. Includes all Level A requirements plus additional criteria for colour contrast, text resizing, and navigation. This is the target for most organisations.
Level AAA
The highest conformance level. Includes all A and AA requirements with enhanced criteria for sign language, extended audio descriptions, and stricter contrast ratios (7:1).
The Four POUR Principles
Operable
Users must be able to interact with all elements — navigable via keyboard, voice controls, or assistive devices. Ensure adequate tap targets and avoid interactions that require precise mouse control.
Understandable
Content and functionality should be clear and easy to understand. Use plain language, logical content structure, consistent navigation patterns, and clear error messaging.
Robust
Content must work reliably across all users, including those with assistive technologies, and remain compatible with evolving technologies. Use valid, semantic markup.
Types of Disabilities to Consider
Accessible email design accounts for a wide spectrum of permanent, temporary, and situational disabilities. One hundred percent of people will experience some form of situational or temporary impairment during their lifetime.
Vision Impairments
Includes blindness, low vision, colour blindness, cataracts, glaucoma, and sensitivity to brightness. At least 2.2 billion people globally have some form of vision impairment. Ensure proper colour contrast (4.5:1 minimum), readable font sizes (16px+), and compatibility with screen readers.
Auditory Impairments
Includes deafness, hard of hearing, and tinnitus. 65% of people with hearing loss are younger than retirement age. Provide video captions, podcast transcripts, and alternative text-based content for any audio elements.
Cognitive Disabilities
Affects memory, problem-solving, attention, or comprehension. Dyslexia impacts 5-10% of the population. Use simple layouts, avoid technical jargon, include clear instructions, and break content into small, scannable sections.
Neurological Conditions
Includes epilepsy, Parkinson's, ADD/ADHD, and conditions affecting motor control. Avoid flashing content between 2-55 Hz that could trigger seizures. Make emails easy to navigate and avoid requiring precise actions.
Physical Limitations
Includes tremors, paralysis, joint disorders, and missing limbs. Ensure emails are navigable with keyboard-only controls and screen readers. Use large enough tap targets (minimum 44×44px) for buttons and links.
Temporary & Situational
Broken arms, missing glasses, slow internet, bright sunlight, or using voice assistants in public. Everyone is only temporarily abled. Design with the assumption that any subscriber may need accessible features at any time.
Design Best Practices for Accessible Emails
Visual design is often where the biggest accessibility wins happen. Small changes to colour, typography, layout, and imagery can dramatically improve the experience for subscribers with disabilities — and for everyone else.
Colour Contrast & Usage
Use a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text. Never use colour alone to convey meaning — screen readers can't interpret colours. Create a colour matrix showing which brand colours work together and which don't.
Typography & Readability
Use a minimum 16px font size for body text. Set line-height to at least 1.5× the font size. Choose evenly-spaced, readable typefaces. Avoid justified text — left-aligned text is proven easier to read. Use rems instead of pixels to respect user browser settings.
Layout & White Space
Use generous white space between sections and around text. Add padding to move content away from email edges. Break text into short paragraphs. Avoid busy designs that can distract subscribers with ADD/ADHD.
Images & Alt Text
Never place important information inside images alone — always use live HTML text. Every important image needs descriptive alt text. Use empty alt attributes (alt="") for decorative images. Present important info as live text, not embedded in graphics.
Buttons & Tap Targets
Make buttons at least 44×44px for touch targets. Use live text in buttons instead of image-based CTAs. Use descriptive link text — avoid “click here”. Ensure links make sense when read out of context by screen readers.
Animations & GIFs
Avoid flashing content between 2-55 Hz that can trigger seizures. Use smooth, slow transitions. Limit GIF cycles and provide static fallbacks. Avoid strobe effects entirely. Test with accessibility tools before sending.
Coding Best Practices for Accessible Emails
While subscribers won't see the code, proper HTML structure is critical for assistive technologies to interpret your emails correctly. Semantic HTML adds meaning to your email code, helping screen readers and other assistive tools make sense of the content.
Semantic HTML & Heading Hierarchy
Use heading tags (h1 through h6) for headings instead of just styling text larger. This lets screen reader users scan through an email by jumping between headings. Every email should have exactly one h1. Use paragraph tags instead of line breaks for paragraphs — a paragraph stands for something while line breaks are only for spacing. Use the em element for emphasis (screen readers will emphasise) and strong for importance.
<!-- Use semantic headings for structure -->
<h1 style="mso-line-height-rule:exactly; margin:0; font-size:24px; line-height:28px;">
Main Heading
</h1>
<h2 style="margin:0; font-size:20px; line-height:24px;">
Sub Heading
</h2>
<p style="margin:0; font-size:16px; line-height:24px;">
Paragraph text here...
</p>role="presentation" & aria-hidden
Add role="presentation" to every table used for layout. This tells screen readers to skip the table structure and go straight to the content. Without it, screen readers announce every row and cell, creating a confusing experience. Add aria-hidden="true" to purely decorative elements like spacer images and visual dividers.
<!-- Layout table — tell screen readers to ignore the table structure -->
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%">
<tr>
<td>Content goes here</td>
</tr>
</table>
<!-- Decorative image — hide from screen readers -->
<img src="divider.png" alt="" role="presentation" aria-hidden="true" />Language & Title Attributes
Always set the lang attribute on your html tag (e.g. lang="en"). This tells screen readers which language to use for pronunciation. Include a meaningful title element — many screen readers announce it when opening the email. For multilingual content, use the lang attribute on specific elements to switch pronunciation.
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Your email subject line here</title>
</head>Alt Text Strategy
Decide whether each image is functional (describe the action), illustrative (describe the content), or decorative (use empty alt). Use different alt text for each image even if similar. Don't add title attributes in addition to alt text — screen readers read both, creating a poor experience. Have copywriters compose alt text rather than developers.
<!-- Functional image — describe the action -->
<img src="cta-banner.jpg" alt="Shop the Spring Sale — 30% off all items" />
<!-- Decorative image — use empty alt -->
<img src="decorative-swirl.png" alt="" role="presentation" />
<!-- Logo -->
<img src="logo.png" alt="EmailDeer" width="120" />Bulletproof Buttons with Live Text
Never use image-based buttons. Code bulletproof buttons with VML fallbacks for Outlook and live HTML text that screen readers can announce. This ensures the CTA is accessible regardless of image blocking, dark mode, or assistive technology.
<!-- Bulletproof button with live text -->
<table role="presentation" cellpadding="0" cellspacing="0" border="0">
<tr>
<td align="center" bgcolor="#1a73e8" style="border-radius:4px;">
<!--[if mso]>
<v:roundrect xmlns:v="urn:schemas-microsoft-com:vml"
href="https://example.com"
style="height:44px;v-text-anchor:middle;width:200px;"
arcsize="10%" strokecolor="#1a73e8" fillcolor="#1a73e8">
<w:anchorlock/>
<center style="color:#ffffff;font-family:sans-serif;font-size:16px;">
Shop Now
</center>
</v:roundrect>
<![endif]-->
<!--[if !mso]><!-->
<a href="https://example.com"
style="background:#1a73e8;border-radius:4px;color:#ffffff;
display:inline-block;font-size:16px;font-family:sans-serif;
line-height:44px;text-align:center;text-decoration:none;
width:200px;-webkit-text-size-adjust:none;">
Shop Now
</a>
<!--<![endif]-->
</td>
</tr>
</table>Writing Accessible Email Copy
Accessible copywriting helps subscribers with cognitive, neurological, or visual impairments — but writing clearly benefits everyone. An 8th-grade reading level is considered accessible for 85% of the general public. Here are key tips for accessible email copy:
- Keep sentences under 20 words and paragraphs short — big blocks of text are harder to read.
- Use active voice and direct language. Edit ruthlessly for clarity.
- Avoid slang, jargon, and regional expressions that some readers might not understand.
- Use headings, subheadings, and bullet points for content organisation and navigation.
- Write descriptive link text that makes sense out of context — avoid “click here” or “read more”.
- Compose unique, descriptive alt text for every important image. Have copywriters handle alt text rather than developers.
Use the Flesch-Kincaid Reading Ease test (available in Microsoft Word) to check readability. A score of 60-70 is ideal for most audiences — easily understood by 13-15 year olds. For specialised audiences, you can target a lower score, but always prioritise clarity over complexity.
Screen Readers & Assistive Technology
Screen readers convert digital content into spoken audio or Braille. Users navigate with keyboard shortcuts on desktop (jumping between headings, paragraphs, and links) and via swipe/touch on mobile. Content is presented one item at a time — completely different from how sighted users visually scan emails.
NVDA
Free, open-source screen reader for Windows. One of the most widely used according to WebAIM surveys.
JAWS
Commercial screen reader from Freedom Scientific. Supports Braille output and is popular in enterprise environments.
VoiceOver
Apple's built-in screen reader for macOS and iOS. The default choice for subscribers using iPhones and Macs.
TalkBack
Google's screen reader for Android, part of the Android Accessibility Suite. Over 2.7 million downloads.
Narrator
The default Windows screen reader. Usage has grown 150% since 2017 according to Assistiv Labs.
Digital assistants like Siri, Alexa, and Google Assistant are also being used to access email inboxes. Optimising for screen readers automatically improves the experience for AI-powered email reading. Always test your emails with at least one screen reader before sending.
Accessibility Testing Tools
Nearly 40% of marketers don't use any accessibility testing tools before launching campaigns. Following best practices is essential, but the only way to be certain you've built an accessible email is to test it. Here are key tools:
- WebAIM Colour Contrast Checker — free online tool to verify contrast ratios meet WCAG requirements.
- accessible-email.org — free accessibility reports and code adjustment suggestions for HTML emails.
- Parcel.io Accessibility Checker — free built-in accessibility scanner for the Parcel email editor.
- Microsoft Accessibility Insights — open-source testing tool for web and desktop applications.
- Built-in screen readers (VoiceOver, NVDA, TalkBack, Narrator) — test how your email sounds when read aloud.
Beyond automated tools, consider user testing with real people who have disabilities. User testing always provides insights that automated tools cannot catch. Integrate accessibility testing into your standard email QA workflow.
14-Point Email Accessibility Checklist
Use this checklist before every send to ensure your emails meet accessibility standards:
- 01Subject lines, sentences, and paragraphs are clear and concise.
- 02Language is free of unnecessary jargon and complex terminology.
- 03Content uses headings, subheadings, and bullet lists for organisation.
- 04Every important image has descriptive, unique alt text.
- 05Typefaces are readable and font size is at least 16px.
- 06Important information uses live text — never embedded in images alone.
- 07Colour contrast meets WCAG AA standards (4.5:1 minimum for text).
- 08Colour is not the sole method of conveying meaning.
- 09Animations avoid flashing between 2-55 Hz; GIFs have limited cycles.
- 10Sufficient white space supports readability and comprehension.
- 11Buttons use bulletproof code with live text (no image-only CTAs).
- 12Semantic HTML (<h1>-<h6>, <p>, <em>, <strong>) is used throughout.
- 13All layout tables have role="presentation" applied.
- 14The HTML lang attribute and a meaningful <title> tag are set.
Email accessibility is a critical aspect of professional email marketing that ensures campaigns are perceivable, operable, understandable, and robust for all subscribers — including the 1.3 billion people worldwide living with disabilities. Following WCAG 2.2 Level AA guidelines, using semantic HTML with proper heading hierarchy, applying role="presentation" on layout tables, including descriptive alt text, maintaining 4.5:1 colour contrast ratios, and coding bulletproof buttons with live text are foundational practices that every email developer must implement.
EmailDeer specialises in hand-coded HTML emails that meet WCAG accessibility standards across all major email clients. We implement semantic markup, screen reader optimisation, proper colour contrast, ARIA attributes, bulletproof buttons, and inclusive design patterns as standard practice. Whether you need a single accessible template or ongoing production support with accessibility testing built into the workflow, our team ensures every subscriber can engage with your campaigns.
Need Accessible Email Templates?
We hand-code every email to meet WCAG accessibility standards. From semantic markup to screen reader testing — we handle the complexity so every subscriber can engage with your campaigns.
