<$0>
+ is not allowed after the end tag </body>.The start or end tag of an element appears after the
+ body element has been closed. The document is
+ non-conforming.
Any content of the document other than head
+ contents and comments must be put into the body
+ element.
& character must
@@ -63,18 +78,41 @@
</ string is not followed
+ by a tag name.There is a < (U+003C
+ LESS-THAN SIGN) character
+ immediately followed by a / (U+005F
+ SOLIDUS) character, which is not part
+ of any end tag, in the input stream. The document
+ is non-conforming.
The </ sequence immediately followed
+ by an EOF is
+ interpreted as a string data of </.
The </ sequence as string data must
+ be escaped as:
+
</< character is not followed
by tag name or by a ! character.A < (U+003C LESS-THAN
- SIGN) character which is not part of any markup appears
- in the input stream.
A < (U+003C
+ LESS-THAN SIGN) character which is not part
+ of any markup appears in the input stream.
The < character as a data character must
be escaped as:
-
<lt;<The string &# must be the first two characters
- NUMBER SIGN) character must be the first two characters
of a reference:
To represent &# as data characters, use
- named entity reference:
+ a named entity reference for the & character:
&#To represent &#x as data characters, use
- named entity reference:
+ a named entity reference for the & character:
&#x</ string is not followed
+ by a tag name.There is a < (U+003C
+ LESS-THAN SIGN) character
+ immediately followed by a / (U+005F
+ SOLIDUS) character, which is not part
+ of any end tag, in the input stream. The document
+ is non-conforming.
The </ sequence not followed by a
+ tag name is parsed as an opening of bogus comment.
The </ sequence as string data must
+ be escaped as:
+
</-- sequence
@@ -154,7 +213,8 @@
$0.There are more than one attributes with the same name in a tag. The document is non-conforming.
@@ -183,6 +243,36 @@<?...?>) cannot be used.Processing instructions (<?...?>),
+ including XML declaration (<?xml ...?>)
+ and XML style sheet PI
+ (<xml-stylesheet ...?>), are not allowed
+ in the HTML syntax. The document is non-conforming.
If it is necessary to embed a processing instruction + in the HTML document, you must use the XML syntax instead.
+ +In the HTML syntax, XML declaration is not necessary.
+ +Instead of XML style sheet,
+ PIs, you must
+ use the HTML link element whose rel
+ attribute is set to stylesheet (or
+ alternate stylesheet for an aleternate style sheet).
Web browsers will parse processing instructions as bogus + comments. Some legacy Web browsers, such as IE:mac and + some mobile browsers, will display processing instructions + as string.
+HTML a elements cannot be nested.
+ The document is non-conforming.
In the HTML syntax, a start tag of the a
+ implies the end tag of any opening a element.
<$0>
- is not allowed in body.body element.
The start or end tag of an element, which
cannot be a descendant of body element, appears
@@ -225,10 +327,24 @@
<head>
+ is not allowed in the head element.There is a start tag <head> in the
+ <head> element. The document is non-conforming.
In an HTML document there must not be more than
+ one head element, therefore no more than one
+ start tag <head> can appear in the input stream.
<$0>
- is not allowed in table.table element.
The start or end tag of an element, which
cannot be a child of The document does not start with a There is a start tag of the In an HTML document, there cannot be more than one
+ The document contains a table element, appears
@@ -277,7 +393,7 @@
DOCTYPE.DOCTYPE.
@@ -303,14 +419,32 @@
<html> tag is not
+ the first start tag.html element
+ that it not the first start tag in the input stream.
+ The document is non-conforming.html element and therefore there cannot be
+ more than one <html> tag. In addition,
+ nothing can be placed before the <html> tag
+ except a DOCTYPE, white space characters,
+ and comments.DOCTYPE declaration
- that is different from HTML5 DOCTYPE (i.e. <!DOCTYPE
- HTML>). The document is non-conforming.DOCTYPE (i.e.
+ <!DOCTYPE HTML>). The document is non-conforming.
The document might or might not be conformant to some version of HTML. However, conformance to any HTML @@ -347,24 +481,20 @@ context. The document is non-conforming.
Possible causes: -
a or span)A data character cannot be a child
- of certain sectioning elements such as body,
- section, and blockquote.
Any inline-level content must be put
- in e.g. paragraph element such as p.
div or hn)Though some elements such as div,
- li, and td allow
- either one of block-level or inline-level content
- is allowed. If there is a block-level content,
- any inline-level content must be put
- in e.g. paragraph element such as p.
A data character cannot be a child
+ of certain sectioning elements such as body,
+ section, and blockquote.
Any inline-level content must be put
+ in e.g. paragraph element such as p.
Though some elements such as div,
+ li, and td allow
+ either one of block-level or inline-level content
+ is allowed. If there is a block-level content,
+ any inline-level content must be put
+ in e.g. paragraph element such as p.
Possible causes: -
a or span)a, progress, or imgAn inline-level element cannot be a child
of certain sectioning elements such as body,
section, and blockquote.
Any inline-level content must be put
in e.g. paragraph element such as p.
div or hn)div, hn, or
+ sectionThough some elements such as div,
li, and td allow
either one of block-level or inline-level content
is allowed. If there is a block-level content,
any inline-level content must be put
in e.g. paragraph element such as p.
html elementnoscript elementnoscript element is allowed only in the context
+ where a block-level or inline-level content is expected
+ and in the head element.
+ It cannot be used in e.g. ul, table,
+ or select.html element
+ that is the root element of an XHTML documentIn an XHTML document, the root html
element must have an xmlns attribute
whose value is set to
http://www.w3.org/1999/xhtml.
blink,
+ center, or marquee element$0
+ element before this element.There must be an element before another element, but there + is not. The document is non-conforming.
+ +For example, there must be a dt element
+ before any dd element.
{local-name} is not allowed for
+ {element-local-name} element.An attribute is specified where it is not allowed. + The document is non-conforming.
+ +meta elementmeta element, only one of
+ name, http-equiv, or charset
+ attribute is allowed.xml:lang attribute is not
allowed in HTML document.The xml:lang attribute is not allowed in
HTML document. The document is non-conforming.
To specify natural language information in HTML document,
use lang attribute instead.
XHTML 1.0 Appendix C was encouraged to specify both
+ lang and xml:lang attributes with
+ the same value. Such a duplication has no effect in practice.
+ Use only one of lang (in HTML) or xml:lang (in
+ XML).
The xmlns attribute in the null
namespace is not allowed in XHTML document.
This error should not occur in conformance-checking +
This error should not occur in conformance-checking of static documents.
{@} is not one
+ of them.
+ For this attribute only several values are allowed and the + value of the attribute is not one of them. The document + is non-conforming.
+ +meta element, http-equiv attributeOnly Default-Style and Refresh
+ is allowed.
Value Content-Type is obsolete; for charset
+ declaration, the charset attribute can be used as:
+
<meta charset="charset-name">utf-8.
+ Values Content-Style-Type and
+ Content-Script-Type are currently not allowed.
Value Keywords is not allowed. Use
+ name attribute instead of http-equiv
+ attribute.
Values Expires, Pragma,
+ and Cache-Control are not allowed;
+ use real HTTP header fields for cache control.
$0
cannot be specified for this element.$0
is non-conforming.The specified link type is non-conforming. The entire document - is non-conforming.
+The specified link type is non-conforming, and therefore + the document is non-conforming.
-For example, in place of non-conforming link type copyright
- you must use link type license.
contentsindex.copyrightlicense.homeindex.startfirst.tocindex.{@} is reserved.The specified browsing context name is reserved. The document is non-conforming.
@@ -592,7 +807,7 @@ browsing context names_blank,
_main, and _replace.
However, they are not conforming attribute values.
- th) in the last row.
+rowspan attribute
+ results in creating a table row that does not contain
+ any cell anchored to it.The rowspan attribute value of the cell
+ is so specified that it extends a table in the row axis.
+ However, the extended row does not contain any cell by itself.
+ The document is non-conforming.
For example, the table below is non-conforming: +
<table>
+<tbody>
+<tr><td rowspan=2></td></tr>
+</tbody>
+</table>{@}: An obsolete
+ subtype is used.x- or x.)
- subtype is used.{@}: A private
+ (x- or x.) subtype is used.{@}: The subtype is
+ not registered to IANA.The specified value does not satisfy the syntactical requirements + for IRI references. The document is non-conforming.
+ +Possible causes: +
(U+0020
+ SPACE) character cannot be
+ used in IRI references.The scheme part of the IRI is written in uppercase letter.
+ +Uppercase scheme names are not required to be processed + correctly.
+ +shortcut iconshortcut is not registered.
+ Use only icon for linking to so-called favicon.