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.
> /plugin marketplace add Community-Access/accessibility-agents > /plugin install accessibility-agents@community-access
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
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.
Agent definition
email-accessibility.mdname: email-accessibility
description: 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.
tools:
- Read
- Edit
- Grep
- Glob
- Task
model: inherit
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.
Read more
name: email-accessibility description: 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. tools: - Read - Edit - Grep - Glob - Task model: inherit
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.
AI and automated tools are not perfect. They miss things, make mistakes, and cannot replace testing with real screen readers and assistive technology. Always verify with VoiceOver, NVDA, JAWS, and keyboard-only navigation.
Repo: Community-Access/accessibility-agents
Other agents on accessibility-agents.
- accessibility-lead
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side templates (.leaf, .ejs, .erb, .hbs), or any user-facing web content. This agent coordinates the accessibility specialist
Open agent - developer-hub
Your intelligent developer command center -- start here for any Python, wxPython, desktop app, NVDA addon, accessibility tool building, desktop accessibility, or general software engineering task. Routes to specialist agents across the developer, web, and document accessibility
Open agent - document-accessibility-wizard
Interactive document accessibility audit wizard. Use to run a guided, step-by-step accessibility audit of Office documents (.docx, .xlsx, .pptx) and PDFs. Supports single files, multiple files, entire folders with recursive scanning, and mixed document types. Orchestrates
Open agent - github-hub
Your intelligent GitHub command center -- start here. GitHub Hub discovers your repos and organizations, understands what you want to accomplish in plain English, and guides you to the right outcome by orchestrating every other agent. No commands to memorize. Just talk.
Open agent - markdown-a11y-assistant
Interactive markdown accessibility audit wizard. Runs a guided, step-by-step WCAG audit of markdown documentation. Covers descriptive links, alt text, heading hierarchy, tables, emoji (remove or translate to English), ASCII/Mermaid diagrams (replaced with full accessible text
Open agent - nexus
Your intelligent GitHub command center -- start here. Nexus discovers your repos and organizations, understands what you want to accomplish in plain English, and guides you to the right outcome by orchestrating every other agent. No commands to memorize. Just talk.
Open agent