Here's an example from a recent template-building project for a major online retailer.

Often when I've found myself working in a busy web production environment, things like semantic Html markup and efficient, well-structured and logically named Css rules seem to be low on the priority list (as long as things look ok on FF3, IE 6 and IE7). In fact there may be a lack of awareness as to how much these practices contribute to workflow and make maintenance easier, as well as making the page load faster.

What is the aim of semantic Html?

Here are some great tools and links for ensuring that web pages work across a variety of browsers. The depth of testing of course depends on the type of traffic and scale of the project. In most cases testing for IE6, IE7, IE8, FF2, FF3, Chrome and Safari is going to be sufficient. Heavy traffic sites, .org or .gov domains and sites with specific usability concerns may need more!

Tools of the trade:

Use notepad++ instead of Dreamweaver

Firebug
Web Developer Tools
Dust-me Selectors
Resize Window
SenSEO
Google Semantics

Html emails require a mixture of tables (an otherwise largely obsolete layout method, now replaced by css), remote images and inline css styles.
Many people misunderstand the correct way to design and code a cross-client compatible Html email, and ensuring across the board support for all your recipients can be a detailed task!