Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, making emails accessible (alt text, headings, contrast, screen readers), or deciding transactional vs marketing.
All-time #1739Trending #1385Hot #4212First seen Mar 30, 2026
Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, making emails accessible (alt text, headings, contrast, screen readers), or deciding transactional vs marketing.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Make emails accessible (screen readers, alt text, contrast)
[Accessibility](./references/accessibility.md)
Start Here
New app? Start with the [Catalog](./references/transactional-email-catalog.md) to plan which emails your app needs (password reset, verification, etc.), then set up [Deliverability](./references/deliverability.md) (DNS authentication) before sending your first email.
Spam issues? Check [Deliverability](./references/deliverability.md) first—authentication problems are the most common cause. Gmail/Yahoo reject unauthenticated emails.
Accessibility? Most emails fail basic accessibility checks. See [Accessibility](./references/accessibility.md) for lang/dir, presentational tables, headings, alt text, <title>, and contrast.