Email accessibility — designing email that is usable by people with visual, motor, cognitive, and other disabilities — has moved from an aspirational best practice to a compliance requirement in 2026. The European Accessibility Act (EAA), which came into force in June 2025, requires businesses serving EU consumers to make digital communications including email accessible to people with disabilities. Beyond legal compliance, accessible email design generates better deliverability outcomes: semantic HTML structure that screen readers interpret correctly also produces cleaner content scoring at spam filters; appropriate color contrast that serves low-vision users also prevents the rendering quality issues that dark mode creates; descriptive alt text that benefits users with images disabled also improves the email's text-to-image ratio for spam filter evaluation.
Why Email Accessibility Matters in 2026
Approximately 15-20% of the global population has some form of disability that affects how they interact with digital content — visual impairments (blindness, low vision, color blindness), motor impairments (inability to use a mouse, limited fine motor control), cognitive impairments (dyslexia, attention disorders), and hearing impairments (relevant for video content in email). Email programmes that do not consider these audiences are excluding a significant fraction of their subscriber base from an accessible experience, and in 2026, potentially violating EU law for organisations serving the EU market.
The European Accessibility Act 2025 requires that digital services — including email marketing — comply with accessibility standards. The EAA applies to organisations with more than 10 employees or more than €2M annual turnover that operate in the EU market. For covered organisations, non-accessible digital communications including email are subject to enforcement action. The standard referenced by the EAA for digital accessibility is WCAG 2.1 Level AA — the Web Content Accessibility Guidelines developed by the W3C.
Beyond legal compliance, accessible email design produces commercial benefits: emails that render meaningfully when images are disabled (which includes all images when Apple MPP fetches them in non-rendering mode) generate better engagement from the approximately 35-45% of email recipients who read with images disabled. Semantic HTML that screen readers interpret correctly also helps search engine indexers (relevant if email content is repurposed as web content) and produces cleaner content markup that spam filters evaluate more favourably than table-soup HTML with no semantic structure.
Screen Reader-Compatible HTML Structure
Screen readers (NVDA, JAWS, VoiceOver, TalkBack) convert visual email content to audio or Braille output for blind and low-vision users. Screen reader compatibility in email requires specific HTML patterns that differ from standard web HTML because email uses tables for layout (CSS layout support is limited in email clients).
Table semantics for layout tables: Layout tables (used for email column structure) must be marked with role="presentation" so screen readers treat them as invisible layout containers rather than data tables. Without this attribute, screen readers announce "table with 3 rows and 2 columns" before reading the content — distracting and meaningless to the listener.
<!-- Correct: layout table with role="presentation" -->
<table role="presentation" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>Left column content</td>
<td>Right column content</td>
</tr>
</table>
<!-- Incorrect: layout table without role annotation -->
<table border="0" cellpadding="0" cellspacing="0">
Heading hierarchy: Use h1-h6 heading tags to establish document structure that screen readers use for navigation. The email's primary headline should use h1 or h2; section headings should use h3 or h4. Screen reader users can navigate by heading, allowing them to jump to relevant sections without listening to the full email content sequentially.
Language declaration: The lang attribute on the HTML element specifies the document language, which screen readers use to select the correct text-to-speech pronunciation engine. A French-language email without lang="fr" may be read with English pronunciation rules, producing incomprehensible audio for the screen reader user.
<!DOCTYPE html> <html lang="en"> <!-- or lang="fr", lang="de", lang="es" etc. -->
Reading order: The email's visual layout and the HTML source order should match. Screen readers read content in HTML source order — a layout where the sidebar column appears before the main content column in the HTML (even if the main content appears visually on the left through CSS) causes screen readers to announce the sidebar first, which is disorienting. Structure the HTML so that the logical reading order (main headline → body → CTA → supporting content) matches the HTML source order.
Alt Text: What, When, and How to Write It
Alt text (the alt= attribute on img elements) serves two audiences: screen reader users (the alt text is read aloud in place of the image) and sighted users with images disabled (the alt text is displayed as a text placeholder). Alt text strategy has three categories:
Informative images — descriptive alt text required: Images that convey content (product photos, infographics, charts, illustrations) need alt text that describes what the image shows and its relevance to the email. The alt text should convey the same information the image conveys for someone who cannot see it. Example: alt="Red wool sweater, crew neck, available in S-XL" for a product image, not alt="product image".
Decorative images — empty alt text: Images that are purely decorative (background patterns, decorative dividers, styling elements) should have alt="" (empty alt text, not missing alt attribute). An empty alt tells screen readers to skip the image entirely — which is the correct behaviour for a decorative element that has no informational value. A missing alt attribute (no alt= at all) causes screen readers to read the image filename, which is meaningless noise.
Logo images — brand identification: The company logo should have alt text that identifies the brand: alt="Acme Corporation". This allows screen reader users to identify the sender from the email body rather than relying on the From: header alone.
CTA button images — action text: If a CTA is implemented as an image (common in HTML email for custom button styling), the alt text should match the button text: alt="Shop the sale" or alt="Download the report". Never use generic alt text like alt="button" for a CTA image — the action text is the critical information.
Color Contrast and WCAG Requirements
WCAG 2.1 Level AA — the standard referenced by the European Accessibility Act — requires specific minimum contrast ratios between text and background colors:
- Normal text (below 18pt or 14pt bold): minimum 4.5:1 contrast ratio
- Large text (18pt+ or 14pt+ bold): minimum 3:1 contrast ratio
- UI components and graphical objects: minimum 3:1 contrast ratio
Contrast ratio is calculated from the relative luminance of the foreground and background colors. Online contrast checkers (WebAIM Contrast Checker, Colour Contrast Analyser) calculate ratios from hex color values. Check all text/background combinations in the email template — body text, headlines, CTA button text, legal footer text.
Common contrast failures in email design: light grey text on white background (#999999 on #ffffff = 2.85:1, below 4.5:1 requirement), yellow text on white background (often used for promotional highlights — frequently fails contrast requirements), light-colored text on brand-colored backgrounds (a brand's signature medium-blue background may not provide sufficient contrast for white text at small sizes).
The contrast check should be performed for both light mode and dark mode color combinations, since many email clients automatically convert light-mode color combinations to dark-mode equivalents that may produce different contrast ratios than the light-mode original.
Font Size, Readability, and Cognitive Accessibility
Readable email typography supports users with low vision, cognitive impairments, and reading difficulties. The accessibility typography standards for email:
Minimum font size: Body text should be at least 14px (16px recommended). Text below 14px is difficult for low-vision users to read even with system zoom enabled, and is often rendered unreadable on mobile displays without zoom. Legal and compliance text in email footers is typically 11-12px — these sections should include a note directing users with accessibility needs to the web version of the disclosure where font size can be adjusted.
Line height: Minimum 1.5x the font size for body text (150% line height). Tight line spacing reduces readability for users with dyslexia or cognitive processing difficulties. Email clients have inconsistent line-height support — use explicit line-height values in inline styles rather than relying on default browser or email client spacing.
Font family: System fonts (Arial, Helvetica, Georgia, Times New Roman) and web-safe fonts are safer choices for accessibility than custom web fonts, which may not render for users in low-bandwidth environments or with specific accessibility tools. If custom fonts are used, always specify a matching web-safe fallback stack.
Cognitive accessibility — plain language: Use clear, direct language free of jargon. Sentence length under 20 words for most body text. Active voice preferred over passive voice. Bullet points for list information rather than complex nested clauses. These practices benefit all readers but particularly benefit users with cognitive processing differences, dyslexia, and non-native language readers.
Link and Button Accessibility
Links and CTA buttons are the action elements of email — the elements that drive the commercial outcomes the programme measures. Accessible link and button implementation ensures these action elements are usable by all recipients.
Descriptive link text: Link text should describe the destination or action, not the URL or generic phrases. "Shop the collection" is accessible link text; "Click here" and "www.brand.com/collection" are not. Screen reader users can navigate by links (listening to each link text in sequence without surrounding context) — link text must be self-describing for this navigation mode to work.
Minimum touch target size: CTA buttons and links on mobile must be at minimum 44x44 pixels in touch target size (Apple's Human Interface Guidelines). Smaller targets are difficult for users with motor impairments to tap accurately. Use padding rather than just border to achieve minimum touch target size.
Visible focus indicator: For keyboard-only users (who navigate through email using Tab key), a visible focus indicator (border, outline, or background highlight) should appear around the currently focused link or button. Email clients vary in their default focus indicator behaviour — some suppress the default browser focus outline, making keyboard navigation impossible. Explicit CSS focus styles ensure keyboard-navigable email.
/* Ensure visible focus indicator for keyboard users */
a:focus {
outline: 2px solid #0050b3; /* High contrast focus ring */
outline-offset: 2px;
}
European Accessibility Act 2025: Email Compliance
The European Accessibility Act, effective June 28, 2025, requires businesses operating in the EU to make digital products and services — including digital communications — accessible to people with disabilities. For email marketing, EAA compliance requires meeting WCAG 2.1 Level AA standards across all consumer-facing email communications.
The EAA's scope for email: any business with more than 10 employees or more than €2M annual revenue that markets to or serves EU consumers must ensure their digital communications are accessible. This includes marketing email, transactional email, and account notifications. Exemptions exist for very small businesses (under 10 employees AND under €2M revenue) and for situations where accessibility compliance would create a disproportionate burden — but this exemption requires documented assessment and is not a blanket exemption for all small organisations.
The practical EAA compliance checklist for email: (1) All images have appropriate alt text. (2) Color contrast meets 4.5:1 minimum for body text and 3:1 for large text. (3) Font size minimum 14px for body text. (4) HTML structure uses role="presentation" on layout tables and heading hierarchy for semantic structure. (5) Language declared in HTML element. (6) Link text is descriptive and meaningful out of context. (7) CTA touch targets are minimum 44x44px. (8) Email renders meaningfully with images disabled. (9) A plain text version is available (required for WCAG email success criterion 1.3.1).
Testing Email Accessibility
Accessibility testing for email involves automated checks (contrast ratio, HTML validation, alt text presence) and manual testing with screen reader software. The testing sequence:
Automated checks: WAVE (WebAIM's accessibility evaluation tool) provides alt text, contrast, and semantic structure evaluation. Litmus Accessibility Checker tests email HTML against a set of email-specific accessibility criteria. Email on Acid's accessibility check covers major WCAG success criteria applicable to email.
Manual screen reader testing: Test the email using VoiceOver (Apple's built-in screen reader on iPhone and Mac) and NVDA (free Windows screen reader). Listen to the full email read aloud — does the content make sense without visual context? Is the reading order logical? Are all links descriptive? Are all images properly described or appropriately skipped?
Images-disabled testing: Most email clients allow disabling image loading. View the email with images disabled and evaluate whether the content is still comprehensible and whether CTAs are still actionable from the alt text alone.
Color contrast verification: Use WebAIM Contrast Checker or Colour Contrast Analyser to verify all foreground/background text combinations meet the 4.5:1 minimum. Check both light mode and dark mode colour combinations.
Email accessibility is not an optional enhancement — for organisations serving the EU market in 2026, it is a legal obligation. For all programmes regardless of jurisdiction, it is a quality investment that serves the 15-20% of subscribers with disabilities, improves the email's technical quality scores, and ensures the commercial content reaches its full potential audience. The practices documented in this guide — semantic HTML, appropriate alt text, sufficient contrast, readable typography — are standard email quality indicators that benefit all subscribers and require modest additional care rather than fundamental redesign of existing email templates.