Email Graceful Degradation

Definition

Graceful degradation in email design is the practice of building a rich, feature-enhanced email and then systematically applying fixes and fallbacks for clients that cannot support those features. The strategy acknowledges that modern email clients vary dramatically in their CSS support and rendering capabilities, with Outlook's Word engine representing the lowest common denominator while Apple Mail and mobile clients offer near-web-standard support.

In practice, graceful degradation means designing for the best possible experience in clients like Apple Mail and iOS Mail, then adding conditional comments, VML fallbacks, and simplified CSS for Outlook. For example, a multi-column layout with rounded corner buttons and background images might be designed first, then degraded to stacked columns, square buttons, and flat background colours for Outlook. The degraded version ensures core content and calls to action remain accessible.

The approach has fallen out of favour compared to progressive enhancement, primarily because starting with the richest possible layout often creates more bugs than starting simple. However, graceful degradation remains useful when the target audience is heavily weighted toward modern clients and a small percentage of Outlook users is acceptable. Marketing teams sometimes prefer this approach because it prioritises the visual experience for the majority of their audience.

Best Practices

Identify your audience's client distribution before choosing a degradation strategy. If less than 5% of your recipients use Outlook, a degradation-first approach may be appropriate, but ensure those recipients can still read and click.

Always ensure that the degraded version provides a complete experience. Core content, primary calls to action, and essential navigation must function in Outlook even if they are less visually polished.

Use conditional comments and VML as degradation tools rather than enhancement tools. Apply Outlook-specific fixes after the primary design is complete, addressing each rendering issue one at a time.

Test the degraded version before the enhanced version. If the Outlook version is broken, a significant segment of your audience cannot interact with the email at all.

Document degradation decisions so your team understands why certain fallbacks exist. Without documentation, developers may accidentally remove Outlook fixes during refactoring, assuming they are no longer needed.