Mark Wyner Design

Extreme Email Makeovers Vol. III: EIU Alumni Association

Published April 11, 2007

Welcome to the third episode of our Extreme Email Makeovers series with Dr. Mark Wyner. We’ll be running a series of email makeovers to help illustrate best practices for email design, layout and construction. Dr. Wyner will assess an existing email newsletter for ailments which can easily be cured with treatments in modern “medicine.” A patient’s vitals will be provided (email intent, target audience, etc.) and a diagnosis will be revealed. Finally a cure will be outlined, complete with a brand new email template designed and built by Dr. Wyner.

The Patient

The Alumni News Bulletin is a monthly email-publication for Eastern Illinois University (EIU) Alumni Association. The newsletter covers (a whole lot of) information about the EIU-campus, alumni events, etc.

Email Clients

As this newsletter is deployed by an educational institution to a subscriber base of graduates, it can be assumed that a general audience of recipients are employing a broad array of email clients such as:

• Apple Mail
• Thunderbird
• AOL
• Outlook Express
• .Mac
• Yahoo
• Gmail
• Windows Live Hotmail
• Hotmail
• Outlook

Note that while it is likely most of the alumni are using personal email addresses to receive the bulletin, some of them may be using typical office-clients such as Outlook.

The Diagnosis

An initial assessment exposed an array of potential infirmities, but an exploratory surgery would be necessary to grasp the full scope of the patient’s condition. Upon investigation, it became clear that reconstructive surgery would only be the beginning of treatment which would be necessary to stabilize the patient’s health.

Design Ailments

The EIU Alumni Association has quite a lot to tell each month, and they sure pack it in. While very informative, this email is quite extensive for a single message. And for recipients willing to read a 1,700-word email, the visual design left something to be desired. Dr. Wyner addressed the following disorders as part of his treatment:

[fig. 1]

1. Graphical masthead (title and issue date vulnerable to possible omission).
2. “Web version” link placed below large masthead-image and in the right-column of a two-column layout (very low in the hierarchy).
3. Lengthy, redundant information consuming valuable real estate (albeit useful, it is more of a utility statement).
4. Secondary information placed in most important corner of layout, including gratuitous use of graphical text (vulnerable to possible omission).
5. Overwhelming number of events (distracts attention from events on the immediate horizon).
6. Photos with graphic borders/shadows (bandwidth-heavy and labor intensive to create).
7. Excessive number of story previews (decreases potential for quick scanning).
8. No visual separation between stories and utility information about the association (blends recurring information with news).
9. No link with “forward to a friend” feature.

It should be noted that this template was not only CAN-SPAM Act compliant (reference item 9 in fig. 1), but the patient went the extra mile for good health in adding a link to their website as well as two telephone numbers. Nice work!

Markup Ailments

When I opened up the patient’s code, it became clear that there was a lot of work ahead to stop internal bleeding. Following is a list of life-threatening ailments which required attention:

• CSS was in short supply, and only half of it was embedded (external style sheets are scarcely supported, trigger many spam filters and are most often stripped altogether).
• The CSS which was used utilized a naming schema with no reference to presentation (.style13, .style 14 and so on) creating an ambiguous environment for third parties attempting to format content.
• Tables were used for all aspects of layout, including use of 1x1 pixel “spacer GIFs” (an antiquated technique which increases file-size and decreases accessibility), and many FONT tags were used throughout.
• ALT text was not used for graphical text.
• Lack of semantic markup (unnatural and inconsistent paragraphs, subheads, etc.).

Email Vital Signs

• Standards-based markup: no
• CAN-SPAM Act compliance: perfect
• File size: 56KB

The Cure

With a clear diagnosis a treatment was obvious. A visual-design overhaul would help heighten the attention of the patient’s audience and enable content editors to easily create new editions. Improving the information design and using semantic markup would ensure readability and accessibility for all recipients. Finally, a depressant would be prescribed to reduce the amount of information exhibited in each edition.

Treatment

