We're still validating against IE6 / IE7. My process is basically this: reset.css + 960.gs Build site entirely in Chrome (dev channel) Make sure it work

We're still validating against IE6 / IE7. My process is basically this: reset.css + 960.gs Build site entirely in Chrome (dev channel) Make sure it works in IE8, turn on compatibility view ensure it works there (usually a few fixed needed for IE7). Open it up on iPad / iPhone and ensure that works (usually no issues, somtimes need to set min-width on body) Then pop open FF 3.0 and Safari just to make sure there are no issues (Sorry Opera folks, you don't factor into my process) I could care less what the standards say, no customer cares, they just want to open it in the browser of their choice and see a working site. This new process makes a lot of sense as what you can use depends primarily on the browser demographics of the site and what people are willing to forgo to support IE6. It also meshes well with the release process browsers except for IE / Safari are moving to which is continuous release. You're always going to be limited in what part of the spec is 'valid' based on the browser demographics of your site, because every browser implements 80-90% of the spec.