Markup Validation Service

Validation Output: 12 Errors

1. Line 85, Column 12: there is no attribute "face"

   <FONT face=Arial color=blue size=2>

   ✉

   You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

   This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

   How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

2. Line 85, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

   <FONT face=Arial color=blue size=2>

   ✉

3. Line 85, Column 24: there is no attribute "color"

   <FONT face=Arial color=blue size=2>

   ✉

   You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

   This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

   How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

4. Line 85, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

   <FONT face=Arial color=blue size=2>

   ✉

5. Line 85, Column 34: there is no attribute "size"

   <FONT face=Arial color=blue size=2>

   ✉

   You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

   This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

   How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

6. Line 85, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

   <FONT face=Arial color=blue size=2>

   ✉

7. Line 85, Column 35: element "FONT" undefined

   <FONT face=Arial color=blue size=2>

   ✉

   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).
8. Line 86, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

   <table width=450 border=3 cellspacing=5>

   ✉

9. Line 86, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

   <table width=450 border=3 cellspacing=5>

   ✉

10. Line 86, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

    <table width=450 border=3 cellspacing=5>

    ✉

11. Line 102, Column 7: end tag for element "font" which is not open

    </font>

    ✉

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

12. Line 113, Column 6: end tag for "FONT" omitted, but OMITTAG NO was specified

    </div>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

13. Line 85, Column 1: start tag was here

    <FONT face=Arial color=blue size=2>

↑ Top