Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Character Encoding Override in effect!
The detected character encoding
"utf-8"
has been suppressed and
"windows-1252" used instead.
DOCTYPE Override in effect!
The detected DOCTYPE Declaration
"<!doctype html>" has been
suppressed and the DOCTYPE for
"HTML 4.01 Transitional" inserted instead,
but even if no errors are shown below the document will not be Valid
until you update it to reflect this new DOCTYPE.
Line 1,
Column 152:
there is no attribute "CLASS"
…ype html> --><html lang="de-de" class="a-no-js" data-19ax5a9jf="dingo"><!-- sp…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 1,
Column 177:
there is no attribute "DATA-19AX5A9JF"
…g="de-de" class="a-no-js" data-19ax5a9jf="dingo"><!-- sp:feature:head-start -->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 2,
Column 14:
required attribute "TYPE" not specified
<head><script>var aPageStart = (new Date()).getTime();</script><meta charset="u…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 2,
Column 78:
there is no attribute "CHARSET"
…script>var aPageStart = (new Date()).getTime();</script><meta charset="utf-8"/>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 2,
Column 85:
NET-enabling start-tag requires SHORTTAG YES
…script>var aPageStart = (new Date()).getTime();</script><meta charset="utf-8"/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 2,
Column 85:
required attribute "CONTENT" not specified
…script>var aPageStart = (new Date()).getTime();</script><meta charset="utf-8"/>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 2,
Column 86:
character data is not allowed here
…script>var aPageStart = (new Date()).getTime();</script><meta charset="utf-8"/>You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 86,
Column 8:
required attribute "TYPE" not specified
<script>window.ue && ue.count && ue.count('CSMLibrarySize', 10140)</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 89,
Column 792:
NET-enabling start-tag requires SHORTTAG YES
…1L.css,21F85am0yFL.css,01giMEP+djL.css_.css?AUIClients/AmazonUI#not-trident" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 89,
Column 793:
character data is not allowed here
…1L.css,21F85am0yFL.css,01giMEP+djL.css_.css?AUIClients/AmazonUI#not-trident" />You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 90,
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 134,
Column 129:
NET-enabling start-tag requires SHORTTAG YES
….com/images/I/01C10v4TaxL.css?AUIClients/ShoppingPortalAssets-cookieConsent" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 134,
Column 130:
character data is not allowed here
….com/images/I/01C10v4TaxL.css?AUIClients/ShoppingPortalAssets-cookieConsent" />You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 135,
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 139,
Column 108:
there is no attribute "CROSSORIGIN"
…11J1WJh9jNL.js?AUIClients/PRIVCONAssets-stub" crossorigin="anonymous"></script>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 139,
Column 119:
required attribute "TYPE" not specified
…11J1WJh9jNL.js?AUIClients/PRIVCONAssets-stub" crossorigin="anonymous"></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 160,
Column 339:
cannot generate system identifier for general entity "DceWEPuy"
…s_.css?AUIClients/NavDesktopUberAsset&DceWEPuy#desktop.language-de.de.488657-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 160,
Column 339:
general entity "DceWEPuy" not defined and no default entity
…s_.css?AUIClients/NavDesktopUberAsset&DceWEPuy#desktop.language-de.de.488657-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 160,
Column 347:
reference to entity "DceWEPuy" for which no system identifier could be generated
…ss?AUIClients/NavDesktopUberAsset&DceWEPuy#desktop.language-de.de.488657-T1" />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 160,
Column 338:
entity was defined here
…ss_.css?AUIClients/NavDesktopUberAsset&DceWEPuy#desktop.language-de.de.488657-……ss?AUIClients/NavDesktopUberAsset&DceWEPuy#desktop.language-de.de.488657-T1" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 160,
Column 383:
character data is not allowed here
…ss?AUIClients/NavDesktopUberAsset&DceWEPuy#desktop.language-de.de.488657-T1" />You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 163,
Column 7:
required attribute "TYPE" not specified
<style>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 166,
Column 130:
NET-enabling start-tag requires SHORTTAG YES
…mages-amazon.com/images/I/4171sdbgqbL.css?AUIClients/AmazonGatewayAuiAssets" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 166,
Column 131:
character data is not allowed here
…mages-amazon.com/images/I/4171sdbgqbL.css?AUIClients/AmazonGatewayAuiAssets" />You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 167,
Column 7:
required attribute "TYPE" not specified
<style>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 170,
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 221,
Column 16:
there is no attribute "PROPERTY"
<meta property="fb:app_id" content="164734381262">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 222,
Column 33:
there is no attribute "VALUE"
<meta name="twitter:card" value="summary">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 222,
Column 42:
required attribute "CONTENT" not specified
<meta name="twitter:card" value="summary">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 223,
Column 46:
required attribute "CONTENT" not specified
<meta name="twitter:site:id" value="20793816">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 224,
Column 226:
there is no attribute "XMLNS:OG"
…Drogerie & mehr bei Amazon.de" xmlns:og="http://opengraphprotocol.org/schema/">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 225,
Column 71:
NET-enabling start-tag requires SHORTTAG YES
…1" content="3C8D6512B1E530046DE0569BA27093F3" /><script type="text/javascript">
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 264,
Column 8:
required attribute "TYPE" not specified
<script>window.ue && ue.count && ue.count('CSMLibrarySize', 3172)</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 267,
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 274,
Column 7:
end tag for element "HEAD" which is not open
</head><!-- sp:end-feature:head-close -->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 276,
Column 283:
document type does not allow element "BODY" here
…_cache_333406-c a-aui_tnr_v2_180836-c"><div id="a-page"><script type="a-state"…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 276,
Column 337:
there is no attribute "DATA-A-STATE"
…"><script type="a-state" data-a-state="{"key":"a-wlab-states&qu…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 276,
Column 680:
required attribute "TYPE" not specified
…SK_BANNER_210084":"C"}</script><script>typeof uex === 'function' && uex('ld', …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 278,
Column 243:
there is no attribute "ONLOAD"
…d%3D5G9NCES2BMM0GMZ2XSR6:0' alt="" onload="window.ue_sbl && window.ue_sbl();"/>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 278,
Column 278:
NET-enabling start-tag requires SHORTTAG YES
…d%3D5G9NCES2BMM0GMZ2XSR6:0' alt="" onload="window.ue_sbl && window.ue_sbl();"/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 281,
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 310,
Column 8:
required attribute "TYPE" not specified
<script>window.ue && ue.count && ue.count('CSMLibrarySize', 16762)</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 313,
Column 41:
there is no attribute "DATA-ACTION"
…pan class="a-declarative" data-action="sp-cc" data-csa-c-type="widget" data-cs…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 313,
Column 65:
there is no attribute "DATA-CSA-C-TYPE"
…" data-action="sp-cc" data-csa-c-type="widget" data-csa-c-func-deps="aui-da-sp…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 313,
Column 95:
there is no attribute "DATA-CSA-C-FUNC-DEPS"
…-c-type="widget" data-csa-c-func-deps="aui-da-sp-cc" data-sp-cc="{"custom…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 313,
Column 121:
there is no attribute "DATA-SP-CC"
…c-func-deps="aui-da-sp-cc" data-sp-cc="{"customerId":"null"…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 313,
Column 417:
document type does not allow element "FORM" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME" start-tag
…on="/privacyprefs/retail/v1/acceptall"><input type="hidden" name="anti-csrftok…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 313,
Column 577:
NET-enabling start-tag requires SHORTTAG YES
…3MDE4LTRlZmQtODRjMS0yMmEwMWU4ODkxNmE="/><input type="hidden" name="timeStamp" …
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 313,
Column 638:
NET-enabling start-tag requires SHORTTAG YES
…name="timeStamp" value="1699663592615"/><input type="hidden" name="locale" val…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 313,
Column 688:
NET-enabling start-tag requires SHORTTAG YES
…e="hidden" name="locale" value="de_DE"/><input type="hidden" name="isMobile" v…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 313,
Column 740:
NET-enabling start-tag requires SHORTTAG YES
…"hidden" name="isMobile" value="false"/><input type="hidden" name="treatmentNa…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 313,
Column 834:
NET-enabling start-tag requires SHORTTAG YES
…COOKIE_BANNER_CUSTOMIZE_TEST_724232_C"/><input type="hidden" name="userType" v…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 313,
Column 896:
NET-enabling start-tag requires SHORTTAG YES
…ame="userType" value="UNAUTHENTICATED"/><div id="sp-cc-rejectall-container"><a…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 313,
Column 1001:
there is no attribute "ROLE"
…class="a-link-emphasis" href="#" role="button">Weiter ohne zu akzeptieren</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 314,
Column 1214:
cannot generate system identifier for general entity "ref_"
…ustomer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerkläru…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 314,
Column 1214:
general entity "ref_" not defined and no default entity
…ustomer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerkläru…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 314,
Column 1218:
reference to entity "ref_" for which no system identifier could be generated
…mer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklärung</…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……r aok-hidden a-spacing-top-base" role="alert"><div class="a-box-inner a-alert-…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 314,
Column 1825:
NET-enabling start-tag requires SHORTTAG YES
…t celwidget" type="submit" value="all"/><span class="a-button-text" aria-hidde…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 314,
Column 1867:
there is no attribute "ARIA-HIDDEN"
…pan class="a-button-text" aria-hidden="true">Cookies akzeptieren</span></span>…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 314,
Column 2180:
required attribute "TYPE" not specified
…pan></span></div></form></span><script>P.register('sp-cc-ready');</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 331,
Column 142:
NET-enabling start-tag requires SHORTTAG YES
…-sprite-global-1x-hm-dsk-reorg._CB405937709_.png" style="display:none" alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 333,
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 414,
Column 17:
there is no attribute "MARK"
<style mark="aboveNavInjectionCSS" type="text/css">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 414,
Column 55:
document type does not allow element "STYLE" here
<style mark="aboveNavInjectionCSS" type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 417,
Column 18:
there is no attribute "MARK"
<script mark="aboveNavInjectionJS" type="text/javascript">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 419,
Column 952:
end tag for "SCRIPT" omitted, but its declaration does not permit this
…nt=$('<div class=\'nav-subcats\'></div>').appendTo(flyout.elem());var panelGro…
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 417,
Column 5:
start tag was here
<script mark="aboveNavInjectionJS" type="text/javascript">…(wlTriggers);});if(panel.isVisible()&&panel.hasInteracted()){logNow();}else{pa…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 419,
Column 2511:
general entity "panel.hasInteracted" not defined and no default entity
…(wlTriggers);});if(panel.isVisible()&&panel.hasInteracted()){logNow();}else{pa…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 419,
Column 2530:
reference to entity "panel.hasInteracted" for which no system identifier could be generated
…panel.isVisible()&&panel.hasInteracted()){logNow();}else{panel.onInteract(logN…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 419,
Column 2510:
entity was defined here
…r(wlTriggers);});if(panel.isVisible()&&panel.hasInteracted()){logNow();}else{p……(0).offset().left;for(var i=1;i<length;i++){if(firstElementLeftPos===$subCatLi……(0).offset().left;for(var i=1;i<length;i++){if(firstElementLeftPos===$subCatLi…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 419,
Column 3314:
an attribute value must be a literal unless it contains only name characters
…u');var $subPanelTitle=$('<span class=\'nav-title nav-item\'>'+ catTitle+'</sp…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 419,
Column 3334:
"NAV-ITEM" is not a member of a group specified for any attribute
…le=$('<span class=\'nav-title nav-item\'>'+ catTitle+'</span>');panel.elem().p……able();};for(var i=0;i<linkKeys.length;i++){var item=linkKeys[i];if(item.panel……able();};for(var i=0;i<linkKeys.length;i++){var item=linkKeys[i];if(item.panel…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 419,
Column 4540:
cannot generate system identifier for general entity "s.digest"
…oveClass("nav-subnav"),s.categoryKey&&s.digest){r.attr("data-category",s.categ…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 419,
Column 4540:
general entity "s.digest" not defined and no default entity
…oveClass("nav-subnav"),s.categoryKey&&s.digest){r.attr("data-category",s.categ…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 419,
Column 4548:
reference to entity "s.digest" for which no system identifier could be generated
…("nav-subnav"),s.categoryKey&&s.digest){r.attr("data-category",s.categoryKey).…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 419,
Column 4539:
entity was defined here
…moveClass("nav-subnav"),s.categoryKey&&s.digest){r.attr("data-category",s.cate……ttr("style",s.style):r.attr("style")&&r.removeAttr("style");var i=function(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 419,
Column 4710:
general entity "r.removeAttr" not defined and no default entity
…ttr("style",s.style):r.attr("style")&&r.removeAttr("style");var i=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 419,
Column 4722:
reference to entity "r.removeAttr" for which no system identifier could be generated
…s.style):r.attr("style")&&r.removeAttr("style");var i=function(t){if(t&&t.href…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 419,
Column 4709:
entity was defined here
…attr("style",s.style):r.attr("style")&&r.removeAttr("style");var i=function(t)……Attr("style");var i=function(t){if(t&&t.href){var n="nav-a",s=t.text,i=t.dataK…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 419,
Column 4756:
general entity "t.href" not defined and no default entity
…Attr("style");var i=function(t){if(t&&t.href){var n="nav-a",s=t.text,i=t.dataK…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 419,
Column 4762:
reference to entity "t.href" for which no system identifier could be generated
…style");var i=function(t){if(t&&t.href){var n="nav-a",s=t.text,i=t.dataKey;if(…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 419,
Column 4755:
entity was defined here
…eAttr("style");var i=function(t){if(t&&t.href){var n="nav-a",s=t.text,i=t.data……='"+t.image+"'class='nav-categ-image' ></a>":s,l=a("<a href='"+t.href+"' class…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 419,
Column 4949:
end tag for element "A" which is not open
…t.image+"'class='nav-categ-image' ></a>":s,l=a("<a href='"+t.href+"' class='"+…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 419,
Column 5143:
cannot generate system identifier for general entity "l.addClass"
…e"),t.rightText=""),t.bold&&!t.image&&l.addClass("nav-b"),t.floatRight&&l.addC…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 419,
Column 5143:
general entity "l.addClass" not defined and no default entity
…e"),t.rightText=""),t.bold&&!t.image&&l.addClass("nav-b"),t.floatRight&&l.addC…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 419,
Column 5153:
reference to entity "l.addClass" for which no system identifier could be generated
…tText=""),t.bold&&!t.image&&l.addClass("nav-b"),t.floatRight&&l.addClass("nav-…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 419,
Column 5142:
entity was defined here
…ge"),t.rightText=""),t.bold&&!t.image&&l.addClass("nav-b"),t.floatRight&&l.add……lass("nav-b"),t.floatRight&&l.addClass("nav-right"),t.flyoutFullWidth&&"0"!==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 419,
Column 5142:
entity was defined here
…ge"),t.rightText=""),t.bold&&!t.image&&l.addClass("nav-b"),t.floatRight&&l.add……utFullWidth&&"0"!==t.flyoutFullWidth&&l.attr("data-nav-flyout-full-width","1")…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 419,
Column 5245:
general entity "l.attr" not defined and no default entity
…utFullWidth&&"0"!==t.flyoutFullWidth&&l.attr("data-nav-flyout-full-width","1")…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 419,
Column 5251:
reference to entity "l.attr" for which no system identifier could be generated
…Width&&"0"!==t.flyoutFullWidth&&l.attr("data-nav-flyout-full-width","1"),t.src…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 419,
Column 5244:
entity was defined here
…outFullWidth&&"0"!==t.flyoutFullWidth&&l.attr("data-nav-flyout-full-width","1"…… g=["nav-image"];t["absolute-right"]&&g.push("nav-image-abs-right"),t["absolut…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 419,
Column 5334:
general entity "g.push" not defined and no default entity
… g=["nav-image"];t["absolute-right"]&&g.push("nav-image-abs-right"),t["absolut…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 419,
Column 5340:
reference to entity "g.push" for which no system identifier could be generated
…av-image"];t["absolute-right"]&&g.push("nav-image-abs-right"),t["absolute-righ…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 419,
Column 5333:
entity was defined here
…r g=["nav-image"];t["absolute-right"]&&g.push("nav-image-abs-right"),t["absolu……bs-right"),t["absolute-right"]&&g.push("nav-image-abs-right"),a("<img src='"+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 419,
Column 5333:
entity was defined here
…r g=["nav-image"];t["absolute-right"]&&g.push("nav-image-abs-right"),t["absolu……+g.join(" ")+"' alt='"+(t.alt||"")+"' />").appendTo(v)}t.rightText&&v.append(t…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 419,
Column 5515:
cannot generate system identifier for general entity "v.append"
…|"")+"' />").appendTo(v)}t.rightText&&v.append(t.rightText),v.appendTo(l),i&&(…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 419,
Column 5515:
general entity "v.append" not defined and no default entity
…|"")+"' />").appendTo(v)}t.rightText&&v.append(t.rightText),v.appendTo(l),i&&(…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 419,
Column 5523:
reference to entity "v.append" for which no system identifier could be generated
…/>").appendTo(v)}t.rightText&&v.append(t.rightText),v.appendTo(l),i&&(a("<span…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 419,
Column 5514:
entity was defined here
…||"")+"' />").appendTo(v)}t.rightText&&v.append(t.rightText),v.appendTo(l),i&&……createTextNode(" "))}};if(s.category&&s.category.data&&(s.category.data.bold=!…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 419,
Column 5725:
general entity "s.category.data" not defined and no default entity
…createTextNode(" "))}};if(s.category&&s.category.data&&(s.category.data.bold=!…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 419,
Column 5740:
reference to entity "s.category.data" for which no system identifier could be generated
…" "))}};if(s.category&&s.category.data&&(s.category.data.bold=!0,i(s.category.…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 419,
Column 5724:
entity was defined here
….createTextNode(" "))}};if(s.category&&s.category.data&&(s.category.data.bold=……ype)for(var d=0;d<s.subnav.data.length;d++)i(s.subnav.data[d]);n.addClass("nav……ype)for(var d=0;d<s.subnav.data.length;d++)i(s.subnav.data[d]);n.addClass("nav…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 431,
Column 13:
end tag for element "SCRIPT" which is not open
</script>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 434,
Column 27:
document type does not allow element "STYLE" here
<style type="text/css"><!--The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 477,
Column 12:
there is no attribute "ID"
<header id="navbar-main" class = "nav-opt-sprite nav-flex nav-locale-de nav-lan…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 34:
there is no attribute "CLASS"
<header id="navbar-main" class = "nav-opt-sprite nav-flex nav-locale-de nav-lan…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 129:
element "HEADER" undefined
…av-flex nav-locale-de nav-lang-de nav-ssl nav-unrec nav-progressive-attribute">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 480,
Column 34:
there is no attribute "CEL_WIDGET_ID"
<div id='navbar' cel_widget_id='Navigation-desktop-navbar'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 32:
there is no attribute "ARIA-LABEL"
role='navigation' aria-label='navigation' class="nav-sprite-v1 celwidget nav-…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 486,
Column 110:
there is no attribute "ARIA-LABEL"
…prites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon.de">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 495,
Column 115:
there is no attribute "DATA-A-MODAL"
…v-progressive-attribute" data-a-modal='{"width":375, "closeButt…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 497,
Column 93:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…ss="nav-sprite nav-progressive-attribute" id="nav-packard-glow-loc-icon"></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 498,
Column 41:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<div id="glow-ingress-block">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 508,
Column 35:
there is no attribute "DATA-ADDNEWADDRESS"
<input data-addnewaddress="add-new" id="unifiedLocation1ClickAddress" n…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 508,
Column 169:
NET-enabling start-tag requires SHORTTAG YES
…n-selection" type="hidden" value="add-new" class="nav-progressive-attribute" />
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 509,
Column 153:
NET-enabling start-tag requires SHORTTAG YES
…election-ubb" type="hidden" value="add-new" class="nav-progressive-attribute"/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 510,
Column 186:
NET-enabling start-tag requires SHORTTAG YES
…ECXp7yDt+f60aAPwbKR5oeCLy6AAAAAGVOzugAAAAB" class="nav-progressive-attribute"/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 515,
Column 18:
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 520,
Column 18:
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 539,
Column 10:
there is no attribute "ROLE"
role="search"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 549,
Column 47:
there is no attribute "DATA-VALUE"
<div class="nav-search-facade" data-value="search-alias=aps">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 555,
Column 24:
there is no attribute "ARIA-DESCRIBEDBY"
aria-describedby="searchDropdownDescription"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 557,
Column 23:
there is no attribute "DATA-NAV-DIGEST"
data-nav-digest="gwQcISAnaHYte8r0yK8PrfYZ6AI="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 558,
Column 25:
there is no attribute "DATA-NAV-SELECTED"
data-nav-selected="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 627,
Column 24:
there is no attribute "AUTOCOMPLETE"
autocomplete="off"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 628,
Column 23:
there is no attribute "PLACEHOLDER"
placeholder="Suche Amazon.de"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 630,
Column 20:
value of attribute "DIR" cannot be "AUTO"; must be one of "LTR", "RTL"
dir="auto"
The value of the attribute is defined to be one of a list of possible
values but in the document it contained something that is not allowed
for that type of attribute. For instance, the “selected” attribute must be either
minimized as “selected”
or spelled out in full as “selected="selected"”; a value like
“selected="true"” is not
allowed.
Line 632,
Column 22:
there is no attribute "ARIA-LABEL"
aria-label="Suche Amazon.de"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 633,
Column 22:
there is no attribute "SPELLCHECK"
spellcheck="false"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 640,
Column 122:
there is no attribute "ARIA-LABEL"
…"nav-search-submit-text nav-sprite nav-progressive-attribute" aria-label="Los">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 656,
Column 47:
cannot generate system identifier for general entity "preferencesReturnUrl"
…f="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_lan…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 656,
Column 47:
general entity "preferencesReturnUrl" not defined and no default entity
…f="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_lan…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 656,
Column 67:
reference to entity "preferencesReturnUrl" for which no system identifier could be generated
…nces/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_lang_ais" id="icp-nav-f…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 656,
Column 46:
entity was defined here
…ef="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_la……?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_lang_ais" id="icp-nav-flyout" cl…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär… <div>DE</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 669,
Column 71:
cannot generate system identifier for general entity "openid.return_to"
…/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazo…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 669,
Column 71:
general entity "openid.return_to" not defined and no default entity
…/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazo…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 669,
Column 87:
reference to entity "openid.return_to" for which no system identifier could be generated
…d.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazon.de%2Fexec%2Fob…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 669,
Column 70:
entity was defined here
…e/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amaz……-redirect%3Dde%26ref_%3Dnav_ya_signin&openid.identity=http%3A%2F%2Fspecs.openi…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 669,
Column 263:
general entity "openid.identity" not defined and no default entity
…-redirect%3Dde%26ref_%3Dnav_ya_signin&openid.identity=http%3A%2F%2Fspecs.openi…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 669,
Column 278:
reference to entity "openid.identity" for which no system identifier could be generated
…26ref_%3Dnav_ya_signin&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 262:
entity was defined here
…e-redirect%3Dde%26ref_%3Dnav_ya_signin&openid.identity=http%3A%2F%2Fspecs.open…….net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=deflex&openid.mode=c…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 669,
Column 342:
general entity "openid.assoc_handle" not defined and no default entity
….net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=deflex&openid.mode=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 669,
Column 361:
reference to entity "openid.assoc_handle" for which no system identifier could be generated
…Fidentifier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid…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 669,
Column 341:
entity was defined here
…d.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=deflex&openid.mode=……ier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claimed…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 669,
Column 369:
general entity "openid.mode" not defined and no default entity
…ier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claimed…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 669,
Column 380:
reference to entity "openid.mode" for which no system identifier could be generated
…openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A…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 669,
Column 368:
entity was defined here
…fier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claime……ndle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.ope…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 669,
Column 395:
general entity "openid.claimed_id" not defined and no default entity
…ndle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.ope…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 669,
Column 412:
reference to entity "openid.claimed_id" for which no system identifier could be generated
…d.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 394:
entity was defined here
…andle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.op…….net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%…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 669,
Column 476:
general entity "openid.ns" not defined and no default entity
….net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%…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 669,
Column 485:
reference to entity "openid.ns" for which no system identifier could be generated
…th%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 475:
entity was defined here
…d.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net……v-progressive-attribute" data-nav-ref="nav_ya_signin" data-nav-role="signin" …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 669,
Column 624:
there is no attribute "DATA-NAV-ROLE"
…av-ref="nav_ya_signin" data-nav-role="signin" data-ux-jq-mouseenter="true" id…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 669,
Column 655:
there is no attribute "DATA-UX-JQ-MOUSEENTER"
…v-role="signin" data-ux-jq-mouseenter="true" id="nav-link-accountList" tabinde…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 669,
Column 717:
there is no attribute "DATA-CSA-C-TYPE"
…untList" tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav-link-acco…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 669,
Column 743:
there is no attribute "DATA-CSA-C-SLOT-ID"
…-csa-c-type="link" data-csa-c-slot-id="nav-link-accountList" data-csa-c-conten…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 669,
Column 788:
there is no attribute "DATA-CSA-C-CONTENT-ID"
…ata-csa-c-slot-id="nav-link-accountList" data-csa-c-content-id="nav_ya_signin">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 670,
Column 36:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<div class="nav-line-1-container"><span id="nav-link-accountList-nav-line-1" …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 684,
Column 39:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<div id="nav-cart-count-container">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 688,
Column 98:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…rt-text-container" class="nav-collapsible-cart-text nav-progressive-attribute">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 712,
Column 33:
there is no attribute "DATA-CSA-C-INTERACTION-EVENTS"
data-csa-c-interaction-events="click" >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 742,
Column 80:
reference to entity "ref_" for which no system identifier could be generated
…br_brands_browse-bin=AmazonBasics&ref_=nav_cs_amazonbasics" class="nav-a " ta…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……f="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="na…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 750,
Column 45:
general entity "node" not defined and no default entity
…f="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="na…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 750,
Column 49:
reference to entity "node" for which no system identifier could be generated
…b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="nav-a " tabindex=…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär…<a href="/Video-Games/b/?ie=UTF8&node=300992&ref_=nav_cs_video_games" class="na…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……ideo-Games/b/?ie=UTF8&node=300992&ref_=nav_cs_video_games" class="nav-a " tab…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……%BCche-haushalt-wohnen/b/?ie=UTF8&node=3167641&ref_=nav_cs_home" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……lt-wohnen/b/?ie=UTF8&node=3167641&ref_=nav_cs_home" class="nav-a " tabindex="…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……href="/Elektronik-Foto/b/?ie=UTF8&node=562066&ref_=nav_cs_electronics" class="…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……ronik-Foto/b/?ie=UTF8&node=562066&ref_=nav_cs_electronics" class="nav-a " tab…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……="/Amazon-Fashion-Mode/b/?ie=UTF8&node=11961464031&ref_=nav_cs_fashion" class=…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……-Mode/b/?ie=UTF8&node=11961464031&ref_=nav_cs_fashion" class="nav-a " tabinde…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……kt-werkzeug-heimwerken/b/?ie=UTF8&node=80084031&ref_=nav_cs_hi" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……imwerken/b/?ie=UTF8&node=80084031&ref_=nav_cs_hi" class="nav-a " tabindex="0"…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……tspiele-Baby-Kleinkind/b/?ie=UTF8&node=12950651&ref_=nav_cs_toys" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……leinkind/b/?ie=UTF8&node=12950651&ref_=nav_cs_toys" class="nav-a " tabindex="…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……/auto-tuning-autoteile/b/?ie=UTF8&node=78191031&ref_=nav_cs_automotive" class=…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……utoteile/b/?ie=UTF8&node=78191031&ref_=nav_cs_automotive" class="nav-a " tabi…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär…<a href="/b/?node=15425785031&ref_=nav_cs_shoppertoolkit" class="nav-a " tabin…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……erie-K%C3%B6rperpflege/b/?ie=UTF8&node=64187031&ref_=nav_cs_hpc" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……erpflege/b/?ie=UTF8&node=64187031&ref_=nav_cs_hpc" class="nav-a " tabindex="0…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……-freizeit-sportartikel/b/?ie=UTF8&node=16435051&ref_=nav_cs_sports" class="nav…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……tartikel/b/?ie=UTF8&node=16435051&ref_=nav_cs_sports" class="nav-a " tabindex…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……Tierbedarf-Tiernahrung/b/?ie=UTF8&node=340852031&ref_=nav_cs_pets" class="nav-…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……nahrung/b/?ie=UTF8&node=340852031&ref_=nav_cs_pets" class="nav-a " tabindex="…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär…… href="/Premium-Beauty/b/?ie=UTF8&node=3765352031&ref_=nav_cs_beauty" class="n…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……Beauty/b/?ie=UTF8&node=3765352031&ref_=nav_cs_beauty" class="nav-a " tabindex…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……usstattung-babyartikel/b/?ie=UTF8&node=355007011&ref_=nav_cs_baby" class="nav-…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……artikel/b/?ie=UTF8&node=355007011&ref_=nav_cs_baby" class="nav-a " tabindex="…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……ef="/Computer-Zubehoer/b/?ie=UTF8&node=340843031&ref_=nav_cs_pc" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……ubehoer/b/?ie=UTF8&node=340843031&ref_=nav_cs_pc" class="nav-a " tabindex="0"…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……n-Weihnachten-Aufladen/b/?ie=UTF8&node=1571256031&ref_=nav_cs_gc" class="nav-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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……fladen/b/?ie=UTF8&node=1571256031&ref_=nav_cs_gc" class="nav-a " tabindex="0"…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……stomer/display.html?nodeId=508510&ref_=nav_cs_help" class="nav-a " tabindex="…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär…<a href="/b/?node=2383621031&ld=AZDEGNOSellC&ref_=nav_cs_sell" class="nav-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 788,
Column 30:
general entity "ld" not defined and no default entity
<a href="/b/?node=2383621031&ld=AZDEGNOSellC&ref_=nav_cs_sell" class="nav-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 788,
Column 32:
reference to entity "ld" for which no system identifier could be generated
<a href="/b/?node=2383621031&ld=AZDEGNOSellC&ref_=nav_cs_sell" class="nav-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 788,
Column 29:
entity was defined here
<a href="/b/?node=2383621031&ld=AZDEGNOSellC&ref_=nav_cs_sell" class="nav-a " ……/?node=2383621031&ld=AZDEGNOSellC&ref_=nav_cs_sell" class="nav-a " tabindex="…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……zeitungen-zubeh%C3%B6r/b/?ie=UTF8&node=530484031&ref_=nav_cs_kindle_books" cla…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 750,
Column 44:
entity was defined here
…ef="/b%C3%BCcher-buch-lesen/b/?ie=UTF8&node=186606&ref_=nav_cs_books" class="n……%C3%B6r/b/?ie=UTF8&node=530484031&ref_=nav_cs_kindle_books" class="nav-a " ta…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……ref="/blackfriday/?_encoding=UTF8&ref_=nav_swm_BFW&pf_rd_p=718bff66-8f74-490e-…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……iday/?_encoding=UTF8&ref_=nav_swm_BFW&pf_rd_p=718bff66-8f74-490e-8745-cf6ace59…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 803,
Column 77:
general entity "pf_rd_p" not defined and no default entity
…iday/?_encoding=UTF8&ref_=nav_swm_BFW&pf_rd_p=718bff66-8f74-490e-8745-cf6ace59…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 803,
Column 84:
reference to entity "pf_rd_p" for which no system identifier could be generated
…encoding=UTF8&ref_=nav_swm_BFW&pf_rd_p=718bff66-8f74-490e-8745-cf6ace598102&pf…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 803,
Column 76:
entity was defined here
…riday/?_encoding=UTF8&ref_=nav_swm_BFW&pf_rd_p=718bff66-8f74-490e-8745-cf6ace5……=718bff66-8f74-490e-8745-cf6ace598102&pf_rd_s=nav-sitewide-msg-export&pf_rd_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 803,
Column 122:
general entity "pf_rd_s" not defined and no default entity
…=718bff66-8f74-490e-8745-cf6ace598102&pf_rd_s=nav-sitewide-msg-export&pf_rd_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 803,
Column 129:
reference to entity "pf_rd_s" for which no system identifier could be generated
…66-8f74-490e-8745-cf6ace598102&pf_rd_s=nav-sitewide-msg-export&pf_rd_t=4201&pf…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 803,
Column 121:
entity was defined here
…p=718bff66-8f74-490e-8745-cf6ace598102&pf_rd_s=nav-sitewide-msg-export&pf_rd_t……98102&pf_rd_s=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m…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 803,
Column 154:
general entity "pf_rd_t" not defined and no default entity
…98102&pf_rd_s=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m…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 803,
Column 161:
reference to entity "pf_rd_t" for which no system identifier could be generated
…f_rd_s=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA67…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 803,
Column 153:
entity was defined here
…598102&pf_rd_s=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_……=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMF…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 803,
Column 167:
general entity "pf_rd_i" not defined and no default entity
…=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMF…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 803,
Column 174:
reference to entity "pf_rd_i" for which no system identifier could be generated
…tewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_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 803,
Column 166:
entity was defined here
…s=nav-sitewide-msg-export&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKM……port&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2B…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 803,
Column 187:
general entity "pf_rd_m" not defined and no default entity
…port&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2B…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 803,
Column 194:
reference to entity "pf_rd_m" for which no system identifier could be generated
…_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2BMM0GMZ2…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 803,
Column 186:
entity was defined here
…xport&pf_rd_t=4201&pf_rd_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2……_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2BMM0GMZ2XSR6" class="nav…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 803,
Column 210:
general entity "pf_rd_r" not defined and no default entity
…_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2BMM0GMZ2XSR6" class="nav…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 803,
Column 217:
reference to entity "pf_rd_r" for which no system identifier could be generated
…ar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2BMM0GMZ2XSR6" class="nav-imageH…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 803,
Column 209:
entity was defined here
…d_i=navbar-4201&pf_rd_m=A1PA6795UKMFR9&pf_rd_r=5G9NCES2BMM0GMZ2XSR6" class="na…….nav-flyout-content{padding:0;}</style><a href='/amazonfresh'><img src='https:…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 842,
Column 384:
end tag for element "A" which is not open
…a/flyout_72dpi._V270092858_.png' /></a>"}}}},"cartTimeout":{"template":{"name"…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 842,
Column 874:
end tag for element "A" which is not open
…t-piv-fallback._V309896279_.jpg' /></a>"}}}},"ewcTimeout":{"template":{"name":…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 844,
Column 107:
end tag for element "SPAN" which is not open
…ss='nav-title'><#=error.title #></span><# } #><# if(error.paragraph) { #><p cl…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 844,
Column 191:
end tag for element "P" which is not open
…av-paragraph'><#=error.paragraph #></p><# } #><# if(error.button) { #><a href=…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 844,
Column 343:
end tag for element "SPAN" which is not open
…n' ><span class='nav-action-inner'><#=error.button.text #></span></a><# } #>");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 844,
Column 347:
end tag for element "A" which is not open
…n' ><span class='nav-action-inner'><#=error.button.text #></span></a><# } #>");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 1225,
Column 31:
character "-" is not allowed in the value of attribute "TABINDEX"
<a id="skippedLink" tabindex="-1"></a>
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 1236,
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 1240,
Column 84:
there is no attribute "DATA-CSA-OP-LOG-RENDER"
…esktop-banner" data-csa-op-log-render="" data-csa-c-type="widget" data-csa-c-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 1240,
Column 103:
there is no attribute "DATA-CSA-C-TYPE"
…-csa-op-log-render="" data-csa-c-type="widget" data-csa-c-slot-id="desktop-her…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 1240,
Column 131:
there is no attribute "DATA-CSA-C-SLOT-ID"
…sa-c-type="widget" data-csa-c-slot-id="desktop-hero-order" class="celwidget"><…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 1240,
Column 225:
there is no attribute "DATA-AUTOROTATION-DELAY"
…op-herotator" data-autorotation-delay="5000" class="a-section a-spacing-none 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 1240,
Column 312:
there is no attribute "DATA-A-CAROUSEL-OPTIONS"
…ve tall"><div data-a-carousel-options="{"set_size":6,"minimum_g…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 1240,
Column 589:
there is no attribute "DATA-A-DISPLAY-STRATEGY"
…":6000}" data-a-display-strategy="single" data-a-transition-strategy="sli…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 1240,
Column 625:
there is no attribute "DATA-A-TRANSITION-STRATEGY"
…y="single" data-a-transition-strategy="slideCircular" data-a-class="desktop" c…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 1240,
Column 654:
there is no attribute "DATA-A-CLASS"
…strategy="slideCircular" data-a-class="desktop" class="a-begin a-carousel-cont…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 1240,
Column 1353:
there is no attribute "ROLE"
…viewport"><ol class="a-carousel" role="list"><!--gw:component:hero-h1--><li cl…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 1240,
Column 1420:
there is no attribute "ROLE"
…h1--><li class="a-carousel-card" role="listitem"><div id="gw-ftGr-desktop-hero…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 1240,
Column 1722:
there is no attribute "DATA-PF_RD_P"
…-47a8-972b-1d5f27b8d36b" data-pf_rd_p="d011dc15-524b-46c9-9aa9-290a686a2edb" d…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 1240,
Column 1775:
there is no attribute "DATA-PD_RD_WG"
…46c9-9aa9-290a686a2edb" data-pd_rd_wg="7DEtD" data-pd_rd_w="VQlpV" data-pd_rd_…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 1240,
Column 1796:
there is no attribute "DATA-PD_RD_W"
…b" data-pd_rd_wg="7DEtD" data-pd_rd_w="VQlpV" data-pd_rd_r="edd500bd-e533-47a8…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 1240,
Column 1817:
there is no attribute "DATA-PD_RD_R"
…tD" data-pd_rd_w="VQlpV" data-pd_rd_r="edd500bd-e533-47a8-972b-1d5f27b8d36b" d…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 1240,
Column 1973:
there is no attribute "DATA-CSA-C-CONTENT-ID"
…desktop-hero-1" data-csa-c-content-id="amzn1.sym.d011dc15-524b-46c9-9aa9-290a6…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 1240,
Column 2041:
there is no attribute "DATA-CSA-C-PAINTER"
…9aa9-290a686a2edb" data-csa-c-painter="cropped-image-link"><style>._cropped-im…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 1240,
Column 2068:
required attribute "TYPE" not specified
…-c-painter="cropped-image-link"><style>._cropped-image-link_style_cropped-imag…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 1240,
Column 2068:
document type does not allow element "STYLE" here
…-c-painter="cropped-image-link"><style>._cropped-image-link_style_cropped-imag…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 1244,
Column 170:
there is no attribute "DATA-CARD-METRICS-ID"
…HLqrMjK91sj0Aeg" data-card-metrics-id="cropped-image-link_desktop-gateway-atf_…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 1244,
Column 685:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…link_style_fluidImageContainer__2jd50"><img alt="Erlebe zauberhafte Weihnachte…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 1245,
Column 60:
there is no attribute "DATA-A-HIRES"
…style_fluidImage__iJ3aE" data-a-hires="https://m.media-amazon.com/images/I/71Y…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 1245,
Column 122:
NET-enabling start-tag requires SHORTTAG YES
…com/images/I/71YufkDC1NL._SX3000_.jpg"/></div></a></div><script>(function(f){f…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1245,
Column 147:
required attribute "TYPE" not specified
…_SX3000_.jpg"/></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1248,
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 1248,
Column 8:
document type does not allow element "SCRIPT" here; assuming missing "LI" start-tag
<script><script>GwInstrumentation.markH1Af({ uri: "/ah/ajax/counter?ctr=desktop_ajax_at…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 1267,
Column 8:
required attribute "TYPE" not specified
<script>P.when("LinkDecorator").execute("LDEventListenerInit", function(ld){ ld…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 1268,
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 1276,
Column 138:
there is no attribute "DATA-GRID-BREAKPOINT"
…"gw-card-layout" data-grid-breakpoint="ws" data-flow-dir="h" class="a-section …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 1276,
Column 157:
there is no attribute "DATA-FLOW-DIR"
…ta-grid-breakpoint="ws" data-flow-dir="h" class="a-section a-spacing-none gw-c…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 1276,
Column 216:
required attribute "TYPE" not specified
…"ws" data-flow-dir="h" class="a-section a-spacing-none gw-card-layout"><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 1285,
Column 35:
there is no attribute "DATA-GWI"
<div id="desktop-grid-1" data-gwi="{"visible":"desktop-grid-1-vi…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 1285,
Column 163:
there is no attribute "DATA-DISPLAY-AT"
…grid-1-active"}" data-display-at="smws" data-order-ws="1" class="gw-col c…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 1285,
Column 184:
there is no attribute "DATA-ORDER-WS"
… data-display-at="smws" data-order-ws="1" class="gw-col csm-placement-id-df273…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 1285,
Column 412:
there is no attribute "DATA-ORDER-SM"
…4d75-b05e-f2758a060830" data-order-sm="1" data-pf_rd_p="df27379f-01de-4ce6-816…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 1285,
Column 573:
there is no attribute "DATA-REF_"
…176-4d75-b05e-f2758a060830" data-ref_="pd_gw_unk" data-csa-op-log-render="" da…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 1285,
Column 796:
required attribute "TYPE" not specified
…ter="fluid-quad-image-label-v2"><style>._fluid-quad-image-label-v2_style_fluid…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 1285,
Column 796:
document type does not allow element "STYLE" here
…ter="fluid-quad-image-label-v2"><style>._fluid-quad-image-label-v2_style_fluid…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 1289,
Column 118:
there is no attribute "DATA-A-CARD-TYPE"
…adImageLabel__3b-Iv" data-a-card-type="basic" id="CardInstanceNmCJvLpEbL4UkcDK…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 1289,
Column 1147:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Computer & Zubehör" src=…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 1289,
Column 1648:
NET-enabling start-tag requires SHORTTAG YES
…DE_GL_PC_desk._SY232_CB603710907_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1289,
Column 1778:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1289,
Column 2547:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Elektronik-Foto" src="https:/…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 1289,
Column 3058:
NET-enabling start-tag requires SHORTTAG YES
…ctronics_desk._SY232_CB603710907_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1289,
Column 3188:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1289,
Column 3985:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Kopfhörer & Zubehör" sr…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 1289,
Column 4500:
NET-enabling start-tag requires SHORTTAG YES
…wireless_desk._SY232_CB603710907_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1289,
Column 4630:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1289,
Column 5397:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Video Games" src="https://ima…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 1289,
Column 5902:
NET-enabling start-tag requires SHORTTAG YES
…op_videogames._SY232_CB602519622_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1289,
Column 6032:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1289,
Column 6541:
required attribute "TYPE" not specified
…Jetzt entdecken</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1291,
Column 1977:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Adventskalender" src="https:/…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 1291,
Column 2436:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_it_IT._SY232_CB578496054_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1291,
Column 2566:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1291,
Column 3520:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Weihnachtsbäume" src="https:…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 1291,
Column 3980:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_it_IT._SY232_CB578496054_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1291,
Column 4110:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1291,
Column 4938:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Weihnachtsdeko" src="https://…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 1291,
Column 5396:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_it_IT._SY232_CB578496054_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1291,
Column 5526:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1291,
Column 6455:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Angebote für Geschenke" src=…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 1291,
Column 6922:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_it_IT._SY232_CB578496054_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1291,
Column 7052:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1291,
Column 7600:
required attribute "TYPE" not specified
…ür Weihnachten</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1293,
Column 1917:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Fernseher" src="https://image…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 1293,
Column 2409:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB658795075_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1293,
Column 2539:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1293,
Column 3299:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Blu-ray-Player" src="https://…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 1293,
Column 3796:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB658795075_.png"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1293,
Column 3926:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1293,
Column 4707:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Beamer" src="https://images-e…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 1293,
Column 5196:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB658795075_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1293,
Column 5326:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1293,
Column 6082:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Lautsprecher" src="https://im…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 1293,
Column 6577:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB658795075_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1293,
Column 6707:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1293,
Column 7220:
required attribute "TYPE" not specified
…Jetzt entdecken</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1295,
Column 797:
required attribute "TYPE" not specified
…csa-c-painter="deal-of-the-day"><style>._deal-of-the-day_style_badgeContainer_…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 1295,
Column 797:
document type does not allow element "STYLE" here
…csa-c-painter="deal-of-the-day"><style>._deal-of-the-day_style_badgeContainer_…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 1302,
Column 384:
there is no attribute "DATA-CSA-C-ITEM-ID"
…-csa-c-type="item" data-csa-c-item-id="amzn1.deal.31b8dead" data-csa-c-posx="1…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 1302,
Column 422:
there is no attribute "DATA-CSA-C-POSX"
…"amzn1.deal.31b8dead" data-csa-c-posx="1" data-csa-c-owner="DealsX"><a class="…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 1302,
Column 443:
there is no attribute "DATA-CSA-C-OWNER"
… data-csa-c-posx="1" data-csa-c-owner="DealsX"><a class="a-spacing-small a-lin…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 1302,
Column 907:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…<div class="a-section a-spacing-small"><div class="a-section a-spacing-mini ce…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 1302,
Column 1237:
NET-enabling start-tag requires SHORTTAG YES
…m/images/I/41Dt-V8gtvL._AC_SY460_.jpg"/></div></div><div class="a-section a-sp…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1302,
Column 1446:
there is no attribute "DATA-COMPONENT"
…badgeContainer__2F-_x" data-component="dui-badge"><div style="background-color…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 1302,
Column 2019:
there is no attribute "DATA-A-WORD-BREAK"
…base a-text-normal" data-a-word-break="normal" data-a-max-rows="2" data-a-over…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 1302,
Column 2044:
there is no attribute "DATA-A-MAX-ROWS"
…a-word-break="normal" data-a-max-rows="2" data-a-overflow-marker="&hellip;…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 1302,
Column 2071:
there is no attribute "DATA-A-OVERFLOW-MARKER"
…a-max-rows="2" data-a-overflow-marker="&hellip;" style="line-height:1.3em …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 1302,
Column 2733:
required attribute "TYPE" not specified
…eitere Angebote</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1303,
Column 8:
required attribute "TYPE" not specified
<script>P.when('af').execute(function(){P.load.js('https://images-eu.ssl-images…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 1305,
Column 8:
required attribute "TYPE" not specified
<script>if(window.mixTimeout){window.mixTimeout('deal-of-the-day', 'CardInstanc…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 1309,
Column 21:
there is no attribute "DATA-DISPLAY-AT"
<hr data-display-at="smws" data-order-sm="4" data-order-ws="5" class="card-flow…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 1309,
Column 42:
there is no attribute "DATA-ORDER-SM"
… data-display-at="smws" data-order-sm="4" data-order-ws="5" class="card-flow-r…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 1309,
Column 60:
there is no attribute "DATA-ORDER-WS"
…at="smws" data-order-sm="4" data-order-ws="5" class="card-flow-row-break"></hr>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 1309,
Column 96:
end tag for element "HR" which is not open
…at="smws" data-order-sm="4" data-order-ws="5" class="card-flow-row-break"></hr>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 1310,
Column 1937:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Schlagzeug" src="https://imag…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 1310,
Column 2412:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB639403901_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1310,
Column 2542:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1310,
Column 3311:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="DJ- & VJ-Equipment" src="…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 1310,
Column 3798:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB637753685_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1310,
Column 3928:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1310,
Column 4733:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Piano & Keyboard" src="ht…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 1310,
Column 5218:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB637753685_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1310,
Column 5348:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1310,
Column 6114:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Mikrofone" src="https://image…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 1310,
Column 6588:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB639403901_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1310,
Column 6718:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1310,
Column 7231:
required attribute "TYPE" not specified
…Jetzt entdecken</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1312,
Column 794:
required attribute "TYPE" not specified
…inter="fluid-fat-image-link-v2"><style>._fluid-fat-image-link-v2_style_fluidFa…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 1312,
Column 794:
document type does not allow element "STYLE" here
…inter="fluid-fat-image-link-v2"><style>._fluid-fat-image-link-v2_style_fluidFa…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 1315,
Column 808:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1315,
Column 1389:
NET-enabling start-tag requires SHORTTAG YES
…x608_2X_de_DE._SY608_CB626502628_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1315,
Column 1431:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1315,
Column 1751:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1317,
Column 1926:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Drogerie" src="https://images…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 1317,
Column 2438:
NET-enabling start-tag requires SHORTTAG YES
…rugstore_desk._SY232_CB603712708_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1317,
Column 2568:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1317,
Column 3318:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Kosmetik" src="https://images…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 1317,
Column 3806:
NET-enabling start-tag requires SHORTTAG YES
…E_beauty_desk._SY232_CB603712708_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1317,
Column 3936:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1317,
Column 4723:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Körperpflegegeräte" src="ht…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 1317,
Column 5235:
NET-enabling start-tag requires SHORTTAG YES
…onalCare_desk._SY232_CB602565505_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1317,
Column 5365:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1317,
Column 6129:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Hautpflege" src="https://imag…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 1317,
Column 6623:
NET-enabling start-tag requires SHORTTAG YES
…desk_skincare._SY232_CB602543946_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1317,
Column 6753:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1317,
Column 7263:
required attribute "TYPE" not specified
…Jetzt entdecken</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1319,
Column 1587:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1319,
Column 2156:
NET-enabling start-tag requires SHORTTAG YES
…x608_2X_de_DE._SY608_CB626507292_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1319,
Column 2198:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1319,
Column 2518:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1321,
Column 98:
end tag for element "HR" which is not open
…="smws" data-order-sm="10" data-order-ws="10" class="card-flow-row-break"></hr>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 1322,
Column 33:
required attribute "TYPE" not specified
<!--RowSeparator::3::C--><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 1417,
Column 840:
end tag for element "SPAN" which is not open
…lass='nav-action-inner'>Anmelden</span></a><div id='nav-flyout-ya-newCust' cla…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 1417,
Column 844:
end tag for element "A" which is not open
…='nav-action-inner'>Anmelden</span></a><div id='nav-flyout-ya-newCust' class='…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 1417,
Column 1530:
end tag for element "A" which is not open
…ofollow' class='nav-a'>Starte hier.</a></div></div></div><div id='nav-al-wishl…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 1417,
Column 1536:
end tag for "SCRIPT" omitted, but its declaration does not permit this
…w' class='nav-a'>Starte hier.</a></div></div></div><div id='nav-al-wishlist' c…
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 1414,
Column 1:
start tag was here
<script type="text/javascript">…v-a'>Starte hier.</a></div></div></div><div id='nav-al-wishlist' class='nav-al…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 1417,
Column 1772:
reference to entity "ref_" for which no system identifier could be generated
…chenkefinder/gfhz/?_encoding=UTF8&ref_=nav_wishlist_gf' class='nav-link nav-it…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……st/ls?triggerElementID=createList&ref_=nav_ListFlyout_navFlyout_createList_lv_…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……'/hz/wishlist/ls?requiresSignIn=1&ref_=nav_AccountFlyout_wl' class='nav-link n…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……'/gp/browse.html?node=14154536031&ref_=nav_AccountFlyout_deb2b_reg' class='nav…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……='/gp/browse.html?node=5686557031&ref_=nav_AccountFlyout_pmu' class='nav-link …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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……='/gp/browse.html?node=3279204031&ref_=nav_AccountFlyout_piv' class='nav-link …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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……av-item'><span class='nav-text'>Meine Apps & Geräte</span></a></div></div>" },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 1419,
Column 148:
reference to entity "openid.return_to" for which no system identifier could be generated
…d.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazon.de%2Fexec%2Fob…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 669,
Column 70:
entity was defined here
…e/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amaz……_%3Dnav_custrec_signin&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 262:
entity was defined here
…e-redirect%3Dde%26ref_%3Dnav_ya_signin&openid.identity=http%3A%2F%2Fspecs.open……Fidentifier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid…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 669,
Column 341:
entity was defined here
…d.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=deflex&openid.mode=……openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A…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 669,
Column 368:
entity was defined here
…fier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claime……d.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 394:
entity was defined here
…andle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.op……th%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 475:
entity was defined here
…d.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net……d.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazon.de%2Fexec%2Fob…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 669,
Column 70:
entity was defined here
…e/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amaz……%3Dnav_custrec_newcust&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 262:
entity was defined here
…e-redirect%3Dde%26ref_%3Dnav_ya_signin&openid.identity=http%3A%2F%2Fspecs.open……Fidentifier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid…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 669,
Column 341:
entity was defined here
…d.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=deflex&openid.mode=……openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A…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 669,
Column 368:
entity was defined here
…fier_select&openid.assoc_handle=deflex&openid.mode=checkid_setup&openid.claime……d.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 394:
entity was defined here
…andle=deflex&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.op……th%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F…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 669,
Column 475:
entity was defined here
…d.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net…… } else {#> <span class=' <# } #> <# if(item.panelKey) { #> …The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.
Line 1420,
Column 2712:
NET-enabling start-tag requires SHORTTAG YES
…>px; width:<#=item.image.width #>px;' /> <# } #> <# if(item.text) { …
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1420,
Column 2712:
required attribute "ALT" not specified
…>px; width:<#=item.image.width #>px;' /> <# } #> <# if(item.text) { …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 1420,
Column 3160:
document type does not allow element "A" here
…a href='<#=cItem.url #>' class='nav-a'><#=cItem.text #></a><# } else if (cItem…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 1420,
Column 3435:
end tag for element "SPAN" which is not open
… </a> <# } else {#> </span> <# } #> <# } #> <# if(item.…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 1420,
Column 3611:
unclosed start-tag requires SHORTTAG YES
…} #> <img class='nav-image' <# if(item.id) { #> id='<#=item.i…The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.
Line 1420,
Column 3611:
required attribute "SRC" not specified
…} #> <img class='nav-image' <# if(item.id) { #> id='<#=item.i…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 1420,
Column 3611:
required attribute "ALT" not specified
…} #> <img class='nav-image' <# if(item.id) { #> id='<#=item.i…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 1420,
Column 4198:
unclosed start-tag requires SHORTTAG YES
…div class='nav_sv_fo_v_button' <# if (row.elementStyle) { #> s…The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.
Line 1420,
Column 4597:
an attribute value literal can occur in an attribute specification list only after a VI delimiter
…lumn <#=(j === 0) ? 'nav_sv_fo_v_first' : '' #>'> <ul class='<#=list.…
Have you forgotten the "equal" sign marking the separation
between the attribute and its declared value?
Typical syntax is attribute="value".
Line 1420,
Column 4664:
start tag for "LI" omitted, but its declaration does not permit this
…s='<#=list.elementClass #>'> <# jQuery.each(list.linkList, function (…… <# } #> </li> <# }); #> </ul> </div> …You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 1423,
Column 9:
end tag for element "SCRIPT" which is not open
</script>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 1467,
Column 324:
there is no attribute "DATA-COL-SPAN-WS"
…top-1-active"}" data-col-span-ws="4" data-col-span-sm="3" data-order-ws="…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 1467,
Column 345:
there is no attribute "DATA-COL-SPAN-SM"
…data-col-span-ws="4" data-col-span-sm="3" data-order-ws="2" data-order-sm="2" …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 1467,
Column 1203:
value of attribute "ID" invalid: "1" cannot start a name
…er-v2_desktop-gateway-btf_0"><div id="1f6ec19d-650d-482b-9938-6d0c3383ada8" cl…
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 1467,
Column 2108:
there is no attribute "ROLE"
…-horizontal feed-carousel-shelf" role="list"><li data-sgproduct="{"asin&q…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 1467,
Column 2134:
there is no attribute "DATA-SGPRODUCT"
…shelf" role="list"><li data-sgproduct="{"asin":""}" class=…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 1467,
Column 2870:
NET-enabling start-tag requires SHORTTAG YES
…00x400_2X_de_DE_new._CB575218538_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 3707:
NET-enabling start-tag requires SHORTTAG YES
…_en_US_CB638067402_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 4544:
NET-enabling start-tag requires SHORTTAG YES
…_en_US_CB638070184_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 5386:
NET-enabling start-tag requires SHORTTAG YES
…_en_US_CB638069932_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 6222:
NET-enabling start-tag requires SHORTTAG YES
…_en_US_CB638069710_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 7073:
NET-enabling start-tag requires SHORTTAG YES
…_en_US_CB638068940_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 7918:
NET-enabling start-tag requires SHORTTAG YES
…_en_US_CB638069016_._CB608159219_.jpg"/></a></span></li></ul><div class="spinn…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1467,
Column 7974:
there is no attribute "ARIA-HIDDEN"
…</ul><div class="spinner" aria-hidden="true"><i class="gw-spinner" role="prese…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 1467,
Column 8008:
there is no attribute "ROLE"
…den="true"><i class="gw-spinner" role="presentation"></i></div></div><a aria-l…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 1467,
Column 8143:
character "-" is not allowed in the value of attribute "TABINDEX"
…carousel-control feed-left" tabindex="-1" href="#"><span class="gw-icon feed-a…
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 1467,
Column 8301:
character "-" is not allowed in the value of attribute "TABINDEX"
…arousel-control feed-right" tabindex="-1" href="#"><span class="gw-icon feed-a…
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 1467,
Column 8676:
there is no attribute "ID"
…el", 10, 9 ); });</script><script id="1f6ec19d-650d-482b-9938-6d0c3383ada8-bt…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 1467,
Column 9601:
end tag for element "A" which is not open
…S_CB638070656_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{"…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 1467,
Column 9608:
end tag for element "SPAN" which is not open
…070656_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{"asin&qu…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 1467,
Column 9613:
end tag for element "LI" which is not open
…6_._CB608159219_.jpg"/></a></span></li><li data-sgproduct="{"asin":&…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 1467,
Column 10403:
end tag for element "A" which is not open
…0x400_2X_de_DE._CB576468853_.jpg"/></a></span></li></script><script type="text…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 1467,
Column 10410:
end tag for element "SPAN" which is not open
…X_de_DE._CB576468853_.jpg"/></a></span></li></script><script type="text/javasc…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 1467,
Column 10415:
end tag for element "LI" which is not open
…DE._CB576468853_.jpg"/></a></span></li></script><script type="text/javascript"…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 1467,
Column 10765:
required attribute "TYPE" not specified
… window));</script></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1469,
Column 96:
end tag for element "HR" which is not open
…at="smws" data-order-sm="2" data-order-ws="2" class="card-flow-row-break"></hr>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 1470,
Column 1053:
value of attribute "ID" invalid: "6" cannot start a name
…er-v2_desktop-gateway-btf_1"><div id="6a28ed08-b1bb-4221-bdc0-875192121b4a" cl…
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 1470,
Column 2899:
NET-enabling start-tag requires SHORTTAG YES
…16_400x400_2X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 3715:
NET-enabling start-tag requires SHORTTAG YES
…21_400x400_2X_de_DE._CB574624639_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 4536:
NET-enabling start-tag requires SHORTTAG YES
…17_400x400_2X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 5339:
NET-enabling start-tag requires SHORTTAG YES
…18_400x400_2X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 6139:
NET-enabling start-tag requires SHORTTAG YES
…19_400x400_2X_de_DE._CB575225168_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 6936:
NET-enabling start-tag requires SHORTTAG YES
…25_400x400_2X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{&…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 7752:
NET-enabling start-tag requires SHORTTAG YES
…22_400x400_2X_de_DE._CB576578629_.jpg"/></a></span></li></ul><div class="spinn…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1470,
Column 7977:
character "-" is not allowed in the value of attribute "TABINDEX"
…carousel-control feed-left" tabindex="-1" href="#"><span class="gw-icon feed-a…
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 1470,
Column 8135:
character "-" is not allowed in the value of attribute "TABINDEX"
…arousel-control feed-right" tabindex="-1" href="#"><span class="gw-icon feed-a…
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 1470,
Column 9347:
end tag for element "A" which is not open
…0x400_2X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{"…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 1470,
Column 9354:
end tag for element "SPAN" which is not open
…X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{"asin&qu…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 1470,
Column 9359:
end tag for element "LI" which is not open
…DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{"asin":&…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 1470,
Column 10412:
end tag for element "A" which is not open
…0x400_2X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{"…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 1470,
Column 10419:
end tag for element "SPAN" which is not open
…X_de_DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{"asin&qu…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 1470,
Column 10424:
end tag for element "LI" which is not open
…DE._CB576578629_.jpg"/></a></span></li><li data-sgproduct="{"asin":&…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 1470,
Column 11160:
end tag for element "A" which is not open
…0x400_2X_de_DE._CB576578629_.jpg"/></a></span></li></script><script type="text…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 1470,
Column 11167:
end tag for element "SPAN" which is not open
…X_de_DE._CB576578629_.jpg"/></a></span></li></script><script type="text/javasc…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 1470,
Column 11172:
end tag for element "LI" which is not open
…DE._CB576578629_.jpg"/></a></span></li></script><script type="text/javascript"…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 1470,
Column 11522:
required attribute "TYPE" not specified
… window));</script></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1472,
Column 96:
end tag for element "HR" which is not open
…at="smws" data-order-sm="3" data-order-ws="3" class="card-flow-row-break"></hr>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 1473,
Column 1621:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1473,
Column 2301:
NET-enabling start-tag requires SHORTTAG YES
…essories_Desk._SY608_CB598504051_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1473,
Column 2343:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1473,
Column 2663:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1475,
Column 1625:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1475,
Column 2204:
NET-enabling start-tag requires SHORTTAG YES
…58x608_-_Copy._SY608_CB640553673_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1475,
Column 2246:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1475,
Column 2566:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1477,
Column 1609:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1477,
Column 2291:
NET-enabling start-tag requires SHORTTAG YES
…yCarrier_Desk._SY608_CB598504051_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1477,
Column 2333:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1477,
Column 2653:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1479,
Column 76:
end tag for element "HR" which is not open
<hr data-display-at="sm" data-order-sm="4" class="card-flow-row-break"></hr>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 1480,
Column 1925:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Objektive" src="https://image…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 1480,
Column 2389:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB655398559_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1480,
Column 2519:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1480,
Column 3274:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Blitzgeräte" src="https://im…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 1480,
Column 3741:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB655398559_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1480,
Column 3871:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1480,
Column 4660:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Sofortbildkameras" src="https…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 1480,
Column 5132:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB655398558_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1480,
Column 5262:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1480,
Column 6045:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Actionkameras & Zubehör"…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 1480,
Column 6528:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB655398558_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1480,
Column 6658:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1480,
Column 7199:
required attribute "TYPE" not specified
…Jetzt entdecken</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1482,
Column 76:
end tag for element "HR" which is not open
<hr data-display-at="ws" data-order-ws="4" class="card-flow-row-break"></hr>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 1483,
Column 1621:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1483,
Column 2187:
NET-enabling start-tag requires SHORTTAG YES
…x608_2X_de_DE._SY608_CB626500299_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1483,
Column 2229:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1483,
Column 2549:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1485,
Column 1574:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1485,
Column 2158:
NET-enabling start-tag requires SHORTTAG YES
…_Petcare_EN_1._SY608_CB601300556_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1485,
Column 2200:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1485,
Column 2520:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1487,
Column 76:
end tag for element "HR" which is not open
<hr data-display-at="sm" data-order-sm="9" class="card-flow-row-break"></hr>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 1488,
Column 1601:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1488,
Column 2082:
NET-enabling start-tag requires SHORTTAG YES
…022/Watches_2._SY608_CB625098338_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1488,
Column 2124:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1488,
Column 2444:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1490,
Column 1598:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1490,
Column 2268:
NET-enabling start-tag requires SHORTTAG YES
…yCarrier_Desk._SY608_CB598504051_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1490,
Column 2310:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1490,
Column 2630:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1492,
Column 76:
end tag for element "HR" which is not open
<hr data-display-at="ws" data-order-ws="9" class="card-flow-row-break"></hr>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 1493,
Column 1634:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1493,
Column 2210:
NET-enabling start-tag requires SHORTTAG YES
…x608_2X_de_DE._SY608_CB626506870_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1493,
Column 2252:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1493,
Column 2572:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1495,
Column 77:
end tag for element "HR" which is not open
<hr data-display-at="sm" data-order-sm="12" class="card-flow-row-break"></hr>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 1496,
Column 1603:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1496,
Column 2180:
NET-enabling start-tag requires SHORTTAG YES
…x608_2X_de_DE._SY608_CB626294019_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1496,
Column 2222:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1496,
Column 2542:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1498,
Column 1921:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Staubsauger" src="https://ima…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 1498,
Column 2389:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB657337446_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1498,
Column 2519:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1498,
Column 3281:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Kaffee & Tee" src="https:…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 1498,
Column 3754:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB657337446_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1498,
Column 3884:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1498,
Column 4682:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Reinigungszubehör" src="http…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 1498,
Column 5157:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB657337441_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1498,
Column 5287:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1498,
Column 6054:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…l-v2_style_fluidImageContainer__2SOMr"><img alt="Küchengeräte" src="https://…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 1498,
Column 6525:
NET-enabling start-tag requires SHORTTAG YES
…x232_2X_de_DE._SY232_CB657337446_.jpg"/></div><div class="a-section a-spacing-…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1498,
Column 6655:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…NSV aok-inline-block aok-align-center"><span class="a-size-small a-color-base …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 1498,
Column 7183:
required attribute "TYPE" not specified
…Jetzt entdecken</a></div></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1500,
Column 1594:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…v2_style_fluidFatImageLinkBody__1LsOX"><div class="a-section a-spacing-none _f…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 1500,
Column 2260:
NET-enabling start-tag requires SHORTTAG YES
…Backpack_Desk._SY608_CB598504051_.jpg"/></div></div><div class="a-cardui-foote…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1500,
Column 2302:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…div></div><div class="a-cardui-footer"><span class="a-truncate see-more" data-…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 1500,
Column 2622:
required attribute "TYPE" not specified
…></span></span></div></a></div><script>(function(f){f(P._namespace('gwiAutoIns…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 1502,
Column 77:
end tag for element "HR" which is not open
<hr data-display-at="ws" data-order-ws="12" class="card-flow-row-break"></hr>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 1503,
Column 33:
required attribute "TYPE" not specified
<!--RowSeparator::9::C--><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 1523,
Column 447:
required attribute "ALT" not specified
…ybh/loading-4x-gray._CB485916907_.gif'> </td> </tr> </table> </div> <div id='r…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 1527,
Column 34:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<div class="navFooterBackToTop">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 1541,
Column 59:
reference to entity "ref_" for which no system identifier could be generated
…f="/gp/browse.html?node=202588011&ref_=footer_careers" class="nav_a">Karriere …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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……ww.aboutamazon.de/?utm_source=gateway&utm_medium=footer" class="nav_a">Erfahre…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 1547,
Column 71:
general entity "utm_medium" not defined and no default entity
…ww.aboutamazon.de/?utm_source=gateway&utm_medium=footer" class="nav_a">Erfahre…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 1547,
Column 81:
reference to entity "utm_medium" for which no system identifier could be generated
…azon.de/?utm_source=gateway&utm_medium=footer" class="nav_a">Erfahre mehr übe…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 1547,
Column 70:
entity was defined here
…www.aboutamazon.de/?utm_source=gateway&utm_medium=footer" class="nav_a">Erfahr……href="/gp/browse.html?node=505050&ref_=footer_nav_legal" class="nav_a">Impress…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……zon.de/sell.html?ld=AZDESOAFooter&ref_=sdde_soa" class="nav_a">Jetzt verkaufen…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……"/gp/browse.html?node=15426871031&ref_=footer_swp" class="nav_a">Einkaufen mit…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……f="/gp/browse.html?node=459632031&ref_=footer_moneystore" class="nav_a">Kredit…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……="/gp/browse.html?node=1571256031&ref_=footer_giftcards" class="nav_a">Gutsche…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……play.html?nodeId=GFB7JMU32WA3P66Y&ref_=footer_rechnung" class="nav_a">Monatsab…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……stomer/display.html?nodeId=504928&ref_=footer_bankeinzug" class="nav_a">Bankei…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……mer/display.html?nodeId=200219670&ref_=footer_tfx" class="nav_a">Amazon Währu…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……"/gp/browse.html?node=13847036031&ref_=footer_purchase_code" class="nav_a">Ama…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……play.html?nodeId=GDFU3JS5AL6SYHRD&ref_=footer_covid" class="nav_a">Amazon und …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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……stomer/display.html?nodeId=504938&ref_=footer_shiprates" class="nav_a">Versand…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……mer/display.html?nodeId=201819410&ref_=footer_disposal" class="nav_a">Recyclin…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……="/gp/browse.html?node=4951330031&ref_=footer_mobapp" class="nav_a">Amazon App…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……stomer/display.html?nodeId=504874&ref_=footer_gw_m_b_cs" class="nav_a">Kundens…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……play.html?nodeId=GUUVBZ8WGVFP8R8X&ref_=nav_foot_accessibility" class="nav_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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär… <div class="navFooterLine navFooterLogoLine">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 1682,
Column 46:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<div class="nav-logo-base nav-sprite"></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 1688,
Column 32:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
class="navFooterLine">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 1689,
Column 23:
document type does not allow element "STYLE" here
<style type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 1694,
Column 65:
reference to entity "preferencesReturnUrl" for which no system identifier could be generated
…nces/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=footer_lang" aria-label="Wähl…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 656,
Column 46:
entity was defined here
…ef="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_la……?ie=UTF8&preferencesReturnUrl=%2F&ref_=footer_lang" aria-label="Wähle eine Sp…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……cp-nav-globe-img-2 icp-button-globe-2"></div><span class="icp-color-base">Deut…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 1700,
Column 23:
document type does not allow element "STYLE" here
<style type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 1703,
Column 68:
reference to entity "preferencesReturnUrl" for which no system identifier could be generated
…s/country?ie=UTF8&preferencesReturnUrl=%2F&ref_=footer_icp_cp" aria-label="Wä…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 656,
Column 46:
entity was defined here
…ef="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_la……?ie=UTF8&preferencesReturnUrl=%2F&ref_=footer_icp_cp" aria-label="Wähle ein L…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……ass="navFooterDescItem"><a href=https://advertising.amazon.de/?ref=footer_advt…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1714,
Column 210:
end tag for element "A" which is not open
…nden, gewinnen<br>und binden</span></a></td><td class="navFooterDescSpacer" st…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 1715,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://music.amazon.de?ref=dm_aff_amz_de clas…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1715,
Column 184:
end tag for element "A" which is not open
…reame Millionen<br>von Songs</span></a></td><td class="navFooterDescSpacer" st…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 1716,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://www.abebooks.de class="nav_a">AbeBooks…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1716,
Column 164:
end tag for element "A" which is not open
…er, Kunst<br>& Sammelobjekte</span></a></td><td class="navFooterDescSpacer" st…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 1717,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://aws.amazon.com/de/?sc_channel=el&sc_ca…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1717,
Column 80:
cannot generate system identifier for general entity "sc_campaign"
…ps://aws.amazon.com/de/?sc_channel=el&sc_campaign=deamazonfooter&sc_publisher=…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 1717,
Column 80:
general entity "sc_campaign" not defined and no default entity
…ps://aws.amazon.com/de/?sc_channel=el&sc_campaign=deamazonfooter&sc_publisher=…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 1717,
Column 91:
reference to entity "sc_campaign" for which no system identifier could be generated
…azon.com/de/?sc_channel=el&sc_campaign=deamazonfooter&sc_publisher=de_amazon&s…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 1717,
Column 79:
entity was defined here
…tps://aws.amazon.com/de/?sc_channel=el&sc_campaign=deamazonfooter&sc_publisher……channel=el&sc_campaign=deamazonfooter&sc_publisher=de_amazon&sc_medium=footer&…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 1717,
Column 107:
general entity "sc_publisher" not defined and no default entity
…channel=el&sc_campaign=deamazonfooter&sc_publisher=de_amazon&sc_medium=footer&…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 1717,
Column 119:
reference to entity "sc_publisher" for which no system identifier could be generated
…c_campaign=deamazonfooter&sc_publisher=de_amazon&sc_medium=footer&sc_content=&…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 1717,
Column 106:
entity was defined here
…_channel=el&sc_campaign=deamazonfooter&sc_publisher=de_amazon&sc_medium=footer……deamazonfooter&sc_publisher=de_amazon&sc_medium=footer&sc_content=&sc_category…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 1717,
Column 130:
general entity "sc_medium" not defined and no default entity
…deamazonfooter&sc_publisher=de_amazon&sc_medium=footer&sc_content=&sc_category…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 1717,
Column 139:
reference to entity "sc_medium" for which no system identifier could be generated
…ooter&sc_publisher=de_amazon&sc_medium=footer&sc_content=&sc_category=AWS_clou…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 1717,
Column 129:
entity was defined here
…=deamazonfooter&sc_publisher=de_amazon&sc_medium=footer&sc_content=&sc_categor……_publisher=de_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_comput…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 1717,
Column 147:
general entity "sc_content" not defined and no default entity
…_publisher=de_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_comput…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 1717,
Column 157:
reference to entity "sc_content" for which no system identifier could be generated
…=de_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_computing&TRK=EL…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 1717,
Column 146:
entity was defined here
…c_publisher=de_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_compu……e_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_computing&TRK=EL_d…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 1717,
Column 159:
general entity "sc_category" not defined and no default entity
…e_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_computing&TRK=EL_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 1717,
Column 170:
reference to entity "sc_category" for which no system identifier could be generated
…_medium=footer&sc_content=&sc_category=AWS_cloud_computing&TRK=EL_de_amazon_fo…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 1717,
Column 158:
entity was defined here
…de_amazon&sc_medium=footer&sc_content=&sc_category=AWS_cloud_computing&TRK=EL_……tent=&sc_category=AWS_cloud_computing&TRK=EL_de_amazon_footer class="nav_a">Am…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 1717,
Column 191:
general entity "TRK" not defined and no default entity
…tent=&sc_category=AWS_cloud_computing&TRK=EL_de_amazon_footer class="nav_a">Am…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 1717,
Column 194:
reference to entity "TRK" for which no system identifier could be generated
…t=&sc_category=AWS_cloud_computing&TRK=EL_de_amazon_footer class="nav_a">Amazo…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 1717,
Column 190:
entity was defined here
…ntent=&sc_category=AWS_cloud_computing&TRK=EL_de_amazon_footer class="nav_a">A……puting Dienste<br>von Amazon</span></a></td><td class="navFooterDescSpacer" st…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 1718,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://www.audible.de class="nav_a"><a href="…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1718,
Column 208:
end tag for element "A" which is not open
…Hörbücher<br>herunterladen</span></a></td><td class="navFooterDescSpacer" st…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 1719,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://www.imdb.com/ class="nav_a">IMDb<br><s…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1719,
Column 145:
end tag for element "A" which is not open
…Db<br><span class="navFooterDescText">Filme, TV<br>& Stars</span></a></td></tr>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 1722,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://kdp.amazon.com/de_DE/ class="nav_a">Ki…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1722,
Column 184:
end tag for element "A" which is not open
…n E-Book<br>veröffentlichen</span></a></td><td class="navFooterDescSpacer" st…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 1723,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://www.shopbop.com/de/welcome class="nav_…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1723,
Column 163:
end tag for element "A" which is not open
…Text">Designer<br>Modemarken</span></a></td><td class="navFooterDescSpacer" st…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 1724,
Column 39:
an attribute value must be a literal unless it contains only name characters
<td class="navFooterDescItem"><a href=/gp/browse.html?node=3581963031&ref_=foot…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1725,
Column 45:
NET-enabling start-tag requires SHORTTAG YES
…ass="navFooterDescItem"><a href=https://www.zvab.com/index.do?ref=amazon&utm_m…
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1725,
Column 90:
reference to entity "utm_medium" for which no system identifier could be generated
…vab.com/index.do?ref=amazon&utm_medium=referral&utm_source=amazon.de class="na…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 1547,
Column 70:
entity was defined here
…www.aboutamazon.de/?utm_source=gateway&utm_medium=footer" class="nav_a">Erfahr……dex.do?ref=amazon&utm_medium=referral&utm_source=amazon.de class="nav_a">ZVAB<…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 1725,
Column 100:
general entity "utm_source" not defined and no default entity
…dex.do?ref=amazon&utm_medium=referral&utm_source=amazon.de class="nav_a">ZVAB<…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 1725,
Column 110:
reference to entity "utm_source" for which no system identifier could be generated
…=amazon&utm_medium=referral&utm_source=amazon.de class="nav_a">ZVAB<br><span 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 1725,
Column 99:
entity was defined here
…ndex.do?ref=amazon&utm_medium=referral&utm_source=amazon.de class="nav_a">ZVAB……iquarischer Bücher und mehr</span></a></td><td class="navFooterDescSpacer" st…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 1726,
Column 39:
an attribute value must be a literal unless it contains only name characters
<td class="navFooterDescItem"><a href=/gp/browse.html?node=14154536031&ref_=nav…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1735,
Column 90:
reference to entity "ref_" for which no system identifier could be generated
…mer/display.html?nodeId=201909000&ref_=footer_cou" id="" class="nav_a">Unsere …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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……nodeId=201909000&ref_=footer_cou" id="" class="nav_a">Unsere AGB</a> </li><li …
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 1735,
Column 209:
reference to entity "ref_" for which no system identifier could be generated
…mer/display.html?nodeId=201909010&ref_=footer_privacy" id="" class="nav_a">Dat…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……Id=201909010&ref_=footer_privacy" id="" class="nav_a">Datenschutzerklärung</a…
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 1735,
Column 343:
reference to entity "ref_" for which no system identifier could be generated
…mer/display.html?nodeId=202024860&ref_=footer_impressum" id="" class="nav_a">I…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……=202024860&ref_=footer_impressum" id="" class="nav_a">Impressum</a> </li><li >…
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 1735,
Column 467:
reference to entity "ref_" for which no system identifier could be generated
…mer/display.html?nodeId=201890250&ref_=footer_cookies_notice" id="" class="nav…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……90250&ref_=footer_cookies_notice" id="" class="nav_a">Hinweise zu Cookies</a> …
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 1735,
Column 622:
reference to entity "ref_" for which no system identifier could be generated
…mer/display.html?nodeId=201909150&ref_=footer_Interest_Based_Ads_Notice" id=""…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 314,
Column 1213:
entity was defined here
…customer/display.html?nodeId=201909010&ref_=footer_privacy">Datenschutzerklär……footer_Interest_Based_Ads_Notice" id="" class="nav_a">Hinweise zu interessenba…
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 1740,
Column 131:
required attribute "TYPE" not specified
…000px; top: -1000000px;"></div><script>(function(a,b){a.attachEvent?a.attachEv…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 1740,
Column 671:
end tag for element "IFRAME" which is not open
…inheight="0" scrolling="no" tabindex="-1" sandbox></iframe>')},300)});</script>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 1746,
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 1754,
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 1761,
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 1766,
Column 140:
NET-enabling start-tag requires SHORTTAG YES
…ackdetect' action="get"><input type="hidden" name='ue_back' value='1' /></form>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1964,
Column 236:
NET-enabling start-tag requires SHORTTAG YES
…XSR6$uedata=s:%2Frd%2Fuedata%3Fnoscript%26id%3D5G9NCES2BMM0GMZ2XSR6:0' alt=""/>
For the current document, the validator interprets strings like
<FOO /> according to legacy rules that
break the expectations of most authors and thus cause confusing warnings
and error messages from the validator. This interpretation is triggered
by HTML 4 documents or other SGML-based HTML documents. To avoid the
messages, simply remove the "/" character in such contexts. NB: If you
expect <FOO /> to be interpreted as an
XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted
attribute value containing one or more "/". Example:
<a href=http://w3c.org>W3C</a>.
In such cases, the solution is to put quotation marks around the value.
Line 1967,
Column 8:
required attribute "TYPE" not specified
<script>window.ue && ue.count && ue.count('CSMLibrarySize', 82152)</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 1969,
Column 6:
end tag for element "DIV" which is not open
</div></body></html>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.
