<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Standards, Semantics, Accessibility, and HTML Email</title>
	<atom:link href="http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/</link>
	<description>A resource for Web designers and developers to read about and discuss their craft.</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:29:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: What is HTML Email?</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-873</link>
		<dc:creator>What is HTML Email?</dc:creator>
		<pubDate>Tue, 26 Jun 2007 15:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-873</guid>
		<description>lease don’t encourage users to post HTML Email. It’s dangerous, takes up resources, and is not accessible. Even if it can be done correctly, it seldom is. Like putting metal in the microwave. It’s often better to say “don’t” than to teach people to do it properly.</description>
		<content:encoded><![CDATA[<p>lease don’t encourage users to post HTML Email. It’s dangerous, takes up resources, and is not accessible. Even if it can be done correctly, it seldom is. Like putting metal in the microwave. It’s often better to say “don’t” than to teach people to do it properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-872</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Sat, 03 Feb 2007 03:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-872</guid>
		<description>@Gort:  As far as HTML emails are concerned -- maybe.  There are times when it comes down to client orders having to be followed and CSS support just isn&#039;t there as far as email clients are concerned.  The decision by Microsoft to resort to Word rendering in Office 2007 for HTML emails goes to say that things are headed in an awful direction as it is.  I can&#039;t accept it when it comes to the Web, however.  Thanks for taking the time to post your thought.</description>
		<content:encoded><![CDATA[<p>@Gort:  As far as HTML emails are concerned &#8212; maybe.  There are times when it comes down to client orders having to be followed and CSS support just isn&#8217;t there as far as email clients are concerned.  The decision by Microsoft to resort to Word rendering in Office 2007 for HTML emails goes to say that things are headed in an awful direction as it is.  I can&#8217;t accept it when it comes to the Web, however.  Thanks for taking the time to post your thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gort</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-871</link>
		<dc:creator>Gort</dc:creator>
		<pubDate>Wed, 31 Jan 2007 17:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-871</guid>
		<description>I am a UI designer; I espouse the use of CSS and forward thinking markup; however, tables are not dead and are still a reliable construct for getting things done.  CSS still has a way to go before tables are fully written off.  Accept it.</description>
		<content:encoded><![CDATA[<p>I am a UI designer; I espouse the use of CSS and forward thinking markup; however, tables are not dead and are still a reliable construct for getting things done.  CSS still has a way to go before tables are fully written off.  Accept it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-870</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 11 Dec 2006 03:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-870</guid>
		<description>@Justin Kistner:  You&#039;re absolutely right about CSS inconsistencies between clients.  If a client is being completely specific about how they want their HTML email to look then sure, using tables for layout can become a necessity.

@Peter Scott:  You bring up a great point, Lotus Notes is still used extensively, and as a few have said before, sometimes you just have to buckle down and use tables to get something right for a paying client.  Unfortunately that will probably be how it is for some time to come as well.</description>
		<content:encoded><![CDATA[<p>@Justin Kistner:  You&#8217;re absolutely right about CSS inconsistencies between clients.  If a client is being completely specific about how they want their HTML email to look then sure, using tables for layout can become a necessity.</p>
<p>@Peter Scott:  You bring up a great point, Lotus Notes is still used extensively, and as a few have said before, sometimes you just have to buckle down and use tables to get something right for a paying client.  Unfortunately that will probably be how it is for some time to come as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Scott</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-869</link>
		<dc:creator>Peter Scott</dc:creator>
		<pubDate>Thu, 07 Dec 2006 14:05:14 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-869</guid>
		<description>A business email application still in widespread use is Lotus Notes, which will throw your carefully coded CSS all over the show. To achieve any sort of layout which will work across multiple email applications you have to use tables - it&#039;s unfortunate, I know, but utterly unavoidable if you are going to allow Notes users to read your html emails. You also have to use old-style font tags in your markup for Notes - not good news.</description>
		<content:encoded><![CDATA[<p>A business email application still in widespread use is Lotus Notes, which will throw your carefully coded CSS all over the show. To achieve any sort of layout which will work across multiple email applications you have to use tables &#8211; it&#8217;s unfortunate, I know, but utterly unavoidable if you are going to allow Notes users to read your html emails. You also have to use old-style font tags in your markup for Notes &#8211; not good news.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Kistner</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-868</link>
		<dc:creator>Justin Kistner</dc:creator>
		<pubDate>Thu, 07 Dec 2006 07:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-868</guid>
		<description>CSS support among email clients is really poor and inconsistent. I am a huge standards proponent, but HTML emails are no place for positioning CSS. Now, that doesn&#039;t mean you can&#039;t still use semantic markup, but when it comes to layout, tables are still the best for the greatest compatibility.</description>
		<content:encoded><![CDATA[<p>CSS support among email clients is really poor and inconsistent. I am a huge standards proponent, but HTML emails are no place for positioning CSS. Now, that doesn&#8217;t mean you can&#8217;t still use semantic markup, but when it comes to layout, tables are still the best for the greatest compatibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-867</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 04 Dec 2006 22:42:45 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-867</guid>
		<description>@Dan: You&#039;re definitely not alone in your stance, which is exactly why the people behind HTML emails need to ensure that you see a message with the same value as someone who does prefer to read HTML email.

@Michael Chase:  Absolutely... I also remember back to the days of Eudora.  It&#039;s funny how it usually takes the masses a bit of time tor realize that something is causing more trouble than good.

@Mark Reeder: You are absolutely right.  If anybody thought supporting multiple Web browsers was too tough to handle, they shouldn&#039;t be working with HTML email.  Just about every client (Web based or otherwise) will treat an HTML/CSS email differently.  You&#039;re right, sometimes a project will come down to a tabular layout to please a client.

@Russel James Smith: You&#039;re completely justified in saying that you can&#039;t trust CSS to any extent in an HTML email.  Keeping the design simple is essential to a successful campaign.

@Jared Cornwall:  You may be correct in saying that HTML/CSS based emails could become more common and better supported over the coming years, but that is probably quite a way down the line unfortunately.  We can always hope, though.  Personally, I don&#039;t have any experience with Campaign Monitor but the articles posted to the site are often well written and very comprehensive.

@Leonardo Ribeiro:  Definitely, I&#039;ve come across a few &#039;guidelines&#039; for designing HTML emails in that you should keep widths to a number hovering around 560px and a few other tips and tricks.  It&#039;s always good practice to offer a plain text alternative.</description>
		<content:encoded><![CDATA[<p>@Dan: You&#8217;re definitely not alone in your stance, which is exactly why the people behind HTML emails need to ensure that you see a message with the same value as someone who does prefer to read HTML email.</p>
<p>@Michael Chase:  Absolutely&#8230; I also remember back to the days of Eudora.  It&#8217;s funny how it usually takes the masses a bit of time tor realize that something is causing more trouble than good.</p>
<p>@Mark Reeder: You are absolutely right.  If anybody thought supporting multiple Web browsers was too tough to handle, they shouldn&#8217;t be working with HTML email.  Just about every client (Web based or otherwise) will treat an HTML/CSS email differently.  You&#8217;re right, sometimes a project will come down to a tabular layout to please a client.</p>
<p>@Russel James Smith: You&#8217;re completely justified in saying that you can&#8217;t trust CSS to any extent in an HTML email.  Keeping the design simple is essential to a successful campaign.</p>
<p>@Jared Cornwall:  You may be correct in saying that HTML/CSS based emails could become more common and better supported over the coming years, but that is probably quite a way down the line unfortunately.  We can always hope, though.  Personally, I don&#8217;t have any experience with Campaign Monitor but the articles posted to the site are often well written and very comprehensive.</p>
<p>@Leonardo Ribeiro:  Definitely, I&#8217;ve come across a few &#8216;guidelines&#8217; for designing HTML emails in that you should keep widths to a number hovering around 560px and a few other tips and tricks.  It&#8217;s always good practice to offer a plain text alternative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leonardo Ribeiro</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-866</link>
		<dc:creator>Leonardo Ribeiro</dc:creator>
		<pubDate>Mon, 04 Dec 2006 22:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-866</guid>
		<description>I always use narrow widths to fit webmail space and inline css.
I also provide plain text alternative text, but I&#039;m not sure about embedding images.</description>
		<content:encoded><![CDATA[<p>I always use narrow widths to fit webmail space and inline css.<br />
I also provide plain text alternative text, but I&#8217;m not sure about embedding images.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Cornwall</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-865</link>
		<dc:creator>Jared Cornwall</dc:creator>
		<pubDate>Mon, 04 Dec 2006 20:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-865</guid>
		<description>I prefer receiving a well designed HTML email as opposed to basic text. I think HTML emails will become more common and email clients with support creating and receiving HTML emails, eventually.

I also end up using table based layouts with inline styles to make HTML emails work in the widest range of email clients.

The thing that has made my job the easiest for sending HTML email campaigns is using Campaign Monitor (as mentioned). Great tool and good resource for information.</description>
		<content:encoded><![CDATA[<p>I prefer receiving a well designed HTML email as opposed to basic text. I think HTML emails will become more common and email clients with support creating and receiving HTML emails, eventually.</p>
<p>I also end up using table based layouts with inline styles to make HTML emails work in the widest range of email clients.</p>
<p>The thing that has made my job the easiest for sending HTML email campaigns is using Campaign Monitor (as mentioned). Great tool and good resource for information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell James Smith</title>
		<link>http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-864</link>
		<dc:creator>Russell James Smith</dc:creator>
		<pubDate>Mon, 04 Dec 2006 18:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2006/12/04/standards-semantics-accessibility-and-html-email/#comment-864</guid>
		<description>I agree with many of the sentiments behind this article.

But, I&#039;ve worked creating customer marketing emails for various large clients over the last few years and I&#039;m sorry to say I still feel that it&#039;s all but impossible to use CSS to any great extent.

The worst offenders for not supporting CSS are the webmail clients such as Hotmail (Livemail) and G-Mail and when we look at our clients data we often see that as many as 75% of customers are using webmail providers.

Currently when our clients require a grid-layout in an email to display products; going back to tables is the only answer (with of course a text only alternative (usualy sent in a mulit-part message)). I do hope the situation changes in the near future.

To get the ball rolling if somebody could point me at any references that could gave me some amunition for dissuading clients from sending marketing email based on table-layouts I&#039;d be very happy to start evangelising CSS based emails (as I did with CSS based web pages quite a few years back).</description>
		<content:encoded><![CDATA[<p>I agree with many of the sentiments behind this article.</p>
<p>But, I&#8217;ve worked creating customer marketing emails for various large clients over the last few years and I&#8217;m sorry to say I still feel that it&#8217;s all but impossible to use CSS to any great extent.</p>
<p>The worst offenders for not supporting CSS are the webmail clients such as Hotmail (Livemail) and G-Mail and when we look at our clients data we often see that as many as 75% of customers are using webmail providers.</p>
<p>Currently when our clients require a grid-layout in an email to display products; going back to tables is the only answer (with of course a text only alternative (usualy sent in a mulit-part message)). I do hope the situation changes in the near future.</p>
<p>To get the ball rolling if somebody could point me at any references that could gave me some amunition for dissuading clients from sending marketing email based on table-layouts I&#8217;d be very happy to start evangelising CSS based emails (as I did with CSS based web pages quite a few years back).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using xcache (user agent is rejected)
Database Caching using xcache

Served from: mondaybynoon.com @ 2010-07-30 22:13:11 -->