Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 29,
Column 87:
character "&" is the first character of a delimiter but occurred as data
…createElement("canvas"),a=t.getContext&&t.getContext("2d"),i=String.fromCharCo…This message may appear in several cases:
Line 29,
Column 89:
cannot generate system identifier for general entity "t.getContext"
…eateElement("canvas"),a=t.getContext&&t.getContext("2d"),i=String.fromCharCode…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 "&" (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 æ 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.
Line 29,
Column 89:
general entity "t.getContext" not defined and no default entity
…eateElement("canvas"),a=t.getContext&&t.getContext("2d"),i=String.fromCharCode…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.
Line 29,
Column 101:
reference not terminated by REFC delimiter
…"canvas"),a=t.getContext&&t.getContext("2d"),i=String.fromCharCode;return!(!a|…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 29,
Column 101:
reference to entity "t.getContext" for which no system identifier could be generated
…"canvas"),a=t.getContext&&t.getContext("2d"),i=String.fromCharCode;return!(!a|…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.
Line 29,
Column 88:
entity was defined here
…reateElement("canvas"),a=t.getContext&&t.getContext("2d"),i=String.fromCharCod…….fromCharCode;return!(!a||!a.fillText)&&(a.textBaseline="top",a.font="600 32px…This message may appear in several cases:
Line 29,
Column 155:
character "&" is the first character of a delimiter but occurred as data
…fromCharCode;return!(!a||!a.fillText)&&(a.textBaseline="top",a.font="600 32px …This message may appear in several cases:
Line 29,
Column 272:
character "(" not allowed in attribute specification list
…6806,55356,56826),0,0),3e3<t.toDataURL().length):"diversity"===e?(a.fillText(i……6806,55356,56826),0,0),3e3<t.toDataURL().length):"diversity"===e?(a.fillText(i…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:
Line 29,
Column 876:
character "&" is the first character of a delimiter but occurred as data
…ion(){t.DOMReady=!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&…This message may appear in several cases:
Line 29,
Column 878:
cannot generate system identifier for general entity "t.supports.flag"
…n(){t.DOMReady=!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.…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 "&" (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 æ 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.
Line 29,
Column 878:
general entity "t.supports.flag" not defined and no default entity
…n(){t.DOMReady=!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.…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.
Line 29,
Column 893:
reference not terminated by REFC delimiter
…!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.supports.divers…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 29,
Column 893:
reference to entity "t.supports.flag" for which no system identifier could be generated
…!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.supports.divers…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.
Line 29,
Column 877:
entity was defined here
…on(){t.DOMReady=!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t……!0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.supports.divers…This message may appear in several cases:
Line 29,
Column 895:
cannot generate system identifier for general entity "t.supports.unicode8"
…},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.supports.diversit…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 "&" (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 æ 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.
Line 29,
Column 895:
general entity "t.supports.unicode8" not defined and no default entity
…},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.supports.diversit…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.
Line 29,
Column 914:
reference not terminated by REFC delimiter
…&&t.supports.flag&&t.supports.unicode8&&t.supports.diversity||(a=function(){t.…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 29,
Column 914:
reference to entity "t.supports.unicode8" for which no system identifier could be generated
…&&t.supports.flag&&t.supports.unicode8&&t.supports.diversity||(a=function(){t.…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.
Line 29,
Column 894:
entity was defined here
…0},t.supports.simple&&t.supports.flag&&t.supports.unicode8&&t.supports.diversi……&&t.supports.flag&&t.supports.unicode8&&t.supports.diversity||(a=function(){t.…This message may appear in several cases:
Line 29,
Column 916:
cannot generate system identifier for general entity "t.supports.diversity"
…t.supports.flag&&t.supports.unicode8&&t.supports.diversity||(a=function(){t.re…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 "&" (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 æ 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.
Line 29,
Column 916:
general entity "t.supports.diversity" not defined and no default entity
…t.supports.flag&&t.supports.unicode8&&t.supports.diversity||(a=function(){t.re…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.
Line 29,
Column 936:
reference not terminated by REFC delimiter
…upports.unicode8&&t.supports.diversity||(a=function(){t.readyCallback()},n.add…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 29,
Column 936:
reference to entity "t.supports.diversity" for which no system identifier could be generated
…upports.unicode8&&t.supports.diversity||(a=function(){t.readyCallback()},n.add…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.
Line 29,
Column 915:
entity was defined here
…&t.supports.flag&&t.supports.unicode8&&t.supports.diversity||(a=function(){t.r……",function(){"complete"===n.readyState&&t.readyCallback()})),(a=t.source||{}).…This message may appear in several cases:
Line 29,
Column 1168:
cannot generate system identifier for general entity "t.readyCallback"
…function(){"complete"===n.readyState&&t.readyCallback()})),(a=t.source||{}).co…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 "&" (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 æ 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.
Line 29,
Column 1168:
general entity "t.readyCallback" not defined and no default entity
…function(){"complete"===n.readyState&&t.readyCallback()})),(a=t.source||{}).co…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.
Line 29,
Column 1183:
reference not terminated by REFC delimiter
…plete"===n.readyState&&t.readyCallback()})),(a=t.source||{}).concatemoji?o(a.c…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 29,
Column 1183:
reference to entity "t.readyCallback" for which no system identifier could be generated
…plete"===n.readyState&&t.readyCallback()})),(a=t.source||{}).concatemoji?o(a.c…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.
Line 29,
Column 1167:
entity was defined here
…,function(){"complete"===n.readyState&&t.readyCallback()})),(a=t.source||{}).c……concatemoji?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji))…This message may appear in several cases:
Line 29,
Column 1246:
cannot generate system identifier for general entity "a.twemoji"
…ncatemoji?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))}…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 "&" (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 æ 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.
Line 29,
Column 1246:
general entity "a.twemoji" not defined and no default entity
…ncatemoji?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))}…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.
Line 29,
Column 1255:
reference not terminated by REFC delimiter
…?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))}(window,d…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 29,
Column 1255:
reference to entity "a.twemoji" for which no system identifier could be generated
…?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))}(window,d…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.
Line 29,
Column 1245:
entity was defined here
…oncatemoji?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))……?o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))}(window,d…This message may appear in several cases:
Line 29,
Column 1256:
character "&" is the first character of a delimiter but occurred as data
…o(a.concatemoji):a.wpemoji&&a.twemoji&&(o(a.twemoji),o(a.wpemoji)))}(window,do…This message may appear in several cases:
Line 30,
Column 11:
end tag for "t.toDataURL" omitted, but OMITTAG NO was specified
</script>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 29,
Column 260:
start tag was here
…xt(i(55356,56806,55356,56826),0,0),3e3<t.toDataURL().length):"diversity"===e?(…<link rel='https://api.w.org/' href='http://mkgold.lookingforwhitman.org/wp-jso…
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 186,
Column 247:
there is no attribute "srcset"
…annn" width="643" height="290" srcset="http://mkgold.lookingforwhitman.org/fil…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.
Line 186,
Column 402:
there is no attribute "sizes"
…les/2010/04/whitmannn.GIF 643w" sizes="(max-width: 643px) 100vw, 643px" /></a>…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.
Line 203,
Column 434:
there is no attribute "type"
…ullscreen" value="true" /><embed type="application/x-shockwave-flash" width="4…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.
Line 203,
Column 472:
there is no attribute "width"
…"application/x-shockwave-flash" width="480" height="385" src="http://www.youtu…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.
Line 203,
Column 485:
there is no attribute "height"
…x-shockwave-flash" width="480" height="385" src="http://www.youtube.com/v/oZ56…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.
Line 203,
Column 495:
there is no attribute "src"
…e-flash" width="480" height="385" src="http://www.youtube.com/v/oZ56zonpOKA&am…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.
Line 203,
Column 584:
there is no attribute "allowscriptaccess"
…amp;fs=1&rel=0" allowscriptaccess="always" allowfullscreen="true"></embed>…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.
Line 203,
Column 609:
there is no attribute "allowfullscreen"
…el=0" allowscriptaccess="always" allowfullscreen="true"></embed></object><br />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.
Line 203,
Column 615:
element "embed" undefined
…el=0" allowscriptaccess="always" allowfullscreen="true"></embed></object><br />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:
Line 207,
Column 612:
element "embed" undefined
…el=0" allowscriptaccess="always" allowfullscreen="true"></embed></object><br />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:
Line 212,
Column 471:
there is no attribute "id"
…wfullscreen" value="true" /><embed id="viddler_9aeaf797" type="application/x-s…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.
Line 212,
Column 603:
there is no attribute "name"
…ww.viddler.com/player/9aeaf797/" name="viddler_9aeaf797" allowfullscreen="true…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.
Line 212,
Column 671:
element "embed" undefined
…eaf797" allowfullscreen="true" allowscriptaccess="always"></embed></object></p>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:
Line 216,
Column 671:
element "embed" undefined
…5cc3" allowfullscreen="true" allowscriptaccess="always"></embed></object><br />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:
Line 225,
Column 615:
element "embed" undefined
…;rel=0" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>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:
Line 227,
Column 615:
element "embed" undefined
…;rel=0" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>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:
Line 249,
Column 88:
there is no attribute "target"
…digitalhumanitiesstartup.html" target="_blank">The NEH Digital Humanities Star…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.
Line 251,
Column 6:
character data is not allowed here
<ul> Dr. Bonne August, Provost and Vice President, New York City College of<br …You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 251,
Column 81:
document type does not allow element "br" here; assuming missing "li" start-tag
…l> Dr. Bonne August, Provost and Vice President, New York City College of<br />Technology, CUNY</p>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.
Line 259,
Column 38:
end tag for "p" omitted, but OMITTAG NO was specified
School, Rutgers University-Camden</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 258,
Column 1:
start tag was here
<p>Dr. Michael A. Palis, Interim Dean, Faculty of Arts and Sciences Graduate<br…School, Rutgers University-Camden</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 251,
Column 76:
start tag was here
…l> Dr. Bonne August, Provost and Vice President, New York City College of<br /><ul> <strong>Lead Faculty Members</strong><br />…d <a href="http://www.gc.cuny.edu" target="_blank">CUNY Graduate Center</a></p>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.
Line 292,
Column 84:
end tag for "p" omitted, but OMITTAG NO was specified
…eaner: <a href="http://teleogistic.net/" target="_blank">Boone Gorges</a></ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 292,
Column 1:
start tag was here
<p>Cleaner: <a href="http://teleogistic.net/" target="_blank">Boone Gorges</a>……eaner: <a href="http://teleogistic.net/" target="_blank">Boone Gorges</a></ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 261,
Column 6:
start tag was here
<ul> <strong>Lead Faculty Members</strong><br />…how/show.swf?v=71649" allowFullScreen="true" flashvars="offsite=true&lang…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.
Line 374,
Column 592:
there is no attribute "flashvars"
…649" allowFullScreen="true" flashvars="offsite=true&lang=en-us&page_…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.
Line 374,
Column 855:
element "embed" undefined
…72157622767550160&jump_to=" width="400" height="300"></embed></object></p>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:
Line 377,
Column 1:
character data is not allowed here
techwhit: <a href="http://techwhit.lookingforwhitman.org/2009/11/08/brooklyn-hi…You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 377,
Column 103:
document type does not allow element "a" here; assuming missing "li" start-tag
…/08/brooklyn-historical-museum-visit/">Brooklyn Historical Museum Visit</a></p……/08/brooklyn-historical-museum-visit/">Brooklyn Historical Museum Visit</a></p>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.
Line 381,
Column 5:
end tag for "p" omitted, but OMITTAG NO was specified
</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 380,
Column 1:
start tag was here
<p>jenniferying: <a href="http://jenniferying.lookingforwhitman.org/2009/11/09/…</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 377,
Column 11:
start tag was here
techwhit: <a href="http://techwhit.lookingforwhitman.org/2009/11/08/brooklyn-hi…<li>When <a href="http://lookingforwhitman.org/members/cfontaine/">Claire Fonta…The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 452,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol" start-tag
<li>I’ve assigned you a “then and now” photography assignment…The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 836,
Column 52:
there is no attribute "role"
…ass="quicklinks" id="wp-toolbar" role="navigation" aria-label="Toolbar" tabind…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.
Line 836,
Column 76:
there is no attribute "aria-label"
…uicklinks" id="wp-toolbar" role="navigation" aria-label="Toolbar" tabindex="0">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.
Line 836,
Column 95:
there is no attribute "tabindex"
…uicklinks" id="wp-toolbar" role="navigation" aria-label="Toolbar" tabindex="0">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.
Line 838,
Column 83:
there is no attribute "aria-haspopup"
…op"><a class="ab-item" aria-haspopup="true" href="http://mkgold.lookingforwhi…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.
Line 844,
Column 289:
document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
…type="text" value="" maxlength="150" /><label for="adminbar-search" class="scr…The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 844,
Column 345:
document type does not allow element "label" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
…bar-search" class="screen-reader-text">Search</label><input type="submit" clas…The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 844,
Column 420:
document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
…mit" class="adminbar-button" value="Search"/></form></div> </li></ul> </div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 844,
Column 427:
end tag for "form" which is not finished
…mit" class="adminbar-button" value="Search"/></form></div> </li></ul> </div>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
