With the constant release of new browsers and newer code standards there is still a majority of web users who stick with outdated and unreliable browsers. Worse yet, there is no end in sight for old software (Internet Explorer 6) to die. How can anyone decide what code to use during a design? Luckily, there are a few easy considerations when preparing for cross browser compatibility:
- The site does not need to look the exact same in every browser
- Each browser interprets web code differently. Trying to code a site to appear the same in all browsers is a tall, if not impossible, task.
- Limit the hacks
- While there is a need to use an IE fix every now and again (for example, a transparent PNG), try to limit the practice. Instead consider the first rule above.
- A visitor should not need to have a specific browser
- Nothing looks more amateur than a site saying “this site requires Firefox for the best experience.” (one exception would be an advanced web application)
- Web designers: Charge additional for IE6 compatibility
- There is no secret that coding for Internet Explorer 6 takes much more time. Why should this cut into your overall profit? Instead explain to your client (in layperson’s terms) how an overwhelming amount of users have yet to upgrade and it will take X additional hours to make the site compliant for IE6.
- Ultimately, strive for validated code
- In theory, if a site validates most browsers should display it correctly. Besides, there is little excuse not to have validated code.
In summary, when coding your site consider that it should work in all browsers however, each browser can and most likely will output a different experience.
