I don't.  I mention this in my contract to clients.  If they request support for IE6 I will add it in.
I would only advise a client to have support if I feel their target market is likely to use IE6.

If I develop a site without support and then find out in the analytics that there is a high percentage of people 'trying' to use the site with IE6 I would add support later on.

I would charge more for IE6 support.

No, I don't. It's a waste of time.

I work in the Web Development team for the British children's charity Barnardo's and can confirm that yes, we do still support IE6 in new projects. Having said that, we will be very happy when the day comes that this ancient web browser is finally obsolete.

I think it depends on what kind of site im creating, if it's a design related site I wouldn't even think about it. Most people who use those sites, update their browser. But if I was doing a site for a general subject where casual internet users may use the site I would try to support it as much as possible

Kinda depends on each project... You can't really expect a client to pay for browser support... They likely won't understand it on a high enough level and they will just think your trying to scam them out of more money... It makes you look unprofessional... I prefer the approach of not trying to make it look the same in every browser unless it's broken In IE6's case... Then if your client asks you can give the honest answer of we do support IE6 however we don't spend extreme amounts of time on an outdated and dying browser if the issue is minor. This shows that you are aware of browser issues and that you do care what it looks like in IE6 because like it or not a hell of a lot of people still use it so you can't just ignore it.

Boag World said it best. It's best not to try to force a design into a browser, but rather work with what the browser offers. This is the best advice I have ever had and best advice I have ever given to a client.

You will find yourself spending less time in your IDE and more face time with your client and future clients. It's important that you support all web clients (even Lynx), but this doesn't mean that they should look the same in all browsers. I think it's ridiculous to try to force a client to conform to your standards.

Most visitors will never compare the site in side by side browsers, so the need to obsess about rounded corners, for example, in IE at all is a waste of time. Really just give them the content they desire in the context the browser will support and you will have happier clients and be able to sip on some lemonade when the day comes to a close.

boagworld.com article

No, and we have added a clause in our contracts letting clients know that support for IE6 would incur additional dev fees.  I personally think in order to keep the industry moving forward, as developers we need to make sure that end-user demand for the newest and best solutions stays high.  Supporting a degraded platform just enables lower standards for production, deployment, and usability.  I also think dial-up, playstation 2, analog watches, and cars that can't park themselves should not be supported anymore as well. Ha.

I do, but on a case by case basis. I look at the client and their industry/target market. Then dig into what browser that demographic uses. It's not a rule set in stone, but more of a rule of thumb that I use. It doesn't matter how much I detest IE6, if the client and target market use IE6 then I want to make sure the site degrades properly for IE6 at a minimum. I do have a voice in the back of my head that keeps saying "we are so close to being rid of IE6. Hang in there just a bit longer..."

We dropped support for it by default, but offer it for an additional cost.

I bill troubleshooting time hourly for IE6. I try my best to advise clients against spending the money.

It depends on the client.  If their analytics data shows that a significant number of their visitors use IE6, it's a no brainer, but I will also throw up an 'upgrade to a better browser for free' message and explain to the client why this is beneficial to everyone.  Also, if they're a charity or government office then yes, I'll pitch and quote to include IE6 support.

Otherwise, I don't support it, and I make it very clear to the client at the outset why I don't; if they still push for it I'll charge them a premium.

With the release of IE8, I have stopped supporting IE6 stating IN THE CONTRACT that I only support the 2 latest versions of all browsers. Win!

Definitely. If you're in a professional environment ... You have to support it. Looks at your analytics - and you'll see that unfortunately there is still a large percentage of people using IE6.

Unfortunately yes - always for the lowest common denominator.

No! Unless client specifically request that.
Anyway, I do detect IE6 and show a page with explanation on why IE6 is unsecure and how much headeach it give to web professionals with links to update or download other browsers.

No, ie6 is dead. I think the ie6 users need to "know" that your browser is old. If we still supporting it they never going to understand why ie6 is so hated by developers, and never goes to update it.

I design my sites to suit IE7 and up, Chrome, Safari, and Firefox. If it works in IE6 after that, then yay! If it doesn't then they can suffer.

For a brand new project? - No.

If client wants basic IE6 support with banner to users indicating they are getting the downgraded version due to IE6 and we recommend upgrading (with links to IE8,Firefox,Safari, Chrome) - will add for an additional fee.

For a new "iPhone", "HTML5 app", or other uber cool Web App type project - IE6 is off the table with explicit zero-IE6 support.

The signup/login page indicates that IE6 is not supported at all (and won't ever be) and application entry is blocked.

Note: For users with Google Chrome Frame installed access is granted

Yes "I do" the problem that ie 6 has is that it wont support advanced browsers but we can achieve it with some hacks or js. For me its one of mistake of Microsoft that they didnt took care of it or didnt upgrade it well. They just dropped the support and went to the next level. We need to support it another 2 or 3 years cause of most people still using it in their PCs.

Thanks
Ravikumar V.
Www.ravi.uxdsign.com

No, not even google supports it!

Yes to a certain point. You can use to much time to get it pixel perfect in IE6, not that many clients are willing to pay for that.

No we don't, unless it is specifically requested...even then we try & avoid it at all costs

No. And neither should anyone else honestly.

I no longer have been supporting it. I've been charging extra if the client needs IE6 compatibility.

No. I will occasionally redirect IE6 users to a nice static page
that shows the advantages of updating their browser (including simple
steps how to upgrade). That seems like enough support to me.

Yes, I always support IE6. What a sorrow.
But one day....

Yes, always worry about this towards the end of finishing the project though (depending on target audience).

I support it to the point that the site works reasonably well, but not 100%.  I also throw up a "you're using IE6, please get with the times" warning.

Yes - I work for local government so we MUST make sure IE6 is supported

No - Instead it's more helpful to have a "reset" css style sheet and some javascript to fix the nightmare that IE6 can be.

Ask client and charge more if he want it.
But usually when I'm working on personal projects I don't support IE6.

No