(X)HTML problems
These problems are due to non-conformance with the chosen (X)HTML specification:
| E600 | This element is not recognised | This error is often raised when a browser-specific tag has been used such as <embed>. Alternatively you may have misspelled the name or tried to use a tag that is not valid with the HTML specification you are validating against. |
| E601 | This tag should not be nested within any other tags | This error is normally due to other errors within the page, such as using a frame set with the wrong <!DOCTYPE> tag. You can find a list of the <!DOCTYPE> " recognises here. |
| E602 | This should be the first HTML tag or content in the file | The <!DOCTYPE> tag should appear before all other HTML tags or non-whitespace content (with XHTML it may appear after the XML declaration). |
| E603 | An end tag is not allowed for this element | This error occurs when you use an end tag where no end tag is allowed according to the HTML specification being validated against. Correcting this error is normally a matter of deleting the end tag indicated. |
| E604 | The matching end tag appears to be missing | According to the HTML specification being validated against, the tag must have an end tag. Sometimes this error is caused by improperly nested tags where the end tag exists but cannot be matched with the corresponding start tag. |
| E606 | This tag or content must be nested within another tag | The tag or content appears at the top level, but it must be nested inside another tag. This error is typically caused by missing or misplaced <html>, <head> and <body> start and end tags. Although these three tags are actually optional in HTML, it is poor practice to miss them off and often causes problems for search engine robots. |
| E607 | This tag or content must be nested within another tag | The tag or content appears at the top level, but it must be nested inside another tag. This error is typically caused by missing or misplaced <html>, <head> and <body> start and end tags. Although these three tags are actually optional in HTML, it is poor practice to miss them off and often causes problems for search engine robots. |
| E608 | There must be a <!DOCTYPE> tag at the top of the page (if 'auto-detecting' then a best-fit <!DOCTYPE> will be used) | A <!DOCTYPE> tag should be placed before any other HTML tag or non-whitespace characters on the page. Sometimes the <!DOCTYPE> tag is in the wrong place, but is usually missing altogether in these cases. A correct <!DOCTYPE> tag is needed to ensure that the browser interprets the HTML correctly. You can find a list of the <!DOCTYPE> " recognises here. |
| E609 | This tag or content is not allowed here. One of the following was expected: LIST OF VALID TAGS | If this error is preceded by an E604 error (missing end tag) then correcting the earlier E604 error may correct this one. Otherwise note that there are strict rules as to what tags may be nested within others, as well as the order and number of tags allowed. Try removing the item marked with this error or nesting it within one of the tags listed. Note that in rare cases it is possible that a tag in the list provided also may not be allowed, but a simple test should quickly resolve this. |
| E610 | One or more of the following tags are missing from within the enclosing tag: LIST OF MISSING TAGS | The HTML specification being tested against defines that the tag identified must have one or more specific tags nested within it. You should add one or more of the missing tag(s) as appropriate. |
| E611 | Only one of this type of tag should be used within the enclosing tag | This error occurs when the specification only allows one of a certain tag to be nested within the enclosing tag, and more than one tag was found. |
| E612 | This tag or content is not allowed here | Each tag is defined by the HTML specification as only being allowed to contain certain other items nested within it, and sometimes these nested items may only appear once or only in a certain order. A common problem is to use a tag where it may not be obvious that it is not allowed, and may be accepted by many browsers. Try removing the offending item or nesting it within one of the other tags listed. |
| E614 | The <!DOCTYPE> tag does not match the HTML specification being checked against | The <!DOCTYPE> tag should exactly match the one that uniquely identifies the specification being tested. You can find a list of the <!DOCTYPE> " recognises here. |
| E620 | The 'ATTRIBUTE NAME' attribute is not valid for this tag | The most common reason for this error is the use of a browser-specific attribute (such as 'leftmargin' in the <body> tag), which is not part of the official HTML specification being tested against. If the attribute is for purely for layout then consider using CSS instead. |
| E621 | The 'ATTRIBUTE NAME' attribute for this tag is missing | The HTML specification being validated against requires that the attribute indicated always be used. |
| E622 | The 'ATTRIBUTE NAME' attribute does not have a valid value: LIST OF VALID VALUES | The HTML specification being validated against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Note also that what values are allowed varies from standard to standard. |
| E623 | The values of all attributes must be enclosed by quotes | In XHTML all attribute values must be enclosed by quotes. See http://www.w3.org/TR/xhtml1/#h-4.4 (displayed in new window). This error is sometimes caused by a misformatted tag possibly with single or double quotes in the wrong place or mismatched. Check that there are no extra or missing quote characters. |
| E624 | The 'content' attribute should have a value of 'application/xhtml+xml' for XHTML | Note that <meta> tags override HTTP headers and XHTML should be served with a content type of 'application/xhtml+xml', but the content type used was not recognised. See http://www.w3.org/TR/xhtml-media-types/#summary (displayed in new window). |
| E625 | The 'content' attribute should have a value of 'text/html' for HTML | Note that <meta> tags override HTTP headers and HTML should be served with a content type of 'text/html'. See http://www.w3.org/TR/xhtml-media-types/#summary (displayed in new window). |
| E626 | All element names must be in lower case | XML is case-sensitive and in XHTML all element names are defined as being in lower case. See http://www.w3.org/TR/xhtml1/#h-4.2 (displayed in new window). |
| E628 | Singleton tags are not allowed in HTML | With HTML you are not allowed to end a tag with the '/' character. This is only valid with XHTML documents. |
| E629 | No matching anchor name | A link was found to an anchor in the same page, but that anchor could could not be found. You need to either remove the link or add a matching anchor name. |
| E630 | The name and id attributes must have the same value | When id and name attributes appear in the same element they must have the same value. See http://www.w3.org/TR/html401/struct/links.html#h-12.2.3 (displayed in new window). |
| E631 | Anchor name and id attributes must be unique in the same document | All id and anchor name attributes in the same document must have unique values. See http://www.w3.org/TR/html401/struct/links.html#h-12.2.3 (displayed in new window). |
| E632 | No matching anchor name | A link was found in a redirect that points to an anchor in the same page, but that anchor could could not be found. You need to amend the redirect or add a matching anchor name. |
| E633 | The 'content-type' http header should have a value of 'application/xhtml+xml' for XHTML | XHTML should be served with a content type of 'application/xhtml+xml', but the content type used was not recognised. See http://www.w3.org/TR/xhtml-media-types/#summary (displayed in new window). |
| E634 | The 'content-type' http header should have a value of 'text/html' for HTML | HTML should be served with a content type of 'text/html'. See http://www.w3.org/TR/xhtml-media-types/#summary (displayed in new window). |
| E635 | The XML declaration must appear before any other content or tags | The XML declaration (if supplied) must be the first thing in the file, before any other content or tags. |
| E636 | Only one XML declaration is allowed | Only one XML declaration may be supplied and this must be the first thing in the file, before any other content or tags. |
| E637 | The XML declaration must contain a 'version' attribute | The XML declaration must contain a 'version' attribute. Check the spelling of any attributes supplied. |
| E638 | Invalid value for the 'version' attribute | The 'version' attribute must be set to the string '1.0'. |
| E639 | Invalid value for the 'encoding' attribute | The 'encoding' attribute must begin with a letter [a-zA-Z] and may be followed by any number of letters, digits [0-9], hyphens, underscores, and periods. |
| E640 | Invalid value for the 'standalone' attribute | The 'standalone' attribute must be set to either 'yes' or 'no'. |
| E641 | Unknown or invalid attribute | The XML declaration contains an unrecognised or invalid attribute. Check for spelling mistakes. |
| E642 | The root element name 'html' is missing from the <!DOCTYPE> tag | The root element name 'html' is either missing from the <!DOCTYPE> tag, misspelt, or the wrong root element name has been used. You can find a list of the <!DOCTYPE> tags that Total Validator recognises here. |
| E643 | The keyword 'PUBLIC' is missing from the <!DOCTYPE> tag | The keyword 'PUBLIC' is either missing from the <!DOCTYPE> tag, or misspelt. You can find a list of the <!DOCTYPE> tags that Total Validator recognises here. |
| E644 | The word '!DOCTYPE' must be in uppercase for XHTML documents | The name '!DOCTYPE' must be all in uppercase for XHTML documents. You can find a list of the <!DOCTYPE> tags that Total Validator recognises here. |
| E645 | The keyword 'PUBLIC' must be in uppercase for XHTML documents | The keyword 'PUBLIC' must be all in uppercase for XHTML documents. You can find a list of the <!DOCTYPE> tags that Total Validator recognises here. |
| E646 | The root element name 'html' must be in lowercase for XHTML documents | The root element name 'html' must be all in in lowercase for XHTML documents. You can find a list of the <!DOCTYPE> tags that Total Validator recognises here. |
| E647 | The character set is not recognised | The character set specified is not recognised. This may be because it is misspelled. |
| E648 | The value of the 'for' attribute must match the 'id' of the control element it refers to | When you include a 'for' attribute to associate a label with a control you must provide a control with a matching 'id' value in the same document. See http://www.w3.org/TR/html401/interact/forms.html#h-17.9.1 (displayed in new window). |
| E649 | The default scripting language must be specified for an intrinsic event | When intrinsic events (onclick, onmouseover etc) are specified the default scripting language should be specified using a Content-Script-Type HTTP header or <meta> tag. See http://www.w3.org/TR/html401/interact/scripts.html#h-18.2.2.1 (displayed in new window). |
| E650 | The default style sheet language must be specified when style attributes are used | When style attributes are used the default style sheet language should be specified using a Content-Style-Type HTTP header or <meta> tag. See http://www.w3.org/TR/html401/present/styles.html#h-14.2.1 (displayed in new window). |
| W600 | The 'ATTRIBUTE NAME' attribute has a boolean value, and this may be ignored or cause errors in older browsers/robots | Some older browsers and search engine robots do not recognise XHTML style boolean attributes such as selected="selected". For backwards compatibility just use the attribute without any value, e.g. 'selected' |
| W601 | The 'ATTRIBUTE NAME' attribute for this tag is recommended, but missing | Although this attribute is not required it is recommended that you add it for clarity. |
| W602 | The <!DOCTYPE> tag does not match the HTML specification being checked against | The <!DOCTYPE> tag should exactly match the one that uniquely identifies the specification being tested. You can find a list of the <!DOCTYPE> " recognises here. |
| W603 | The system ID is missing from the <!DOCTYPE> tag | Although not a serious problem, the <!DOCTYPE> tag should exactly match the one that uniquely identifies the specification that the page follows. In this case the system ID is missing and should be added for completeness. This is a URL pointing to the DTD used to validate the page. You can find a list of the <!DOCTYPE> " recognises here. |
| W607 | The 'content' attribute should have a value of 'application/xhtml+xml' for XHTML 1.1 | Note that <meta> tags override HTTP headers and XHTML 1.1 should be served with a content type of 'application/xhtml+xml'. See http://www.w3.org/TR/xhtml-media-types/#summary (displayed in new window). |
| W608 | The 'content-type' http header should have a value of 'application/xhtml+xml' for XHTML 1.1 | XHTML 1.1 should be served with a content type of 'application/xhtml+xml'. See http://www.w3.org/TR/xhtml-media-types/#summary (displayed in new window). |
| W609 | The 'content-type' HTTP header specifies a different character set | The 'content-type' HTTP header specifies a different character set to that specified in the tag. In this case the HTTP header takes precedence. |
| W610 | The BOM specifies a different character set | The BOM (Byte Order Mark) of the document specifies a different character set to that specified in the tag. In this case the BOM takes precedence. |
| W611 | No character set is specified in either the HTTP header, <meta> tag, or XML declaration | The character set (character encoding) should be specified in either a HTTP header or <meta> tag, or XML declaration for XHTML documents. If it isn't then the user agent may select an incorrect character set by mistake. See http://www.w3.org/TR/html401/charset.html#h-5.2.2 (displayed in new window). |
top