Beyond the Envelope™ create and code accessible and usable HTML emails.

Beyond the Envelope™ both create (design) and code (develop) accessible and usable HTML emails, backed by ten years of extensive experience implementing the Web Content Accessibility Guidelines (WCAG) into them.

Packages

It delivers those services in the form of its In Creative, In Code and In Components packages. In Components is comprised of both creative and code elements.

In Creative
(Design)

Features

  • WCAG 2.2 A, AA (and AAA where relevant) conformant.
  • Created for mobile, tablet and desktop (Responsive).
  • Created in Figma.
  • Created with conformance documentation, outlining which elements conform to which WCAG Success Criterion.

Benefits

  • Access accessible HTML emails without having to work out how to conform to the WCAG.
  • A set of documentation at hand in the event you need to provide evidence of accessibility.

In Code
(Development)

Features

  • WCAG 2.2 A, AA (and AAA where relevant) conformant.
  • Coded for email (HTML and CSS).
  • Coded mobile first, tablet second and desktop third (Responsive).
  • Tested in Litmus.
  • Coded with conformance documentation, outlining which elements conform to which WCAG Success Criterion.

Benefits

  • Access accessible HTML emails without having to work out how to conform to the WCAG.
  • Coded mobile first, emails flow without error in the most stubborn email clients, webmail clients and apps.
  • A set of documentation at hand in the event you need to provide evidence of accessibility.

In Components
(Email Design System)

Features

  • Created in Figma.
  • Coded in Parcel.io.
  • Tested in Litmus.
  • Comprising reusable and revisable components and snippets.
  • Created and coded with conformance documentation, outlining which elements conform to which WCAG Success Criterion.

Benefits

  • Access accessible HTML emails without having to work out how to conform to the WCAG.
  • Create components once, use multiple times.
  • Minimise testing accessibility, usability and rendering.
  • Distribute accessible email components and snippets at scale.
  • A set of documentation at hand in the event you need to provide evidence of accessibility.