• blog development
  • pingback dev
  • storing comments
  • trackback dev
  • trackback or pingback
• business blog
  • ATOM feed
  • new eu site
  • new partners
  • RSS feed
• dutch
  • webdesign limburg
• humor
• personal
  • blog start
  • blogrolling
  • ZEND certification
• php security
  • htaccess and php security
• script blog
  • session time outs
  • xml tryouts
• webdev blog
  • agile development
  • any browser
  • code validation
  • css validation
  • microformats and hcards
  • SAJAX

Blog Roll

Hardened-PHP Project News John Lim O'Reilly PHP DevCenter PHP Classes PHP DevCenter PHP Security Consortium PHP-Center php.net PHPBuilder.com Planet PHP Professional PHP Recipes PHP Cookbook Smoking PHP ThinkPHP Tobias Schlitt WeberDev Powered by Bloglines

Validating (X)HTML on your site and fixing them errors

There is a simple way to see if your web page's (X)HTML conforms to the w3c coding standards:
Just put a link to http://validator.w3.org/check?uri=referer on any page you want to validate, and when you open that url from your page you will see an error report on your page's validity.
Now as it turned out I have been quite naughty with regards to coding standards on this site's XHTML so I will have to fix some troubles, and I will fix them while writing this.

First I will have to get rid of all non closed tags errors as XHTML transitional does not allow non closed tags.
Then I should fix all uppercase markups to lowercase, XHTML only validates lowercase markup.

After that was done 81 out of the initial 90 errors were fixed . So that's quite a good result for just a few minutes work.

Now I will address the remaining errors, which are apparently content related. Some <p>  and other not allowed tags inside a <font> tag are the cause of some errors, it seems the WYSIWYG editor used inside the CMS sometimes allows for this kind of errors to happen. So I manually deleted the <font> tags that caused the problem, and now the page will validate.

Anyway, the page (at this moment) is found to be valid XHTML 1.0 Transitional, and therefore I am allowed to put the w3c icon right here! 

I truly recommend using validation tools to check the output you are sending to your visitor's browsers, and fix as many problems you can.
You will learn a lot about valid HTML along the way, and will become a better (X)HTML coder as a result.
Especially the non standard browser visitors (braille reading browsers f.i.) will appreciate your efforts!

All in all it took me just about 30 minutes to find and fix all errors AND write this little blog about the process along the way.

Send your comments to or post them right here!

Start > blog> webdev blog> code validation...