Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 5,
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 34,
Column 79:
required attribute "type" not specified
…rc="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></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 78,
Column 25:
there is no attribute "autocomplete"
<input autocomplete="off" class="usagov-search-autocomplete" id="query" nam…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 176,
Column 150:
end tag for element "a" which is not open
…ture=youtu.be">NEHRI Overview Video Produced by NSF</a> (2:22 minutes)</a></li>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 182,
Column 93:
cannot generate system identifier for general entity "WT.mc_ev"
…f18082/nsf18082.jsp?WT.mc_id=USNSF_25&WT.mc_ev=click">Dear Colleague Letter: R…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 182,
Column 93:
general entity "WT.mc_ev" not defined and no default entity
…f18082/nsf18082.jsp?WT.mc_id=USNSF_25&WT.mc_ev=click">Dear Colleague Letter: R…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 182,
Column 101:
reference not terminated by REFC delimiter
…sf18082.jsp?WT.mc_id=USNSF_25&WT.mc_ev=click">Dear Colleague Letter: Removal o…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 182,
Column 101:
reference to external entity in attribute value
…sf18082.jsp?WT.mc_id=USNSF_25&WT.mc_ev=click">Dear Colleague Letter: Removal o…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 182,
Column 101:
reference to entity "WT.mc_ev" for which no system identifier could be generated
…sf18082.jsp?WT.mc_id=USNSF_25&WT.mc_ev=click">Dear Colleague Letter: Removal o…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 182,
Column 92:
entity was defined here
…sf18082/nsf18082.jsp?WT.mc_id=USNSF_25&WT.mc_ev=click">Dear Colleague Letter: ……="ex2" href="https://doi.org/doi:10.18434/M3KW2M">Testing Database</a></a></li>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 335,
Column 32:
character "/" is not allowed in the value of attribute "target"
<p> <a href="/pdf" target="/pdf/NEHRP_related_Events.pdf"><img src="images/…
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 368,
Column 13:
ID "subscribebox" already defined
<div id="subscribebox"> 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).
Line 358,
Column 13:
ID "subscribebox" first defined here
<div id="subscribebox"> 