Reading around the web you can find people exclaiming that they have web standard services. They show off their CSS skills and valid source code. Just because the files pass validation and you are using CSS does not mean the site meets standards, nor does it mean it's efficient or practical source code. Stop for a second and think about this.
Let us compare this to plumbing. You can put different pieces of pipe together (straight, elbow, p-trap, etc) with the right diameters, seals, and techniques. But, just because followed the correct procedure for joints and pipe diameters does not mean you have met any standards. You might unknowingly connect the hot and cold lines together, or loop the drain pipe back to the sink. You could cap off a breather pipe. Quite simply the plumbing in procedure was done correctly but the overall picture is functionless and fails to meet any standard for household plumbing.
The same idea holds true for a website. You might have all your code tags closed properly and the CSS styles are implemented correctly. Perhaps you have used CSS to position all of the elements of your website. Happy with your work you verify the HTML is valid and the CSS is valid. When you take a step back and look at what has happened. You might notice your CSS file is 200k and your HTML page takes a while to load because of all those image files you used. The code looks messy because it's not formatted to be read correctly. Your source code could be bloated with comment lines. This fictitious example is completely valid; however it is not to standards of any kind. The truth is this is not only fictitious; it is all over the internet.
Maybe it's time to go and review that website code, or better yet bring it to us!
Labels: validation, web standards