To validate a page

When it validates their side, it is often the purpose of standardizing the site so that it will be compatible in most browsers. But also for himself to one side that is completely clean with no errors in coding. It is not easy without sacrificing some scripts and codes to get one side completely validated, you might think now. But - it is, actually. By "poking" into some final code so it prevents the browser to interpret the script error - and example, you can keep your javascript.

Let's say you choose to testvalidera your site and when you discover a lot of errors even though you may have used a WYSWYG programs or are proficient on their own to write your notes. How can it now be that it is still wrong? Here are some examples:

• You are using the wrong doctype
• WYSWYG programs does not use standardization as a "standard", but gives only the code itself. This means you can have more than one code example with head - body attribute which when entered on the page.
• you have missed an "alt" tag.
• you forgot to put out a sluttag or slash.
• You forgot to close one or more pieces
• using the dual attributes such as body or head.
• css codes may not be compatible with XHTML code. This applies particularly to those who have previously used a css template but changed over to encode the page exclusively in CSS. End Tags and other attributes looks completely different, like the javascript to be rewritten when they are not always compatible with a pure CSS-created page .
• regular html code in body text is not permitted, such as changing font, create a line break as <br> (strict) or to use table-attribute <table> without having to define this summary.
• This in turn means that you can not use the target = "_blank" or border = "0" in the code of strict
• you are mixing html and css codes on the same page.
• in XHTML you must not use capital letters in the codes but only lowercase
• You are using the wrong semantic structure

Internet Explorer also places "through" many syntax errors in the codes - so it is not at all certain that your site looks the same in other browsers or operating systems on your own. In addition, there are more variations than today in the computer age began. Therefore, the concept of web standard introduced and have become increasingly common. One can choose from different options but most are transitional and strict. The latter has a bit more tighter rules and you hear the name already.

To test your site?

Get just do not panic when you see the result. See it instead as you can clear the page from a lot of "unnecessary" code and thereby facilitate the upload of your site. In addition, you of course know if the codes are complete or not - and it is mostly of interest if you want a well-functioning page. Those who use php inclu should note row and column - the validator scans the entire page and include all inclu resulting in that you might not find the specific line of your index records. Take a look when the next count rows and inclu or open source and save the entire document in HTML format. Then count the rows. You can not upload a inkludesida as main, footer or header - and validate this, the validator only read entire pages.

For pages built solely by css or xhtml.

xhtml - with transitional or strict doctype

For standard HTML coding

In your stylesheet