Errors found while checking this document as HTML 4.01 Strict!

Result: 5 Errors, 1 warning(s)
:
: windows-1252
: HTML 4.01 Strict
Root Element: HTML
Options

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Warning Character Encoding mismatch!

    The character encoding specified in the HTTP header (windows-1252) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (windows-1252) for this validation.

↑ Top

Validation Output: 5 Errors

  1. Error Line 450, Column 153: element "WBR" undefined 
    …javascript:void(document.location=<wbr>'http://validator.w3.org/<wbr>check?<wb…

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  2. Error Line 450, Column 183: element "WBR" undefined 
    …ion=<wbr>'http://validator.w3.org/<wbr>check?<wbr>uri='<wbr>+escape(document.l…

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  3. Error Line 450, Column 194: element "WBR" undefined 
    …ttp://validator.w3.org/<wbr>check?<wbr>uri='<wbr>+escape(document.location))</…

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  4. Error Line 450, Column 204: element "WBR" undefined 
    …lidator.w3.org/<wbr>check?<wbr>uri='<wbr>+escape(document.location))</a></code>

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  5. Error Line 691, Column 6: element "NOBR" undefined 
    <nobr>variant(s)</nobr> of HTML5 that they check against.

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

↑ Top