Simply Put the agency blog

Posts Tagged ‘standards’

9 best practices for email design

March 2nd, 2008 by Verne

Designing for an email is still quite far off from designing for a browser. In fact, email reader standards are pretty historic in the sense that (a) it requires designers to degrade their modern coding practices and (b) there really are no true standards.

Fortunately, there are bodies in place that are working on standardizing the way emails are being rendered. But something tells me that we shouldn’t hold our breath (after all, we haven’t even fully standardized the experience within browsers yet). So in the mean time, here are some basic best practices to follow when designing for emails that will ensure your work displays as intended.

1. Go old school with your HTML

Go old-school on your HTMLScrap everything you’ve learned in recent years about tableless CSS structures and revert back to the HTML that your grandma grew up with (a little exagerated but it seems that long since we’ve used tables). Forget about positioning divs with CSS and rely on trusty table cells to lay out your content as many email readers will not render positioning instructions properly or at all. Be safe, be old school.

2. Use inline style tags

Email Standards Project Acid TestMost major email readers, whether they’re online, like Gmail and Hotmail, or desktop applications, like Outlook and Thunderbird, will ignore everything between the <head></head> tags, including your style definitions (whether you do it via <link> or <style></style> tags). This means you should style your HTML using inline styles. Be careful though - there are many CSS properties that will not render properly, like the aforementioned position property. A detailed report on how various major email readers performed against an Acid Test (which tests a handful of common CSS properties) can be found here.

3. Don’t rely on using background images

Gmail’s Acid Test performance shows no background imagesUsing background images has become an essential tool on the designer’s belt. However, there is such an inconsistency between which browsers will actually display background images that it’s best to not rely on them. As an Outlook 2007 user, I know as a fact that no background images are displayed (this is true for Gmail as well). On the other hand, readers like AOL Webmail and Windows Live Mail (not Hotmail) will render background images correctly. Since it’s too difficult to predict what reader your audience is using, your use of background images should only be for enhancement and not as something your entire design depends on.

4. Consider your images blocked by default

Many email readers block images by defaultFor security purposes, many email readers will block images embedded in an email by default. The reader must opt-in on each email to display the images (though some may allow readers to set their preference). What this means is that you should rely on your images to communicate your message. Avoid replacing too much text with images and make sure your email design still gets the point across even when images are not displayed.

5. Use the ALT attribute for images

Use the ALT attribute to communicate your blocked image’s messageTo avoid completely losing the message on an image when images are blocked, fill out the ALT attribute for each of your images. This ensures that the important content from the image (i.e. the text) is still passed along. This also helps in cases where the reader is using a text-only email client, as the image will be replaced by the ALT attribute.

6. Use absolute paths

Use absolute paths when referencing imagesThis one’s a no-brainer but make sure to use absolute paths when referencing images. Relative paths (i.e. /images/my-image.jpg) will break as the email reader won’t know what the path is relative to. Your image paths should look like this instead: http://www.mywebsite.com/emails/images/my-image.jpg. This is so simple that it can often be accidentally overlooked so make sure to double check your image paths before you transition from draft to final.

7. Be considerate of file sizes

Be considerate of file sizesLoading up your email design with large images will slow down the download process on the reader’s end and may deter them from reading it all together. In some cases, exceptionally large emails may also be flagged for spam and viruses. To minimize these risks, optimize your images so that they have the smallest possible file size. This may require you to play around with JPG, GIF, and PNG formats to see which gives the highest image quality with the smallest file size. Where possible, use plain text to communicate your message.

8. Avoid rich media and forms

Avoid embedding rich media like FlashIn a browser, using Flash, animated GIFs and forms add interactivity to the user experience. In an email, it bulks up the file size, raises security flags, or just doesn’t work. If there are interactive components attached to your email campaign, you are far better off linking the reader to a live site than to attempt to embed them into the email itself. It’s an extra step but at least you can be sure that your rich media and forms will work.