• Text-to-HTML: the graphic text was converted to HTML text to ensure accessibility and content readability, improve ease of use for content managers, reduce the overall file size and decrease the possibility of spam filtering.
• Link to website version: while the original template did include a link to a website version of the email, its placement was less than optimal. Moving this to the beginning of the template ensured it would be visible in the very scenario it is intended to reconcile.
• Improve information design: the creation of two columns—one for primary information, and another for secondary information—and placing the former first in the hierarchy (left column) would strengthen the overall information structure and ensure fluid readability in the broad array of email environments.
• Reduce information overload: rather than printing previews to every news story from the monthly cache, only four stories are featured with previews. Then a list of titles for the remaining stories are printed under the subhead “additional news.” The list of upcoming events was also optimized to reduce clutter and bring focus to those in the immediate future.
• Optimize visual treatment of contextual photos: using CSS borders is a light-weight and manageable solution to the approach of creating photos which emulate three-dimentional objects.
• Separate stories from utility information: recurring information about the association and the university was segregated from the newsletter stories to increase reading efficiency for monthly readers.
• Permission reminder: a preface was integrated to assist with previews/snippets and to help reduce spam flagging.

The doctor performed one final procedure which would serve the needs of both appearance and character:

[fig. 2: before (top), after (bottom)]

Dr. Wyner noticed how the patient used a seasonally-relevant photograph in each edition of their newsletter (fig. 2, top) to help capture the relevance of the moment. He knew could make a few minor hexadecimal changes to the CSS and change one image SRC value to create a unique template for each season of the year. With that, we are happy to announce the birth of quadruplets (fig. 2, bottom)! Meet Spring, Summer, Fall and Winter.

Email Vital Signs

• Standards-based markup: yes
• CAN-SPAM Act compliance: perfect
• File size: 17KB (30% of the original size)

Before and After

Let’s review some screen shots illustrating some key benefits of this surgery.

Thunderbird: plain-text view

[fig. 4.1: before (left), after (right)]

One of the most detrimental aspects of the markup was the lack of semantic structure. Many paragraphs were created with BR tags instead of the semantically appropriate P tags, and subheads were created with CSS-styled P tags instead of semantically appropriate header tags such as H2. Coupled with a lack of ALT text and gratuitous “spacer GIFs” the problem is quite serious.

These screen shots were taken in Mozilla Thunderbird in plain-text view. Looking at the original template (fig. 4.1, left) we can see how the antiquated markup and gratuitous images render the email scarcely readable for those using text-based clients.

Note how in the new template (fig. 4.1, right) the preface text is visible first in the hierarchy, the title and issue date are immediately obvious, ALT text for the photos are clearly exhibited and paragraphs are properly formatted.

A word about plain-text alternatives

Some email clients (such as Thunderbird) offer a preference to disable HTML rendering even though they are an HTML-capable. Many other email clients—primarily mobile devices and screen readers—simply do not support HTML, and instead look for plain-text alternatives. It is always a best practice to send multi-part emails (HTML and plain-text versions as a single package) to ensure that a properly-formatted plain-text version is available to those who can’t (or choose not to) render HTML. However, if for whatever reason you are unable to send a multi-part email, the aforementioned process of utilizing semantic-markup will help your content survive the evolution from HTML to plain-text if rendered as such.

.Mac: images enabled

[fig. 4.2: before (left), after (right)]

These screen shots were taken in .Mac with images enabled. Looking at the original template (fig. 4.2, left) we can see some significant problems:

• An inappropriate marriage of color and background declarations exhibits dark text on a dark background (including nearly-undecipherable links and subheads).
• Secondary content (alumni links) take center stage while important content is forced downward.

Note how the new template (fig. 4.2, right) retains its formatting and consequently retains its readability.

Opera Mini webmail: images enabled

[fig. 4.3: before (left), after (right)]

These screen shots were taken in Opera Mini webmail with images enabled. Looking at the original template (fig. 4.3, left) we can see some significant readability issues:

