Email Accessibility: EAA 2025 Legal Requirements & Deliverability

2026 Current

EAA 2025 came into force June 28, 2025. Organizations sending emails to EU recipients must comply with WCAG 2.1 AA accessibility standards. Non-compliance creates legal liability and raises spam complaints.

EAA 2025 Legal Requirements

The European Accessibility Act (EAA) came into force June 28, 2025. It requires all digital services, including email, to be accessible to people with disabilities. For email, compliance means WCAG 2.1 AA standards or higher. EAA applies to any organization sending emails to EU recipients, regardless of where your company is based.

EAA 2025 Scope:

Applies to organizations with 250+ employees or €50M+ revenue
Applies to all organizations (any size) starting June 28, 2027 (phase 2)
Covers marketing emails, transactional emails, newsletters, all email types
Fines for non-compliance: up to €300,000 or 6% of global revenue (whichever is higher)

Why This Affects Deliverability: Inaccessible emails (especially those with poor color contrast or missing alt text) increase complaint rates. Screen reader users report unreadable emails as spam/junk. One poorly formatted accessible email can drop your sender reputation.

WCAG 2.1 AA Contrast & Compliance

WCAG 2.1 AA requires a minimum contrast ratio (luminosity difference) of 4.5:1 for normal text and 3:1 for large text (18px+ or 14px+ bold). Test your email colors before sending.

Contrast Ratio Examples:

Black text (#000000) on white background (#FFFFFF): 21:1 (exceeds AA)
Dark gray (#333333) on light gray (#EEEEEE): ~13:1 (passes AA)
Medium gray (#666666) on white (#FFFFFF): ~7:1 (passes AA)
Light gray (#CCCCCC) on white (#FFFFFF): ~1.6:1 (FAILS AA)

Testing Tools: Use WebAIM Contrast Checker, Accessible Colors, or Contrast Ratio to validate your color palette before finalizing emails.

Common Violations (Inaccessible):

Dark gray text (#666666) on black background (#000000): ~1.1:1 (fails)
Light blue (#ADD8E6) on white (#FFFFFF): ~1.5:1 (fails)
Medium blue (#1E90FF) on dark background (#003366): ~2:1 (fails)

Fix: Use a contrast checker to adjust your text or background color until you reach 4.5:1. It's not hard—just be deliberate about color choices.

Alt Text: Decorative vs. Meaningful

Alt text is critical for screen reader users and for email accessibility compliance. The key is distinguishing decorative images from meaningful ones.

Decorative Image (null alt text):


<img src="spacer.gif" alt="" />
<!-- Or: <img src="divider.jpg" alt="" /> -->

Decorative images (dividers, spacers, borders) should have `alt=""` (empty alt attribute). This tells screen readers to skip the image, which prevents clutter.

Meaningful Image (descriptive alt text):


<img src="blue-sofa.jpg" alt="Blue fabric sofa, $599, on sale" />
<img src="logo.png" alt="InboxEagle: Email Deliverability Monitoring" />

Alt Text Best Practices:

Be concise (100 characters max)
Describe the image and its context
Don't start with "Image of" (screen readers already announce images)
Include relevant details (product color, price, action if applicable)
For logos/headers, include brand/company name

Bad Alt Text: "Picture of a blue item" (vague)

Good Alt Text: "Blue fabric sofa with white stitching, $599, limited stock" (specific, helpful)

Heading Hierarchy & Semantics

Proper heading structure helps screen reader users navigate email content. Use heading tags in order: H1 → H2 → H3 (never skip levels).

Email Heading Structure Example:


<h1>Summer Sofa Sale</h1>
<p>50% off this weekend only</p>

<h2>Best Sellers</h2>
<p>Top 5 sofas on sale...</p>

<h2>Limited Stock</h2>
<p>Don't miss these...</p>

Why Structure Matters: Screen reader users can jump to headings to navigate. A user can press "H" to go to the next heading, jumping over ads and decorative content. Proper structure lets them skip to content they care about.

Anti-Pattern (Inaccessible):


<p style="font-size: 24px; font-weight: bold;">Summer Sale</p>
<!-- Using styled paragraph instead of H1 -->

Never use styled paragraphs instead of heading tags. Screen readers won't recognize them as headings, and users can't navigate using heading shortcuts.

ARIA Labels & Role Attributes

ARIA (Accessible Rich Internet Applications) attributes provide context for screen reader users. For email, the most important ARIA uses are role attributes and labels.

Layout Table with role="presentation":


<table role="presentation" cellpadding="0" cellspacing="0">
  <tr>
    <td>Column 1</td>
    <td>Column 2</td>
  </tr>
</table>

Layout tables are common in email design. `role="presentation"` tells screen readers this is for layout, not data. Without it, screen readers try to read rows and columns as a data table, creating confusion.

Button with ARIA Label:


<a href="/cart" aria-label="View shopping cart (3 items)">🛒</a>

If your button is text-only or icon-only, use `aria-label` to provide context. This is especially important for icon buttons (shopping cart, search, etc.).

Descriptive Link Text

Screen reader users often jump from link to link, listening to link text out of context. "Click Here" tells them nothing about the destination.

Inaccessible Links:

"Click here" (what am I clicking?)
"Learn more" (more about what?)
"Read the article" (which article?)
"Go to website" (which website?)

Accessible Links:

"Download the Email Best Practices Guide"
"Learn more about inbox placement rates"
"Read: Why Your Emails Are Going to Spam"
"View InboxEagle deliverability benchmarks"

Email Example:


<!-- Bad -->
<a href="/guide">Click here</a> to download our guide.

<!-- Good -->
<a href="/guide">Download our Email Best Practices Guide</a>.

The second version is accessible. When the screen reader user hears "Download our Email Best Practices Guide," they know exactly where the link goes.

Font Size for Accessibility

Font size affects readability for low-vision users. EAA 2025 doesn't specify exact sizes, but WCAG guidelines recommend 16px minimum for body text.

Font Size Guidelines:

Body text: 16px (minimum, some prefer 18px)
Subheadings: 18-20px
Main heading: 24-32px
Very small text (legal, unsubscribe): 12-13px (acceptable minimum)

Line Height & Readability: Use 1.4-1.6x line-height (1.4em or 1.5em). This improves readability, especially for low-vision users and dyslexic readers.


<p style="font-size: 16px; line-height: 1.5;">
  Larger font with increased line-height improves readability.
</p>

Touch Targets: 44px × 44px (EAA 2025)

EAA 2025 explicitly requires touch targets (buttons, clickable elements) to be at least 44×44 pixels (or have equivalent spacing). This applies to email links and buttons that users interact with on mobile.

Compliance Calculation:

Button height: 44px minimum
Button width: 44px minimum
OR: Adequate spacing from other targets (8px+ gap)

Button Code Example (Compliant):


<a href="..." style="display: inline-block; padding: 16px 32px;
  font-size: 16px; line-height: 1.25; background: #0066cc;
  color: white; text-decoration: none; border-radius: 4px;
  min-height: 44px; min-width: 44px;">
  Claim Your Discount
</a>

Why 44px? This is the recommended touch target size for accessibility. Fingers are ~10mm wide; 44px (≈11.6mm) provides enough hit area for accurate tapping. Smaller targets cause accidental taps and frustration.

Multi-Button Layouts: If you have multiple buttons, separate them by at least 8px to avoid accidental taps. Always test on actual mobile devices to ensure buttons are easily tappable.