Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 47,
Column 72:
end tag for "meta" omitted, but OMITTAG NO was specified
<meta name="viewport" content="width=device-width, initial-scale=1.0">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 47,
Column 2:
start tag was here
<meta name="viewport" content="width=device-width, initial-scale=1.0">…://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">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 48,
Column 2:
start tag was here
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-aweso…
Line 49,
Column 114:
cannot generate system identifier for general entity "display"
…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">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 49,
Column 114:
general entity "display" not defined and no default entity
…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">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 49,
Column 121:
reference not terminated by REFC delimiter
…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">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 49,
Column 121:
reference to external entity in attribute value
…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">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 49,
Column 121:
reference to entity "display" for which no system identifier could be generated
…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">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 49,
Column 113:
entity was defined here
…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">…,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500&display=swap" rel="stylesheet">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 49,
Column 2:
start tag was here
<link href="https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,300;0,… <script>!function(a){var e="https://s.go-mpulse.n…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 81,
Column 395:
character "&" is the first character of a delimiter but occurred as data
…ction(){function n(e){a.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!…This message may appear in several cases:
Line 81,
Column 397:
cannot generate system identifier for general entity "e.timeStamp"
…ion(){function n(e){a.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!a.…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 81,
Column 397:
general entity "e.timeStamp" not defined and no default entity
…ion(){function n(e){a.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!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 81,
Column 408:
reference not terminated by REFC delimiter
…ion n(e){a.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!a.BOOMR||!a.B…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 81,
Column 408:
reference to entity "e.timeStamp" for which no system identifier could be generated
…ion n(e){a.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!a.BOOMR||!a.B…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 81,
Column 396:
entity was defined here
…tion(){function n(e){a.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!a……etTime()}if(!a.BOOMR||!a.BOOMR.version&&!a.BOOMR.snippetExecuted){a.BOOMR=a.BO…This message may appear in several cases:
Line 81,
Column 461:
character "&" is the first character of a delimiter but occurred as data
…tTime()}if(!a.BOOMR||!a.BOOMR.version&&!a.BOOMR.snippetExecuted){a.BOOMR=a.BOO…This message may appear in several cases:
Line 81,
Column 1226:
an attribute specification must start with a name or name token
…this.body.appendChild(a)},_.write("<bo"+'dy onload="document._l();">'),_.close…An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Line 81,
Column 1226:
element "bo" undefined
…this.body.appendChild(a)},_.write("<bo"+'dy onload="document._l();">'),_.close…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 81,
Column 1289:
character "&" is the first character of a delimiter but occurred as data
…();">'),_.close()}}(),"".length>0)if(a&&"performance"in a&&a.performance&&"fun…This message may appear in several cases:
Line 81,
Column 1290:
character "&" is the first character of a delimiter but occurred as data
…);">'),_.close()}}(),"".length>0)if(a&&"performance"in a&&a.performance&&"func…This message may appear in several cases:
Line 81,
Column 1308:
character "&" is the first character of a delimiter but occurred as data
…(),"".length>0)if(a&&"performance"in a&&a.performance&&"function"==typeof a.pe…This message may appear in several cases:
Line 81,
Column 1310:
cannot generate system identifier for general entity "a.performance"
…,"".length>0)if(a&&"performance"in a&&a.performance&&"function"==typeof a.perf…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 81,
Column 1310:
general entity "a.performance" not defined and no default entity
…,"".length>0)if(a&&"performance"in a&&a.performance&&"function"==typeof a.perf…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 81,
Column 1323:
reference not terminated by REFC delimiter
…if(a&&"performance"in a&&a.performance&&"function"==typeof a.performance.setRe…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 81,
Column 1323:
reference to entity "a.performance" for which no system identifier could be generated
…if(a&&"performance"in a&&a.performance&&"function"==typeof a.performance.setRe…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 81,
Column 1309:
entity was defined here
…),"".length>0)if(a&&"performance"in a&&a.performance&&"function"==typeof a.per……if(a&&"performance"in a&&a.performance&&"function"==typeof a.performance.setRe…This message may appear in several cases:
Line 81,
Column 1324:
character "&" is the first character of a delimiter but occurred as data
…f(a&&"performance"in a&&a.performance&&"function"==typeof a.performance.setRes…This message may appear in several cases:
Line 81,
Column 2574:
character "&" is the first character of a delimiter but occurred as data
…unction(e){var t="http.initiator";if(e&&(!e[t]||"spa_hard"===e[t]))_["ak.feo"]…This message may appear in several cases:
Line 81,
Column 2575:
character "&" is the first character of a delimiter but occurred as data
…nction(e){var t="http.initiator";if(e&&(!e[t]||"spa_hard"===e[t]))_["ak.feo"]=…This message may appear in several cases:
Line 81,
Column 3088:
end tag for "bo" omitted, but OMITTAG NO was specified
…!0}return this},is_complete:function(){return!0}}}}()}(window);</script></head>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 81,
Column 1223:
start tag was here
…(),this.body.appendChild(a)},_.write("<bo"+'dy onload="document._l();">'),_.cl……="width:328px" class="colCenter" href="http://www.mites.gob.es" target="_blank…
You have specified an attribute more than once. Example: Using
the "height" attribute twice on the same
"img" tag.
Line 124,
Column 130:
there is no attribute "alt"
…www.mites.gob.es" target="_blank" alt="Ministerio de Empleo y Seguridad Social…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 124,
Column 320:
required attribute "alt" not specified
…g src="../../../resources/img/web/logo_Mites.png" class="imagenMinisterio"></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 124,
Column 324:
end tag for "img" omitted, but OMITTAG NO was specified
…g src="../../../resources/img/web/logo_Mites.png" class="imagenMinisterio"></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 124,
Column 243:
start tag was here
…isterio de Empleo y Seguridad Social"><img src="../../../resources/img/web/log… </table>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.
