Should you price IE6 support as a separate proposal item?

By Deane Barker on September 26, 2008

Along with every Web developer on Earth, I hate IE6. This thing is the cause for so much re-work and so much needless fiddling around.

We had an internal debate here about when to stop supporting it. We didn’t really come to an absolute decision on it, but Joe did come up with an interesting idea:

How about if you put a line-item in a bid for IE6 support? So, your Web site will cost $X, and IE6 support will be an additional $1,500, or whatever.

This could be varied by how complex the design is, and how much IE6-hacking we think we’re going to need to do.

I really think IE6 would come into perspective for a lot of people if they could put a hard number on how much it’s costing them.



  1. I really think we do a disservice to developer, user, and site owner by catering so much to IE6. I think your idea of a line-item bid for IE6 is a good idea (I’d include other legacy browsers too). Perhaps another thing to bring up is the fact the IE8 is around the corner. Of course clients don’t really want a whole lot of version numbers thrown at them…so in simpler terms…spend the money to develop the site for past or the present and future?

    I’d also argue that it’s time to get rid of 800×600 design and even 1024×768…though all those iPhones and mini-netbooks have sort of thrown that idea to the back-burner.

  2. We’ve discussed adding IE6 support as a separate line item internally recently. We hope to be able to do so once IE8 is released. Of course, I’d love to do it as a time & material, not fixed price, line item …

    On our client sites, we’re seeing a roughly 50-50 split between IE6 and 7.

  3. With ie6 still representing 30-40% of the global browser market according to the various stats providers, you’re doing your customers a disservice by eliminating support for the browser.

    Of course, it depends on the site. Sites with a highly technical audience may have lower numbers. Cater to your audience as discussed in relationship to Netscape 4 at

  4. We’re moving to degrading support for IE6 — that is, the site will look OK, but might be missing some graphics or typographic effects. We’re not killing ourselves to replicate the effect of CSS3 selectors, etc, on IE6 browsers any more.

Comments are closed. If you have something you really want to say, tweet @gadgetopia.