9. Design for smaller spaces

Design your emails with appropriate widthsJust like designing for a web browser, you need to be considerate of screen resolutions and window sizes. In addition to this, email readers often have added sidebars and navigations on both sides of where your email content is displayed, further decreasing the amount of space you have to play with. Be safe and keep the width of your email design at least within 800px (we commonly use 750px).

If you’re running an email campaign and would like to learn more about best practices for email designs, speak to us. We’d love to help you.

28 Comments

Tags: , ,

Farewell, IE6

January 22nd, 2008 by Verne

Internet Explorer 7It is with great sadness but greater joy that I share the news that IE6 will finally be put to rest come this February. According to InfoWorld, Microsoft has finally given the thumbs up to an autoupdate of IE6 to IE7 which is set to occur on February 12.

As web designers, we’re constantly kept awake at night fighting crime in the war of browser compatibility issues, hoping only to build websites that deliver consistent experiences to all users regardless of their browser of choice. Microsoft did us all a favour with the release of IE7 not too long ago, marginalizing the differences in how it displays websites between it and its next leading competitor Firefox. But despite this and all the new features and innovations that IE7 brings to users, there still remains a significant portion of internet users who haven’t been incented enough to make the leap from IE6 to IE7. This essentially has meant that the designers who choose to make accomodations for outdated users must design websites for 3 very different browsers. Until now, that is.

On February 12, the update will roll-out and a good 30% of the internet population will see many websites in a whole new light and in the way they were truly designed to be seen (despite our greatest efforts, many websites are still not fully cross-browser compatible). For us, it means the old ‘tester’ computer that still runs IE6 may finally be unplugged. Coincidentally, its power supply died last week.

You can read the full article on InfoWorld here. For the truly stubborn, the article also mentions ways to avoid the autoupdate.

This is great news for the community, and it comes shortly after the announcement of another exciting IE milestone. It’s definitely a good time to be a web designer.

2 Comments

Tags: , ,

The Email Standards Project

December 22nd, 2007 by Verne

Email Standards ProjectWith the explosion of the social media landscape, marketers today have a lot more vehicles to choose from to carry their messages. But of those options, email marketing still holds its ground as a prominent and commonly used medium. What seems to have also not changed are the difficulties that those who produce creative work for emails continue to encounter.

We’ve come a long way from using Microsoft Word email templates, and designers today are doing phenomenal work within the tiny borders of an email client. The problem? With so many different modern email platforms available, and none following any common set of standards in the way they read, interpret, and display emails, designers are facing a dozen-times amplified version of the Internet Explorer vs. Firefox vs. Safari war that continues to roar on today (though we’re much closer to finding a common ground now). Whether the reader is using Gmail or Hotmail, Outlook or Thunderbird, emails just aren’t performing consistently. Imagine deploying a marketing piece and never knowing how it will look to your audience. And this is just from the perspective of the sender - consider the accessibility issues that riddle the readers.

Having done my fair share of email templates for clients in recent years, I can understand the cries of email designers everywhere. And so it was a relief when I stumbled upon the Email Standards Project. From the website:

The Email Standards Project works with email client developers and the design community to improve web standards support and accessibility in email.

Launched in November, the Email Standards Project is an advocator of the establishment of common standards for emails, and is probably the closest thing there is to a regulating body in this field. The site even offers a helpful rating system of various email platforms based on its own acid test.

The winners? Thunderbird, Windows Live Mail, and Yahoo! Mail among a few others. Meanwhile, Gmail, Lotus Notes, and Outlook trail at the bottom of the performance rankings.

If we want to make the same progress with emails as we have with website standards, it’s important to spread the word and show your support. The Email Standards Project lists a number of ways that you can share your support, with blogging and linking to the site being two easy ones.

Read more about the project and why email standards are important on the Email Standards Project website.

Leave a Comment

Tags: , , ,