mcpField
E
email-accessibility

email-accessibility

github.com/community-accessTesting & quality429154 installsUpdated today
Repository

About email-accessibility

email-accessibility is a skill for auditing HTML email templates for accessibility, aimed at email designers and developers. It accounts for email-client rendering constraints and returns findings in a prescribed JSON format.

Key features

  1. 01Check semantic structure and reading order
  2. 02Review layout tables and image alt text
  3. 03Assess links, color contrast, and inline styles
  4. 04Check button targets and screen reader experience
  5. 05Return findings using the specified JSON schema

Use cases

  1. 01Audit HTML email templates for accessibility issues
  2. 02Review accessibility choices across email clients

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/community-access/accessibility-agents --skill email-accessibility

After installing, type/email-accessibilityin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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.

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. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

Comments

Markdown supported