In my humble opinion though, the solution of simply freezing-out EI6 users is a bit immature. ie6nomore.com does try to address the ‘corporate-user’ aspect of the issue by pointing out that complaints might force an IT department to upgrade workstations however, this is far from an ideal scenario. Besides the decent chance that it won’t work in a lot of cases (the IT departments I’ve known are generally more inclined to say TS than help for example…), the whole strategy is just not that friendly. Moreover, the common user (especially ones who have been living under a rock and don’t realize they should have upgraded) are the most likely to think there is a problem with their computer, connection, or your server if they don’t get the site’s contents; regardless of the fairly clear upgrade notice.

A different solution which I posit is in all ways better is that presented by Andy Clarke of For A Beautiful Web fame. He put together a baseline CSS which can be snapped into any design (some customization is probably good practice, but it’s not even recommended by Andy) which bring the website down to a “content only” level. This formatting allows the IE6 user to still access the content, but obviously miss-out on any design goodness. The result is a usable website that degrades nicely for IE6 but a rich and uncompromised experience for everyone else.

Check out the IE6 CSS at

Cheers,
Evan