Markup Validation Service

Validation Output: 44 Errors

1. Line 42, Column 19: Attribute "LANGUAGE" is not a valid attribute. Did you mean "language"?

   	<script language="JavaScript" type="text/javascript" src="../../../javascripts/

   ✉

   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 97, Column 73: NET-enabling start-tag requires SHORTTAG YES

   …e" content="text/html; charset=iso-8859-1" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

3. Line 97, Column 74: character data is not allowed here

   … content="text/html; charset=iso-8859-1" />

   ✉

   You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

   • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
   • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
   • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
4. Line 103, Column 79: NET-enabling start-tag requires SHORTTAG YES

   …vjKUQ6aMuqQeHCrr0alwD8Ytfp3apUCMU8=" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

5. Line 162, Column 243: Attribute "BORDER" is not a valid attribute. Did you mean "border"?

   …s/images/s/podfrey_logo.png" border="0" align="middle"></a></h1>

   ✉

   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 162, Column 253: Attribute "ALIGN" is not a valid attribute. Did you mean "align"?

   …/podfrey_logo.png" border="0" align="middle"></a></h1>

   ✉

   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.

7. Line 162, Column 261: required attribute "ALT" not specified

   …_logo.png" border="0" align="middle"></a></h1>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

8. Line 167, Column 65: document type does not allow element "LINK" here

   …userdata/menu.css" rel="stylesheet" type="text/css">

   ✉

   The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

   One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

9. Line 169, Column 44: NET-enabling start-tag requires SHORTTAG YES

   <img src="/userdata/graphics/same_day.gif" />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

10. Line 169, Column 44: required attribute "ALT" not specified

    <img src="/userdata/graphics/same_day.gif" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

11. Line 181, Column 69: cannot generate system identifier for general entity "parent_menu_item_id"

    …ome/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

12. Line 181, Column 69: general entity "parent_menu_item_id" not defined and no default entity

    …ome/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

13. Line 181, Column 88: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …m?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

14. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

15. Line 181, Column 94: cannot generate system identifier for general entity "menu_id"

    …_code=HOME&parent_menu_item_id=3047&menu_id=0"

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

16. Line 181, Column 94: general entity "menu_id" not defined and no default entity

    …_code=HOME&parent_menu_item_id=3047&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

17. Line 181, Column 101: reference to entity "menu_id" for which no system identifier could be generated

    …OME&parent_menu_item_id=3047&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

18. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

19. Line 194, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6209&parent_menu_item_id=3048&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

20. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

21. Line 194, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …209&parent_menu_item_id=3048&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

22. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

23. Line 207, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6232&parent_menu_item_id=3059&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

24. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

25. Line 207, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …232&parent_menu_item_id=3059&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

26. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

27. Line 220, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6230&parent_menu_item_id=3060&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

28. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

29. Line 220, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …230&parent_menu_item_id=3060&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

30. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

31. Line 233, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6219&parent_menu_item_id=3049&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

32. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

33. Line 233, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …219&parent_menu_item_id=3049&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

34. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

35. Line 246, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6211&parent_menu_item_id=3050&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

36. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

37. Line 246, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …211&parent_menu_item_id=3050&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

38. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

39. Line 259, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6213&parent_menu_item_id=3052&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

40. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

41. Line 259, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …213&parent_menu_item_id=3052&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

42. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

43. Line 272, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6214&parent_menu_item_id=3053&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

44. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

45. Line 272, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …214&parent_menu_item_id=3053&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

46. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

47. Line 285, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6215&parent_menu_item_id=3054&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

48. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

49. Line 285, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …215&parent_menu_item_id=3054&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

50. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

51. Line 298, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6216&parent_menu_item_id=3056&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

52. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

53. Line 298, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …216&parent_menu_item_id=3056&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

54. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

55. Line 311, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6217&parent_menu_item_id=3055&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

56. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

57. Line 311, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …217&parent_menu_item_id=3055&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

58. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

59. Line 324, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6218&parent_menu_item_id=3057&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

60. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

61. Line 324, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …218&parent_menu_item_id=3057&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

62. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

63. Line 326, Column 13: cannot generate system identifier for general entity "Conditions"

    					>Terms&Conditions

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

64. Line 326, Column 13: general entity "Conditions" not defined and no default entity

    					>Terms&Conditions

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

65. Line 326, Column 23: reference to entity "Conditions" for which no system identifier could be generated

    					>Terms&Conditi…

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

66. Line 326, Column 11: entity was defined here

    					>Terms&Conditions

67. Line 337, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6210&parent_menu_item_id=3058&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

68. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

69. Line 337, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …210&parent_menu_item_id=3058&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

70. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

71. Line 350, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6212&parent_menu_item_id=3051&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

72. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

73. Line 350, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …212&parent_menu_item_id=3051&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

74. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

75. Line 363, Column 87: reference to entity "parent_menu_item_id" for which no system identifier could be generated

    …fm?story_id=6233&parent_menu_item_id=3061&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

76. Line 181, Column 67: entity was defined here

    …../home/pages/common/show-story.cfm?link_code=HOME&parent_menu_item_id=3047&menu_id=0"

77. Line 363, Column 100: reference to entity "menu_id" for which no system identifier could be generated

    …233&parent_menu_item_id=3061&menu_id=0"

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

78. Line 181, Column 92: entity was defined here

    …nk_code=HOME&parent_menu_item_id=3047&menu_id=0"

79. Line 372, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br /><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

80. Line 372, Column 11: NET-enabling start-tag requires SHORTTAG YES

    <br /><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

81. Line 373, Column 12: Attribute "ALIGN" is not a valid attribute. Did you mean "align"?

    <div align="center">

    ✉

    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.

82. Line 374, Column 137: NET-enabling start-tag requires SHORTTAG YES

    … Keysoft">Business Opportunities<br />and Employment</a>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

83. Line 379, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

84. Line 380, Column 5: NET-enabling start-tag requires SHORTTAG YES

    <br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

85. Line 431, Column 11: ID "CLEAR" already defined

    	<div id="clear"></div>

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

86. Line 426, Column 12: ID "CLEAR" first defined here

    			<div id="clear"></div>

87. Line 433, Column 63: Attribute "TARGET" is not a valid attribute. Did you mean "target"?

    …"powered"><a href="http://www.keysoft.com.au" target="keysoft">Powered by Keysoft</a></div>

    ✉

    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.

↑ Top