Resources

Making Interactive Email Accessible: A WCAG 2.2 Checklist

WCAG was written for web content, but HTML email is still HTML rendered by a user agent — a webmail client is a browser, and a native mail app's rendering engine isn't fundamentally different. The same success criteria that govern an accessible web form apply just as directly to a poll, quiz, or accordion built from hidden checkboxes and labels.

Published August 23, 2026 · Updated November 14, 2026 · By the MailInApp Team

An email is a web page rendered by a mail app, so the Web Content Accessibility Guidelines (WCAG) apply to it as directly as they apply to a website. WCAG doesn't carve out an exception for email, and its success criteria hold for a poll, a quiz or an accordion just as they do for the same widget on a page. This is a practical checklist for the four criteria that matter most to interactive email, plus what MailInApp's studio checks for you.

Why WCAG applies here

WCAG 2.2 is written about "content" shown by a "user agent," not about web pages specifically. It doesn't name email, but an email's content is HTML either way, so the accessibility community treats WCAG's criteria as the practical bar for email, and this checklist does too.

1.1.1 Non-text content: every image needs a real alt

Product photos, hero images, separators and icon-only buttons need an alt a screen reader can announce. A purely decorative image gets an empty alt="" so the screen reader skips it instead of reading a filename. This matters more in interactive blocks: a spin-to-win wheel or scratch card made only of images, with no text describing the outcome, tells a screen-reader user nothing about what they won.

1.4.3 and 1.4.11: contrast for text and controls

WCAG asks for a 4.5:1 contrast ratio for body text (3:1 for large text, 1.4.3) and 3:1 for the edges of controls and graphics (1.4.11). Both apply to interactive elements: a poll option's border, a quiz answer's background against its card, a countdown's digits against their backdrop. A low-contrast control can be invisible to a low-vision reader.

2.1.1 Keyboard: native controls work without extra effort

Interactive blocks that use real radio buttons and checkboxes placed inside their labels can be reached with Tab and operated with Space or Enter, in any app that draws form controls. That's an advantage over a typical web carousel built from a clickable <div> with no keyboard handling, and it comes from the markup itself. How interactive email works explains the technique. Putting the input inside its label also matters for Yahoo Mail, which ignores a label that only points at an input with for. MailInApp builds its accordion, flashcards, scratch card and spin-to-win this way.

2.5.8 Target size (minimum): new in WCAG 2.2

Success criterion 2.5.8 sets a 24 by 24 CSS pixel floor for tappable targets, with exceptions for inline text, layouts that can't change, and an equivalent larger control elsewhere. It matters most on phones, where most emails are opened, for the elements that are easy to shrink too far: carousel dots, star icons and tightly packed answer chips.

4.1.2 Name, role, value: label every control

A screen reader announces a control's name, role and state from real markup, which a label wrapping a real input provides and a styled <div> doesn't. In practice every poll option, quiz answer and accordion header needs label text a screen reader can read aloud, not only an icon or a background image.

What MailInApp checks for you

The studio runs these checks while you build, so you fix issues before sending:

  • Accessibility panel. Preflight reports color contrast in light and dark mode, heading order, missing alt text (required on a linked image), vague link text such as "click here", the email's language, and tap targets that are too small. See Preview and testing.
  • Real labels by default. Poll options, quiz answers, accordion headers and the other interactive blocks are built as labelled controls, so keyboard and screen-reader access need no extra work from you.
  • Dark mode contrast. The checks cover your dark colors too. Theme, phones and dark mode shows how to set them.

Practical checklist

  • Every image has a real alt, or an empty alt="" if it's decorative.
  • Interactive text and borders meet 4.5:1 (text) and 3:1 (controls) contrast, in light and dark.
  • Every tap-to-reveal control is a real input inside its label, never a bare clickable <div>.
  • Interactive targets are at least 24 by 24 CSS pixels, especially in phone-sized layouts.
  • Poll, quiz and accordion labels carry readable text, not an image or icon alone.

Sources

Frequently asked questions

Does WCAG apply to email, not just websites?

WCAG's success criteria are written in terms of "content" rendered by a "user agent," without carving out an email-specific exception — and HTML email is HTML, rendered by a browser (webmail) or a comparable rendering engine (native clients). It isn't a formal email-specific standard, but the same criteria are the practical, defensible bar the accessibility community applies to email content.

Can a keyboard-only user operate a CSS :checked carousel or accordion?

Yes, when it's built correctly — a real <input type="radio"/"checkbox"> placed inside its <label> is natively focusable and operable with Tab plus Space or Enter in any client that renders form controls at all, with zero extra work. That's a genuine advantage of the checkbox-hack technique over a div-and-click-handler approach, which has no such native keyboard path and can't use one anyway since email strips JavaScript.

What's the minimum touch target size under WCAG 2.2?

Success Criterion 2.5.8 (Target Size, Minimum), new in WCAG 2.2, sets a 24x24 CSS pixel floor for interactive targets unless an exception applies (inline text, an essential layout constraint, or an equivalent larger control available elsewhere). It matters most for poll options, carousel dots, and quiz answers on the mobile clients that receive the majority of opens.

How much color contrast does interactive email copy need?

WCAG's 1.4.3 sets a 4.5:1 minimum contrast ratio for normal body text (3:1 for large text), and 1.4.11 sets a 3:1 minimum for the visual boundaries of UI components and graphics — both apply directly to poll/quiz option buttons and their labels, not just paragraph copy.

Build for the inboxes that actually matter

Start on the free plan — every interactive block and the full fallback engine are included on every tier.