|webdev blog carp fishing blog|
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:
First I will have to get rid of all non closed tags errors as XHTML transitional does not allow non closed tags.
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.
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.
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.
There are no comments on this blog entry yet!
Send your comments to or post them right here!
Start > blog> webdev blog> code validation...