Readability is key
Accessibility is Readability
READABILITY IS THE QUALITY OF BEING EASY OR ENJOYABLE TO READ.
The Cambridge English Dictionary
Write copy everyone can understand
- Keep your copy concise
- Use shorter sentences - break long paragraphs
- Limit the use of jargon and difficult words
THE IDEAL LINE LENGTH IS 50-70 CHARACTERS
Create a visual hierarchy
- Carefully consider the type face, font size, line spacing and white space you use
- Use sans serif typefaces
- The minimum readable font size is 14 pixels
- Consider adding media queries to increase the minimum font size to at least 16-18 pixels on mobile. (On devices with high DPI fonts will look smaller.)
- Ideally use minimum 150% line height
- Use padding / white space to structure the content of your email. By just adding more white space, the email is perceived as easier to read
- Use left aligned text as much as possible
- Make centre aligned text no longer than 2 lines.
NEVER USE JUSTIFIED TEXT
- Links should stand out, not just by using colour. It is good practice to underline links by default and remove the underline on hover. Also consider bold text or increased font size.
Choose your colours wisely
An email design should have a minimum contrast ratio of 4.5:1 to meet level AA standards outlined by the Web Content Accessibility Guidelines (WCAG) 2.0.
In Litmus, there is a "colour blindness" simulated preview - remember to use it.
Ultimately, don't rely just on colours
Colour is good for structuring content, highlighting links etc. - but remember that if the user is colour blind you have to use other visual cues as well.
No more tables?
Traditionally emails are coded using <table> based HTML. This allows the design to be easily translated into code and rendered across devices and email providers.
- Tables are still needed to build the email structure, but it is possible to reduce their use drastically.
- Wherever possible, you can use <divs> wrapped by Outlook ghost tables.
Use the right code
- Set character encoding in your meta tags.
- Set the Title of the email - so that it provides context to users.
- Use the lang attribute (e.g. lang="en")
- Use semantic code: <h1>.....<h6>, <p>, <ul>,<ol>, <li> etc. to structure your message.
- Use role="presentation" or role="button" wherever applicable.
- Call to action buttons or links should clearly describe the action itself not just say "click here"
- Don't set titles on links, as screen readers will read both the title and link text. If the link text is not appropriate for a screen reader add aria-label
- Hide non relevant content with aria-hidden="true"
- Always add alt tags to images
Image Alt Tags
Images are disabled by default in many email clients (notably Outlook desktop and Yahoo).
- It is essential to use descriptive text where images are relevant to the email content.
- Where the image is just for decoration, make sure to add an empty alt tag (alt="").
- The alt text itself should be styled to look as close as possible to the image.
If you don't pay attention, your email could look like this:
But if you apply all the above, it could look like this (note the icon is just for decoration so has no alt tag):
In summary
Step 1: design with accessibility in mind:
- 📚 Accessibility is readability
- 👁️ Create a visual hierarchy
- 🎨 Choose your colours wisely
Step 2: use the right code:
- 🔠 Set the language attribute.
- 📇 Add content type
- 📰 Set the title of the email
- 🎁 Set your table role to presentation
- 🗞 Remove title attributes
- ➕ Add alt text
- 🎨 Check your contrast ratio
- 🔗 Make links accessible (underline)
Credit: @EmailonAcid
Step 3: test, test, test
- ✔️ Use the accessible email checker
- 📧 Test in your personal inbox
- 🎨 Test your colour contrast and /or use the colour-blind preview in Litmus (if available to you)
- ☑️ Use Litmus checklists / Email on Acid accessibility tool (if available to you)
Resources
The ultimate guide to accessible emails (blog post)
The Ultimate Guide to Email Accessibility (ebook)
Email accessibility: how to make email for everyone in 3 easy steps (webinar)
A deep dive into email accessibility
Type E: an email newsletter devoted to typography in email
How to code a responsive email from scratch
How Litmus didn't use tables for its first email newsletter of 2018
Credits:
Created with images by Ash Edmonds - "Inspired by Efe’s colorful photo, I rotated his photo from Spain, which illuminated the MacBook Pro beautifully. Find his photo here: https://unsplash.com/photos/RnCPiXixooY The composition of the shot was inspired, well shamelessly copied from Michal’s shot, found here: https://unsplash.com/photos/WecngmAT-KY Gotta learn somehow :)" • Yomex Owo - "untitled image" • Jaredd Craig - "Spent a week in Los Angeles with my friends and decided to visit the Last Bookstore as one of our stops. I came up with the idea of floating the book with help of my friend. I took two shots one without the book and one with the book being held up from my friend. Photoshopped his arm out of the shot later in post and this was the outcome." • Edvard Alexander Rølvaag - "Nine pebbles stabled on top of each other at the beach of D-day (6th of June 1944), Gold Beach in Normandy, France." • Joyce McCown - "Who knew you could create such beauty with simple things like water, food coloring , light, and glass tubes!" • Alexander Sinn - "Pixel Heart" • Nadia Valko - "untitled image" • KOBU Agency - "Papercraft toy in front of PHP echo statement" • Dan Gold - "Prints by @danielcgold & @beccasiegelphoto" • Bill Oxford - "Test tubes in metal rack. Concept for science, medical, research. " • J. Kelly Brito - "From the Creatives Working collection. Full collection at kellybrito.com" • David Travis - "Notetaking" • Jon Tyson - "untitled image"