How far backward should we still design for?
To answer this question you also need to examine how far forward you need to design for. In a day when HTML5 has taken a few stumbles, and people still use IE6, it is often hard to determine the middle-ground.
The real answer is to consider your audience. When determining browser compatibility, the use of analytic software is vital. I am a data junky, so I find analytic software to been geekishly fun.
You can install a great tool called Google Analytics for free. (http://analytics.google.com) It is as simple as signing up your website and pasting a code on the individual pages. Now the data harvest begins!
From Google Analytics you can determine traffic sources, operating systems, and more importantly browser version. On most of my sites Internet Explorer seems to be king. This poses multiple problems. IE versions have very different abilities. The lower the version, the less the compatibility with coding standards. While HTML5 is not considered a W3C web standard yet, older coding elements, such as advance placement DIVs, do not work in anything lower than IE7. Worse yet, their usability in IE7 and up is questionable.
When you have a lot of outdated IE users, you have to cannibalize a lot of your coding ambitions. A year ago I tracked a site that was primarily receiving users of IE6. It required a lot of old school setup, including designing with tables. One thing I do, because the clients rarely notice, is install a script from Browser Update (http://www.browser-update.org). It is a lightweight script you can install on one or all of your pages, which reminds people when they have an outdated browser. It sets a cookie, so the users are only notified when the cookie expires.
Beyond IE6, I also have qualms with Apple. While learning jQuery is fun, I really am perturbed by the lack of Flash compatibility in Apple products. In a day and age when machines, bandwidth, and design styles could all incredibly utilize/benefit from Flash, it is simply not supported. The new rule of Flash video is this: If you can’t interact with it, pre render it as a video. What worsens this is there is no one video codec which is accepted by all browsers. In order to ensure your animation/video is viewable on all platforms you have to upload three separate versions of the file.
When creating interactive design elements, UI, you need to make a choice between Flash and jQuery. While Apple products do not work at all with Flash, Internet Explorer does not work with heavy use of jQuery. I’ve seen entire pages broken in IE due to its inability to fully process multiple jQuery scripts.
With the (quasi) recent advent and stumblings of HTML5, it is hard to recommend as a primary language. I use HTML5 elements where I can, but I always ensure there is a catch. HTML5 introduces lighter scripts, faster page processing, and more standardization of elements. Unfortunately, it is not cross browser compatible; for that matter, there are NO browsers that fully support it. It’s a designer’s pipe dream and a good look at where the web is going, but far from practical.
What can you do to incorporate the new with the old? Well one new feature that is fairly well supported is CSS3. A year ago I would have said to stay away, but it has really developed a browser following. While CSS3 doesn’t work the same on all browsers, when it fails it does not break the page. CSS3 allows you to add some interesting effects and animations to your site, including 3-d button rotate. A good tutorial can be found over W3Schools.com (http://www.w3schools.com/css3/).
This is going to be one of my shorter entries, but I hope it was at least somewhat helpful. The main point I am trying to make is to think before you code. Don’t just design blindly, but take into consideration how it will work on multiple browsers. For more information on any of these codes visit (http://www.w3schools.com). To test your own site on multiple browsers sign up for Adobe BrowserLab (https://browserlab.adobe.com/). Good designing to you all!









