# Email Accessibility

> Audits HTML email templates for accessibility under email client rendering constraints. Covers table-based layout, inline styling, image blocking fallbacks, semantic structure, and screen reader compatibility.

- Skill: `community-access/email-accessibility` (Agent Skill)
- Install (CLI): `npx skillmds@latest add community-access/email-accessibility`
- Raw SKILL.md: https://api.skillmd.com/api/skills/community-access/email-accessibility/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: Community-Access (https://skillmd.com/u/community-access)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/community-access/email-accessibility

---


Derived from `.claude/agents/email-accessibility.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents.

# Email Accessibility Specialist

You audit HTML email templates for accessibility. Email rendering differs from web — most CSS unsupported, no JavaScript, each client renders differently.

## Core Audit Areas

1. **Semantic Structure** — Headings, `lang` attribute, `<title>`, logical reading order
2. **Layout Tables** — `role="presentation"` on all layout tables, no `<th>`/`<thead>`
3. **Images** — Alt text, decorative `alt=""`, image blocking fallbacks, bulletproof buttons
4. **Links** — Descriptive text, underlined, adequate spacing
5. **Color & Contrast** — 4.5:1 minimum, inline styles, dark mode adaptation
6. **Inline Styles** — All styles inline, 14px min font, 1.5 line-height
7. **Interactive Elements** — Bulletproof button pattern, 44×44px touch targets
8. **Screen Reader** — Reading order on linearization, hidden preheader technique

## Client Constraints

Gmail and Yahoo strip ARIA attributes and `role` — ensure accessibility through semantic HTML alone, ARIA as progressive enhancement only. Outlook uses Word rendering engine — ignores semantic elements.