Email Accessibility

HTML email accessibility under email client rendering constraints.

449 stars 54 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Community-Access/accessibility-agents

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Community-Access/accessibility-agents --skill email-accessibility
Manual install
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/email-accessibility ~/.claude/skills/email-accessibility

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## Email Accessibility Specialist

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

**Skills:** `kb-email-accessibility`

## 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, targets at least 24x24 CSS px (2.5.8, AA; 44x44 for 2.5.5, AAA)
8. **Screen Reader** - Reading order on linearization, hidden preheader technique

## Client Constraints

Gmail and Yahoo strip ARIA attributes and `role`, so ensure accessibility through semantic HTML alone, with ARIA as progressive enhancement only. Classic Outlook for Windows uses the Word rendering engine and ignores many semantic elements.

## Output contract

Return only JSON matching `skills/a11y-core/schemas/findings.schema.json`.
No prose, no summary, no restated instructions. One object, one array of findings.

Shared rules, dispatch contract and schemas: `skills/a11y-core/SKILL.md`.
Read the full skill on GitHub

Details

Skill name
email-accessibility
Path
skills/email-accessibility/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Email Accessibility skill do?

HTML email accessibility under email client rendering constraints.

How do I install the Email Accessibility skill?

Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Email Accessibility popular?

It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.

Related skills

A11y Core

449

Community-Access/accessibility-agents

Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.

Frontend & Design54

A11y Tool Builder

449

Community-Access/accessibility-agents

Build accessibility scanners, rule engines, parsers and report generators.

Frontend & Design54

Accessibility Lead

449

Community-Access/accessibility-agents

Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.

Frontend & Design54

Kb Email Accessibility

449

Community-Access/accessibility-agents

Reference data, not a reviewer. HTML email accessibility: table layouts, inline styles, dark mode, image fallbacks, and email client rendering constraints.

Productivity & Notes54

Turborepo

398

JetBrains/skills

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

Productivity & Notes35

Osaf Workflow

449

Community-Access/accessibility-agents

Open Source Accessibility Framework Workflow phase: expectations, reporting, triage, PR template, labels, docs.

Productivity & Notes54

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.