Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 52,
Column 8:
required attribute "type" not specified
<script>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>.
Line 458,
Column 495:
required attribute "alt" not specified
…orthkoreatech.org/wp-content/uploads/2014/11/nknewscalendar2014.jpg"></a></div>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>.
Line 458,
Column 499:
end tag for "img" omitted, but OMITTAG NO was specified
…orthkoreatech.org/wp-content/uploads/2014/11/nknewscalendar2014.jpg"></a></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 ">".
Line 458,
Column 404:
start tag was here
…s.org/nknews-calendar-2015/', '']);" ><img src="https://www.northkoreatech.org……"https://www.northkoreatech.org/wp-content/uploads/2010/12/kp-banner1.jpg"></a>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>.
Line 459,
Column 525:
end tag for "img" omitted, but OMITTAG NO was specified
…"https://www.northkoreatech.org/wp-content/uploads/2010/12/kp-banner1.jpg"></a>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 459,
Column 438:
start tag was here
…-north-korean-website-list/', '']);" ><img src="https://www.northkoreatech.org……="https://www.northkoreatech.org/wp-content/uploads/2012/09/yt-banner.jpg"></a>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>.
Line 460,
Column 290:
end tag for "img" omitted, but OMITTAG NO was specified
…="https://www.northkoreatech.org/wp-content/uploads/2012/09/yt-banner.jpg"></a>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 460,
Column 204:
start tag was here
…-north-korean-youtube-list/', '']);" ><img src="https://www.northkoreatech.org…<br>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 461,
Column 1:
start tag was here
<br>…s://www.northkoreatech.org/wp-content/uploads/2011/02/facebook-banner.jpg"></a>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>.
Line 462,
Column 296:
end tag for "img" omitted, but OMITTAG NO was specified
…s://www.northkoreatech.org/wp-content/uploads/2011/02/facebook-banner.jpg"></a>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 462,
Column 204:
start tag was here
…-Korea-Tech/179042072124506', '']);" ><img src="https://www.northkoreatech.org……//www.northkoreatech.org/wp-content/uploads/2011/06/dprk-search.jpg"></a></div>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>.
Line 463,
Column 264:
end tag for "img" omitted, but OMITTAG NO was specified
…//www.northkoreatech.org/wp-content/uploads/2011/06/dprk-search.jpg"></a></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 ">".
Line 463,
Column 176:
start tag was here
…eatech.org/dprk-web-search/', '']);" ><img src="https://www.northkoreatech.org…… id='youtube-sidebar-widget' data-url='http://gdata.youtube.com/feeds/api/play…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 477,
Column 358:
cannot generate system identifier for general entity "key"
…eeds/api/playlists/northkoreatech?v=2&key=AI39si4egIgiaFaxxolUNjk1Iw4ip4GHWJMt…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 477,
Column 358:
general entity "key" not defined and no default entity
…eeds/api/playlists/northkoreatech?v=2&key=AI39si4egIgiaFaxxolUNjk1Iw4ip4GHWJMt…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 477,
Column 361:
reference not terminated by REFC delimiter
…s/api/playlists/northkoreatech?v=2&key=AI39si4egIgiaFaxxolUNjk1Iw4ip4GHWJMt44Z…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 477,
Column 361:
reference to external entity in attribute value
…s/api/playlists/northkoreatech?v=2&key=AI39si4egIgiaFaxxolUNjk1Iw4ip4GHWJMt44Z…This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 477,
Column 361:
reference to entity "key" for which no system identifier could be generated
…s/api/playlists/northkoreatech?v=2&key=AI39si4egIgiaFaxxolUNjk1Iw4ip4GHWJMt44Z…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 477,
Column 357:
entity was defined here
…feeds/api/playlists/northkoreatech?v=2&key=AI39si4egIgiaFaxxolUNjk1Iw4ip4GHWJM…<li id='sueIq54W4xA' data-autoplay='0'><img src='http://i2.ytimg.com/vi/sueIq54…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 481,
Column 168:
there is no attribute "desc"
…' alt='North Korea questions at State Dept. briefing, December 29, 2014' desc='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 498,
Column 140:
document type does not allow element "li" here; missing one of "ul", "ol" start-tag
…<li id='LP9MdPnGQ1o' data-autoplay='0'><img src='http://i2.ytimg.com/vi/LP9MdP…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 515,
Column 144:
document type does not allow element "li" here; missing one of "ul", "ol" start-tag
…<li id='ioTo7xw_-xc' data-autoplay='0'><img src='http://i2.ytimg.com/vi/ioTo7x…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 532,
Column 103:
value of attribute "id" invalid: "5" cannot start a name
…PRK human rights - English</a><li id='5oAxxPwI3kk' data-autoplay='0'><img src=…
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 532,
Column 133:
document type does not allow element "li" here; missing one of "ul", "ol" start-tag
…<li id='5oAxxPwI3kk' data-autoplay='0'><img src='http://i2.ytimg.com/vi/5oAxxP…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 549,
Column 106:
end tag for "li" omitted, but OMITTAG NO was specified
…0px;'>UNSC votes to begin debate on DPRK human rights - Original audio</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 532,
Column 95:
start tag was here
…ate on DPRK human rights - English</a><li id='5oAxxPwI3kk' data-autoplay='0'><……0px;'>UNSC votes to begin debate on DPRK human rights - Original audio</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 515,
Column 106:
start tag was here
… Dept. briefing, December 23, 2014</a><li id='ioTo7xw_-xc' data-autoplay='0'><……0px;'>UNSC votes to begin debate on DPRK human rights - Original audio</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 498,
Column 102:
start tag was here
… Dept. briefing, December 29, 2014</a><li id='LP9MdPnGQ1o' data-autoplay='0'><……0px;'>UNSC votes to begin debate on DPRK human rights - Original audio</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 481,
Column 1:
start tag was here
<li id='sueIq54W4xA' data-autoplay='0'><img src='http://i2.ytimg.com/vi/sueIq54……loads/2012/02/feature-dish.png" align=left style="padding:5px"></a><b>Mystery …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 553,
Column 567:
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…loads/2012/02/feature-dish.png" align=left style="padding:5px"></a><b>Mystery ……sh.png" align=left style="padding:5px"></a><b>Mystery Satellite Dishes</b><br>…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>.
Line 553,
Column 595:
end tag for "img" omitted, but OMITTAG NO was specified
…ng" align=left style="padding:5px"></a><b>Mystery Satellite Dishes</b><br>Are …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 553,
Column 475:
start tag was here
…tellite-monitoring-station/', '']);" ><img src="https://www.northkoreatech.org……/a><b>Mystery Satellite Dishes</b><br>Are these large dishes on a Pyongyang hi…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 553,
Column 627:
start tag was here
…x"></a><b>Mystery Satellite Dishes</b><br>Are these large dishes on a Pyongyan…<br>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 554,
Column 1:
start tag was here
<br><br>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 555,
Column 1:
start tag was here
<br>…loads/2012/02/feature-kctv.png" align=left style="padding:5px"></a><b>Behind T……tv.png" align=left style="padding:5px"></a><b>Behind The Scenes at KCTV</b><br…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>.
Line 556,
Column 356:
end tag for "img" omitted, but OMITTAG NO was specified
…ng" align=left style="padding:5px"></a><b>Behind The Scenes at KCTV</b><br>She…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 556,
Column 236:
start tag was here
…ctv-interviews-ri-chun-hui/', '']);" ><img src="https://www.northkoreatech.org……a><b>Behind The Scenes at KCTV</b><br>She's one of the most recognized faces i…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 556,
Column 389:
start tag was here
…"></a><b>Behind The Scenes at KCTV</b><br>She's one of the most recognized fac…<br>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 558,
Column 1:
start tag was here
<br><br>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 560,
Column 1:
start tag was here
<br>…iaelement/mediaelementplayer.min.css?ver=2.15.1' type='text/css' media='all' />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).
Line 629,
Column 172:
document type does not allow element "link" here
…des/js/mediaelement/wp-mediaelement.css?ver=4.1' type='text/css' media='all' />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).
