The increasing importance of PSD to XHTML conversion cannot be negated. It is an intrinsic part of Website Designing and holds a heavy weightage. It also goes beyond saying that Internet has spread its root in a diverse fashion and does not limit itself to Home PC and Systems.
The browsers are adding up in the queue, and with the arrival of every new or improved browser, the coding criteria also changes. Earlier the coder has to fix his attention to limited browsers, but the present XHTML coding rules simply outcast any leniency with browser compatibility.
The well known and highly used browsers are IE (with its different versions), Mozilla and Safari. Many people are comfortable with Mozilla because of its user friendliness (each link opening in different tab with horizontal structure), while many find IE better. Safari is a comparatively new browser with different specifications than IE or Mozilla; and then there is Google Chrome from Google. Hence while code testing, it becomes important to check the pages in all the different browsers from common to uncommon ones. You cannot just leave the compatibility issue with Opera, Opera Mini, Netscape and other browsers because few number of people use it. Your prospective clients, who are sitting poles apart, may very well be browsing your website through Netscape or Opera. And who knows that he might very well turn into a regular business client!
How to Make them Browser Compatible
After knowing the importance, the point in question is how to make the site browser compatible. A thorough XHTML programmer knows all the coding formulae. If you however choose to begin the coding with basic XHTML understanding you possess, it is important to note that not all the browsers can be made XHTML compatible. IE 5 for instance, has no in-built functionality to support Div, and hence does not support XHTML.
It is therefore important to choose a set coding standard that goes well with all the preferred browsers. But at the same time, there might be cases where a particular specified content attains perfect visibility in one browser, and appears deformed in another. A textual paragraph for instance, with a defined width, color and font specifications might not come out fine in two different browsers. In this case, some programmers use Browser Hack to even out the content in both the browsers. But the use of Hacks is not recommended and is avoided to the last as it does not signify browser compatibility.
A little knowledge is very dangerous. It is always a safe bet to outsource the design work to XHTML Conversion firms who are well versed with the ins and outs of XHTML coding standards.