• Many small-screen devices reduce large images to the width of the screen. In this case the graphic title and issue date are reduced to a size which is nearly illegible.
• Lack of semantic markup clumps all fake paragraphs into a single paragraph.
• Placing secondary information in a left-hand column and primary content in a right-hand column, forces important information (including “web version” link) down in the hierarchy.

Note how the new template (fig. 4.3, right) addresses these issues:

• Use of HTML text for the masthead ensures the title and issue date are readable and immediately obvious.
• Semantic markup clearly differentiates subheads from paragraphs.
• Important information appears first in the hierarchy, offering immediate help (preface) and value (first story) for the reader.

Opera Mini webmail: images disabled

[fig. 4.4: before (left), after (right)]

These screen shots were taken in Opera Mini webmail with images disabled. Looking at the original template (fig. 4.4, left) we can see that the aforementioned issues (with images enabled) are made even worse with images disabled. The primary issue is that with no ALT text for the masthead image and only sporadic implementation for the links/subheads, the content becomes practically unreadable. While some of the text is indeed legible, it is ambiguous without subheads and the presence of a title.

Note how the new template (fig. 4.4, right) is very readable with information which retains nearly all of its formatting.

Outlook 2003: auto preview

[fig. 4.5: before (top), after (bottom)]

These screen shots were taken in Outlook 2003 using its “auto preview” feature. Looking at the original-template preview (fig. 4.5, top) we can see that because Outlook is using the image source for its auto preview, it offers literally no information about the email itself.

Note how the new-template preview (fig. 4.5, bottom) at least assures the recipient that s/he is a subscriber.

Gmail: snippet

[fig. 4.6: before (top), after (bottom)]

These screen shots were taken in Gmail using what it refers to as “snippets” (serves the same purpose as Outlook’s auto preview). Looking at the original-template snippet (fig. 4.6, top) we can see that Gmail has plucked the ALT text from the images in their order of appearance. Given that ALT text was used sporadically, the preview is quite meaningless.

Note how the new-template snippet (fig. 4.6, bottom) at least assures the recipient that s/he is a subscriber.

Thunder screen reader

Link 1: ~alumni
Link 2: Eastern Illinois University Home
Link 3: s://www.give2eiu.eiu.edu
Link 4: www.eiu.edu/~pubaff
Link 5: EIU Alumni Association Membership Page
Visit the
Link 6: events page
for more information and registration.
February 17
Link 7: Alumni Reception
Camelback Inn,
Scottsdale, Ariz.
February 24
…(cont.)…
Field Narrowed to 16 for EIU’s President Position

You are receiving this email because the email address [email] was subscribed to the EIU Alumni
Link 1: email list
Having trouble reading this email? View it on our website.
Page Headline: eiu alumni newsletter
march | 2007
Field Narrowed to 16 for EIU’s President Position
The field of presidential candidates has been narrowed down from 58 to 16 as the search for the next president of EIU continues. Robert Webb, the Presidential Search Advisory Committee chairman, said the committee has begun conducting reference checks on each of the 16 remaining candidates.
During their Feb. 15 meeting, committee members are to discuss those findings and reduce the field to five to eight candidates who will be invited to confidential preliminary interviews. After those interviews are complete, finalists will be invited to campus for extensive interviews with the EIU community.
For up-to-date information on the presidential search, please
Link 2: visit the presidential search page.

These transcripts were captured with the screen reader “Thunder” as it read the two templates. Looking at the transcript from the original-template (top) we can see that the primary content is not revealed until well into the email (59 lines to be exact). We aren’t even given a title or issue date because of the absence of ALT text.

Note how the transcript from the new-template (bottom) shares the title and issue date on the fourth line, and immediately continues to the primary content.

Summary

Dr. Wyner approached treatment from many angles. Speech therapy (accessible/semantic markup) to help the patient communicate via all email clients, extensive cosmetic-surgery to make the patient visually appealing (because when we look good, we feel good) and reduction of fat (bulky presentational markup) will make the patient’s heart and lungs (bandwidth) happy.

Return to: top of this article | index of articles