Type E:
From Beyond the Envelope™
|
The alternative text issue — 1.
|
Of all of the pieces of email content, alternative text is arguably one of the most neglected. But, it is arguably one of the most important.
A few years ago, I decided to turn images off in my email client of choice, Apple Mail. I did this for two reasons. One, to experience the emails I received without their images. Two, to experience their images’ alternative text, some of which were bad and some of which were good.
In this issue, I’ll look at some of the bad experiences of alternative text I’ve had over that time and what we can learn from them.
|
What the Web Content Accessibility Guidelines have to say about images.
The Web Content Accessibility Guidelines (WCAG) consider images to be ‘non-text content’, and to conform to WCAG, you must meet the relevant Success Criterion for them. The relevant Success Criterion for ‘non-text content’ is Success Criterion 1.1.1 Non-text Content (Level A):
Success Criterion 1.1.1 Non-text Content
(Level A)
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
|
Helpfully, the guidelines include pages of techniques to help you meet their Success Criterion. Here are two examples from ‘Using alt attributes on img elements’:
Example 1:
An image on a website provides a link to a free newsletter. The image contains the text “Free newsletter. Get free recipes, news, and more. Learn more.” The alt text matches the text in the image.
<img src=" news letter.gif " alt="Free newsletter. Get free recipes, news, and more. Learn more." />
Example 2:
An image on a website depicts the floor plan of a building. The image is an image map with each room an interactive map area. The alt text is “The building’s floor plan. Select a room for more information about the purpose or content of the room.” The instruction to “select a room” indicates that the image is interactive.
|
|
|
Numbers
Numbers form the alternative text for most of the images on this email. In and of themselves, they convey no meaning to the recipient. The images are products, and the numbers are their product codes. The numbers are meaningful for the brand but not the recipient. It would be more appropriate to insert descriptions of those products into their respective alt attributes.
Example 1:
alt="Description of product."
|
|
Words and Numbers
A combination of words and numbers, separated by hyphens, form the alternative text for most of the images on this email. Once again, they’re meaningful for the brand but not the recipient. They refer to the articles they’re associated with and the email’s send date. Given this email’s rich visual nature, it would be more appropriate to insert descriptions of the images into their respective alt attributes.
|
Jargon
‘Display images to show real-time content’ is yet again meaningful for the brand but not the recipient. The difficulty with this image is that it’s dynamic content, and it’s a challenge to write alternative text for an image that’s constantly changing. It would be more appropriate to write generic alternative text or leave the alt attribute empty.
Example 1:
alt="Counting down. Sale ends soon!"
Example 2:
alt=""
|
|
Too Many Heroes
‘Hero image’ is jargon for an email’s first feature image. However, on this email, ‘hero image’ forms the alternative text for the first and a further three images. As this email features beautifully designed and beautifully manufactured products, a description of those products accompanied by their product names in their alternative text would be more appropriate.
|
Placeholder
‘Alt Tag Goes Here’. Plainly, a placeholder, and placed with good intent. Nevertheless, it illustrates how easy it is to neglect alternative text.
|
Another Placeholder
The number sign, pound sign or hash. Another placeholder.
|
Mind Your Language
‘Unsere Empfehlung 1’ is German for ‘Our Recommendation 1’ (so Google Translate tells me!), and it appears that the sender created this email in Germany. All other text on the email is in English. When working on multi-language emails, it’s important to ensure that both visible and ‘invisible’ text is in the same language and the correct language attribute is used (e.g. lang="en-GB").
|
Repeated Text
‘Benefit Offers’. ‘Benefit Offers’. ‘NARS Offers’. ‘NARS Offers’. On this email, some images have alternative text that’s identical to the live text that follows them. It results in a repetitive recipient experience for those using screen readers, leaving them none the wiser about the image content. Image descriptions would be more appropriate.
|
Branded
‘Brand name’, ‘Brand name’, ‘Brand name’, ‘Brand name’. A few emails have landed in my inbox where most or all of their images’ alternative text is their brand name. Image descriptions or depictions would be more appropriate.
|
White Noise
Apart from the live text in its navigation and footer, this email’s all image. Its headings, paragraphs and calls to action are all images, and none of these images have alternative text inserted into their alt attributes. As such, if you can’t see this email’s images, you can’t read it, engage with it, or buy products from it!
|
Conclusion
It’s easy to neglect alternative text. It’s hidden within HTML, and as such, it doesn’t appear on proofs. However, neglecting it can result in a poor recipient experience, as we’ve seen. So, let me conclude this issue of Type E: by giving you some alternative text tips:
- Pay attention to alternative text. If possible, commission a copywriter to write it.
- When copywriting alternative text, dictate, depict or describe:
- Dictate text embedded into imagery (images of text).
- Depict the context of imagery (e.g. a scene).
- Describe the content of imagery (e.g. a product).
- If you can’t dictate, depict or describe, use a null alt attribute (e.g. alt="").
- Consider its context and how it reads in and amongst its surrounding live text. Read it out aloud.
- Avoid repeating alternative text, either in an adjacent image or in an adjacent piece of text.
- Ensure all images include alt attributes.
|
Made with Envelope Developer™
Powered with
|
|
|