Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > CSS

Planning for and Managing Browser Support

With a flurry of new browsers hitting users’ computers and mobile devices this year, everyone involved with the Web has had to scramble to ensure that their sites are compatible with the latest and greatest. This has left many Web professionals and business teams wondering, “What browsers should my site support?” Kimberly Blessing helps you answer that question.
Like this article? We recommend

Once upon a time, the Web was littered with sites boldly proclaiming “Optimized for Browser X” and “Sorry, only Browsers X and Y are supported”. It took a while, but Web professionals helped tear down these roadblocks by demonstrating that broad support for browsers meant more business and more engaged users. Most businesses have learned to like Firefox, Safari, Opera, and Chrome as much as they once liked Netscape Navigator and Internet Explorer.

But with a flurry of new browsers hitting users’ computers and mobile devices this year – including Internet Explorer 8, Firefox 3.5 and 3.6, Safari 4, Opera 10, and multiple releases of Google Chrome – everyone involved with the Web has had to scramble to ensure that their sites are compatible with the latest and greatest. This has left many Web professionals and business teams wondering, “What browsers should my site support?”

Yes, these are the times that try the patience of Web designers, developers, quality assurance analysts, customer support specialists, and – most of all – our users. Web professionals who’ve been around this block before know enough and can improvise a plan for supporting new browsers, but still, many don’t prepare a formal browser support policy until it’s desperately needed.

There’s no time like the present, so let’s get started!

Setting a browser support policy

Browser support policies vary from site to site, company to company. It’s important to come up with a policy that reflects what your users expect support for, as well as what you and your Web team can support.

While some Web site owners assume that the whole world uses the same browser that they do, and couldn’t fathom using or supporting any other browser, we Web professionals know better. However, we also know that there are limits to supporting different browsers, so supporting every single browser ever made is also not practical. So where do you start?

Know your audience

If you already have a site up and running and are trying to start a browser support policy, you should focus on making the best experience for your existing users. Finding out which browsers are already being used to access your site is the best way to determine which browsers you need to support. Usually this data can be obtained by reviewing your site’s log files – a rather messy affair to do by hand. However, there are a variety of tools which can more easily crunch the numbers for you.

One popular log file analysis package is AWStats. Many web hosting providers include this software in their control panels, or you can download and install it yourself. AWStats will examine your Web server’s log files and give you a breakdown of which browsers were used to access your site. An example of its browser report is shown in Figure 1.

Figure 1. AWStats Browser Versions screen.

If you don’t have the ability to install or run a log file analysis tool on your server, you may want to look at a hosted analytics solution instead. Both free and paid solutions are available, and implementation is as easy as calling a third-party JavaScript file on each page of your site.

Google Analytics is a free and easy way of getting started. Once you sign up for an account, you’ll be given some JavaScript to embed in your site’s pages; the scripts will run when users access your site and will send information about the user’s browser back to Google. An example of a Google Analytics report is shown in .

Figure 2. Google Analytics Browser Overview screen.

These tools will give you reports for any amount of time. You will need to run one quarterly report for the past three months to set a baseline of browsers used and their overall popularity; then run a monthly report for each of the past three months to take note of any trends, such as adoption rates of a new browser.

If you’re starting a new site and thus don’t have any visitor data to analyze, you may want to refer to some of the Web-wide metrics reported by sites like and While your site’s statistics will surely vary from these averages, they’re a decent place to start.

Narrowing the list of supported browsers

Ask an uninformed Web site owner which browsers they want you to support and you’re likely to get a response of, “All of them”! But most Web professionals know better than to agree to fully supporting all browsers on all platforms.

Sure, you could spend hours searching blogs and articles for techniques to make every design feature or behavior work identically across browsers and platforms. You’ve probably tried this once or twice, just to test your chops, right?

But, as your stats will likely show you, users will ping your site with about 20 to 40 different browsers (between versions and platforms) per month – for large portals, this number is easily over 200 browsers per month! (Did you even know there were so many browsers?) Realistically, you want to be putting effort in to the browsers most commonly used by your audience.

For example, if 30% of your users are still on IE 6 and only 5% are on IE 8, you still need to code some of your features for and test against IE 6. On the other hand, if you have only 2% of IE 6 users, you may be able to sunset support for that browser.

Ultimately, which browsers you decide to support is up to you and your Web team – but I suggest starting with the browsers which make up 80-90% of your audience. This will likely include some versions of Internet Explorer, Firefox, and Safari. Still, even this mix of browsers can be difficult to support, so how can you narrow that list further?

Browser ‘support’ is not always equal

Assuming your site is already built to follow best practices such as POSH and progressive enhancement – concepts explained in this chapter from Adapting to Web Standards – your content is likely accessible to most or all browsers in common use. However, your design or scripted behaviors may not look or work as expected across all browsers and platforms, and this is the cause of most browser support grief.

For years, large sites had internal or unofficial policies regarding differing levels of support for browsers. These were based on the age of a browser, the number or percent of users on a browser, or the set of features supported by a browser. Yahoo! let the cat out of the bag a few years ago when it publicly documented its Graded Browser Support policy.

Today, it’s much more common for smaller sites to do the same. This allows Web professionals to invest their time more wisely – no more investing 80% of your work to support 20% of your users.

For example, if you use rounded corners extensively in your design but have a small IE audience, then you can consciously decide to limit design feature support for IE, and just use the CSS border-radius property for the browsers which support it. Or, even if you have a large IE audience, you can stick to the border-radius method and message IE users to upgrade to IE 8, or use an alternate browser, for a more refined experience.

Documenting your browser support policy

If your browser support requirements are fairly simple, you may be able to get by with a short statement, such as the following:

All content, design, and behavioral features of this site must work without issue on Internet Explorer 7 and 8 on Windows, and Firefox 3.x on Windows, Mac, and Linux. (Feature support on other browsers and platforms may vary.)

Large, feature-rich sites and Web applications will typically have a much more detailed browser support policy, like the matrix in Figure 3.

Figure 3 Detailed browser support matrix.

Ultimately, the way in which you document your browser support policy is up to you – just make sure the documentation is detailed enough for everyone to set expectations on how their work will be impacted and understand how users will be impacted.

Also, be sure to communicate the policy to your peers and your boss (or client) and take the time to answer their questions, so that everyone is on the same page. Of course, you’ll want to message users as well, so plan those workflows and designs carefully! In particular, if you need users to upgrade for better feature support, take the time to carefully craft messaging and support documentation – otherwise your users may stop visiting your site and could seek out a competitor’s site.

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive:

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020