It’s a question that I often find people asking and unfortunately there is no right or wrong answer as it can vary from site to site depending on the market and the types of users it attracts, however there are usually similarities that are consistent amongst users of the web.
I’ll be discussing this topic by using the statistics captured from this site as a discussion point but please keep in mind that this site will mainly attract people interested in the latest technology and will more than likely keep their browser up to date.
The table that follows shows the total usage of browsers for this website:
| Browser | No. of Users |
|---|---|
| Firefox | 60% |
| Internet Explorer | 26% |
| Safari | 6% |
| Opera | 4% |
| Camino, Mozilla, Konqueror | 4% |
Looking at these stats more closely, Camino, Mozilla, Konqueror, Opera, Safari all seem to use the latest versions of the browser. In Opera’s case 22% of users were even using Opera 9.5 which is only in Alpha stage of testing. Firefox is slightly different in that some people are still using version 1 or 1.5 but the very latest version of Firefox 2.0.0.6 accounts for 91% of my users so it’s fair to say that most Firefox users also keep up to date.
So that just leaves Internet Explorer. There’s a lot of talk in the industry, about dropping support for Internet Explorer 6 completely and ignore testing on this outdated, troublesome browser but I disagree and here’s why.
The table below shows the split of Internet Explorer users on this site:
| Browser | No. of Users |
|---|---|
| Internet Explorer 7 | 56% |
| Internet Explorer 6 | 44% |
Out of all Internet Explorer users on this site the divide between IE7 and IE6 is almost equal. That means that there’s more than 10% of users still using Internet Explorer 6!!
As I mentioned earlier, this site probably receives visits from people who are quite up to date with technology yet there’s still a significant amount of users on IE6 so I’d expect this figure to be much higher for less technical websites.
So which browsers should I test on?
Whilst the stats on this side maybe skewed slightly, they do demonstrate pretty clearly which browsers need to be supported.
- Firefox – Whilst it’s leading the way on this site, it’s still someway behind Internet Explorer in the browser market but definitely needs supporting.
- Internet Explorer 6 and 7 – Is still the leader in the market and unfortunately IE6 i likely to be around for sometime yet especially as IE7 is unavailable for any operating system older than XP.
- Safari – The leading browser on the Mac.
- Opera – Whilst it’s not up there with Firefox in terms of usage, it does have a user base large enough that needs supporting. It’s one of the leading browsers using the latest web standards so there isn’t really any reason not to support it.
- Konqueror – Arguably leading the way with web standards and was the first browser to implement all the CSS3 selectors.
There are other browsers as mentioned before including Camino, Mozilla, Netscape but these all use the same rendering engine as one of the above so probably aren’t worth testing on there own.
What about older versions of Internet Explorer
Internet Explorer 5.0 and Internet Explorer 5.5 still have users despite the stats from this site showing that it doesn’t receive a single visit from them. However, in my experience, there are very few people that do use either of these browsers and therefor it’s debatable as to whether it’s worth checking for errors in them especially as they can cause havoc with the broken box model due to rendering in quirks mode.
However, my advice would be to ensure that any site developed does render and work correctly for these two browsers. Whilst it may be difficult to aim for pixel perfection, it’s not hard to at least make sure the site works correctly and doesn’t do too bad a job of rendering.
Any other considerations
It’s also worth testing in a text only browser like Lynx, not only for people who may be using a text only browser but it can also help raise accessibility problems with the site.
Mobile devices may also be worth considering especially as more users begin to use these types of devices for browsing the web.
Summary
It may sound a little daunting having read this post and realising that you should be supporting IE6 and 7, Firefox, Safari, Opera, Konqueror, Text-Browsers and Mobile devices but as long as you stick to using web standards whilst writing Valid HTML and CSS then, Internet Explorer 6 problems aside (which are well documented and fixable) you shouldn’t find too many problems creating a cross browser experience that is consistent for all users.

I believe that the next version of Konqueror is to use the WebKit engine instead of KHTML, so testing on Safari should take care of it.
FWIW, I always code for Firefox, knowing that should pretty much take care of Safari and Opera too – thank god for web standards! Then I test in IE7, then start writing conditional comments for IE6.
I use the same method as well Peter, although I would encourage less experienced web designers to test as they develop each component of a page.
Through experience it’s easy to learn that putting a float and left margin will create a double margin bug in IE6 or that using overflow on parent’s of float’s won’t work in IE6 and height: 1%; will be required to trigger haslayout but for beginner’s it’s vital to fix problems as they arise so that they aren’t overwhelmed by browser bugs.
Good news on the Konqueror front if it does use Webkit in future. The code I develop does usually work in Firefox, Opera, IE7 and Safari without any testing so I usually presume it’ll be fine in Konqueror anyway (maybe wrongly?) but it is worth considering if there are lots of discrepancies in a design within the modern browsers to check Konqueror as well presently.
I develop with Firefox (webdev+validator extensions), crosscheck with Opera and the W3C validator, and finally I make it work in the current and previous IE version via override style sheets (loaded with conditional statements) if necessary.
So, the user either needs to use a standards compliant browser or a non ancient version of IE. If they aren’t, they are used to broken websites anyways.
I found a great table at Yahoo! Dev Network (Yes, there’s one!). They use the term “A-Grade browsers” and claim to fully support them. It’s quite good for reference (they got IE, FF Opera and Safary), and I use it for development purposes.
I use Opera 9.5a and I’m getting very annoyed by services “for IE or FF” only. There’re quite a lot of Google products which don’t work smoothly on Opera, or not supported at all.
By the way, MS Silverlight doesn’t support my browser, too.
In addition to covering the basics with HTML and CSS validation I second the recommendation for using Yahoo’s Graded Browser Support Chart.
Yahoo keeps this list updated to reflect the most used browsers across its sites, which probably is a better sampling of the “average user” than you’d get on blogs with a technical audience. Yahoo classifies browsers into three categories: A, C and X grades. A grade browsers are the mainstream browsers and are always tested against, while a small sampling of C grade browsers are tested. X grade browsers are assumed to provide basic support for, but they aren’t really tested against.
Hi Dave and All,
Which browsers to support? As many as possible right?
I find that I don’t have too many problems providing for the 5 major browsers…
I generally develop using FF and cross reference using Opera.
These days though, I’m more interested in providing for mobile browsers because I believe mobile is the future of the web.
Regards
Ade