<$0>
- is not allowed after the end tag </html>.The start or end tag of an element appears after the
- html element has been closed. The document is
- non-conforming.
Any content of the document other than comments
- must be put into the html element.
WebHACC + is a conformance checker (or validator) for Web documents, + supporting latest Web standards including + HTML5, + Atom 1.0, + CSS3.
+ +& character must
- introduce a reference.An The input stream is encoded in Note that an The character encoding used for the document is not allowed
+ for HTML document. The document is non‐conforming. The character encoding used for the document is not recommended
+ for HTML document. The document is non‐conforming
+ unless there is any good reason to use that encoding. Use of UTF-8 as the character encoding of the document is encouraged,
+ though the use of another character encoding is still conforming. The conformance checker cannot detect whether the input document
+ met the requirements on character encoding, since the document
+ is not inputed as a serialized byte sequence. The document is
+ not conforming if it is not encoded in an appropriate character
+ encoding with appropriate labeling. The document does not contain a character encoding
+ declaration. Unless the character encoding is explicitly
+ specified in lower‐level protocol, e.g. in HTTP,
+ or is implied by BOM, there must be a character
+ encoding declaration. The document is non‐conforming. The long character encoding declaration syntax
+ Note that the The document is not labeled with character encoding name
+ in lower‐level protocol, e.g. in HTTP, and
+ the document is not begin with BOM. In addition,
+ the character encoding of the document is not a superset of
+ ASCII. The document is non‐conforming. Unless there is a BOM, the character encoding
+ for the document must be specified in e.g. HTTP‐level,
+ as: Existence of HTML character encoding declaration, i.e.
+ Character encodings The conformance checker cannot find an appropriate decoder for
+ the character encoding used to encode characters in the document. This error is raised if: In either case, the result shown by the conformance checker might
+ contain wrong errors caused by errorneous decoder or might not contain
+ errors that should be raised if an appropriate decoder is used. While parsing a document in a character encoding,
+ a character encoding declaration which declares the character
+ encoding of the document as another character encoding is found.
+ The occurence of this warning itself does not make the document
+ non‐conforming. However, the failure of the first attempt to
+ to detect the character encoding might be a result of non‐conformance
+ of the document. The document will be reparsed from the beginning. Some error
+ or warning might be reported again. These are suggestions to avoid this warning: Noncharacter code points are used in the input stream. Noncharacter code points are reserved for internal processings.
+ Their use for information interchanges are forbidden. In addition, they are not allowed in HTML document. In an unquoted attribute value, a character This error is also raised if one try to use empty attribute
+ value like An Any The There is a The The A A The An The string To represent The string To represent There is a There is a The The There is a There are more than one attributes with the same
name in a tag. The document is non-conforming. The attribute value is not specified after the When an attribute value is empty, the Instead, quotation marks can be used to explicitly represent that
+ the attribute value is empty, as: ... or like: Void element syntax ( Polytheistic slash ( The void element syntax can only be
+ The polytheistic slash can only be
used for Note that, unlike in XML, the void element syntax has
+ The polytheistic slash cannot be used for NOTE: Though some user agents interpret
+ polytheistic slash for Note that, unlike in XML, the polytheistic slash has
no effect in HTML. Processing instructions ( 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 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
+ some mobile Web browsers, will display processing instructions
as string. A start tag appears after the A The The start tag of an element appears after the
+ Any content of the document other than The end tag of an element appears after the
+ Any content of the document other than HTML The start or end tag of an element, which
cannot be a descendant of There is a start tag In an HTML document there must not be more than
+ one A The The start or end tag of an element, which
cannot be a child of A data character appears in A non‐white‐space character appears in In Start tag of a The document does not start with a Only white space characters and comments are allowed
- before the End tag of an element is not found before, for example,
an end tag of another element appears or
the end of the document. The document is non-conforming. Only Note that misnesting tags, such as
+ There is a start tag of the In an HTML document, there cannot be more than one
+ The document contains a The document might or might not be conformant to
some version of HTML. However, conformance to any HTML
@@ -294,13 +907,45 @@
HTML document (roughly) as defined in HTML5. An end tag appears though no element with the same name
has been opened. The document is non-conforming. For any end tag in HTML document, there must be a
corresponding start tag. The The A data character appears where it is not allowed in this
context. The document is non-conforming. Possible causes:
- A data character cannot be a child
- of certain sectioning elements such as Any inline-level content must be put
- in e.g. paragraph element such as Though some elements such as A data character cannot be a child
+ of certain sectioning elements such as Any inline-level content must be put
+ in e.g. paragraph element such as Though some elements such as The content model of the element is so defined that it
must contain a For example:
- The An element appears where it is not allowed. The document
is non-conforming. Note: The conformance checker does
- not support form elements yet. Possible causes:
- An inline-level element cannot be a child
of certain sectioning elements such as Any inline-level content must be put
in e.g. paragraph element such as Though some elements such as In an XHTML document, the root The parent element allows either
+ block-level or inline-level content. If there is a
+ block-level content, any inline-level content must be
+ put in e.g. paragraph element such as For example, an HTML document fragment
+ The character encoding declaration
+ ( The character encoding declaration have to occur near the beginning
+ of the document to ensure that Web browsers can be determine the
+ character encoding of the document. The An element that is not allowed as the root element
+ is used as the root element of the document. The document is
+ non-conforming, as far as the conformance checker can tell. In XHTML document, the root The document is written in some version of RSS. The conformance checker does not support any version
+ of RSS. Use Atom 1.0 for feed documents. The Atom The conformance checker does not support Atom 0.3.
+ Use Atom 1.0 for feed documents. The element is not one of elements allowed
+ in the latest version of relevant specifications. The element cannot be used. There must be an element before another element, but there
+ is not. The document is non-conforming. For example, there must be a A required attribute is not specified. The document
is non-conforming. Some attribute is defined as required.
- For example, any An attribute is specified where it is not allowed.
+ The document is non-conforming. The The The attribute is not one of attributes allowed for the element
+ in the latest version of relevant specifications. The attribute cannot be used. The The To specify natural language information in HTML document,
use XHTML 1.0 Appendix C was encouraged to specify both
+ The To specify the character encoding used for serialization,
if necessary, use XML declaration instead:
The HTML The To specify natural language information in XML document,
- use The This error should not occur in conformance-checking
+ This error should not occur in conformance-checking of
static documents. The specified character encoding name is not registered to
+ IANA. Use of registered character encoding name
+ is a good practice to facilitate interoperability. WARNING: This error might be raised for
+ a registered character encoding name, since the character encoding
+ name database of the conformance checker is not complete yet. The specified character encoding name is a private name and
+ not registered to IANA. Use of registered character
+ encoding name is a good practice to facilitate interoperability. The attribute value must be a character encoding name. However,
+ the specified value is not a character encoding name syntactically.
+ The document is non‐conforming. Character encoding name is a string of ASCII
+ printable characters, up to 40 characters. For this attribute only several values are allowed and the
+ value of the attribute is not one of them. The document
+ is non-conforming. Only values Value Values Value Values Old long character encoding declaration syntax
+ The new character encoding declaration syntax is:
+ The A The specified link type cannot be used for the element.
The document 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 The specified character encoding name is different from
+ the character encoding of the document. The document
+ is non‐conforming. The specified browsing context name is reserved.
+ The document is non-conforming. Names of browsing contexts starting with Old version of HTML, non-HTML markup languages, and
+ Web browsers define or implements special reserved
+ browsing context names The link type is in the proposed status; it
@@ -512,49 +1719,225 @@
Warning: The data served to the
conforming checker might be out of date; it might have already
- been accepted or rejected, depending on which the document
- might be conforming or non-conforming. See WHATWG Wiki
+ been accepted or rejected. The document might or might not be
+ conforming depending on the status. See WHATWG Wiki
for the latest information. The value of the For historical reason, there are two attributes applicable to HTML
+ elements to specify language information of an element: In general, only the If both The For example, the table below is non-conforming:
+ The specified Internet Media Type is registered with its intended
+ usage as OBSOLETE. The specified value does not satisfy the syntactical requirements
+ for IRI references. The document is non-conforming. Possible causes:
+ Dot-segment ( The hexadecimal digit in percent-encoding string in the IRI
is in lowercase. Though the IRI is conforming,
it should be in uppercase. An unreserved character is percent-encoded in the IRI.
Though it is conforming, it should be in the
decoded (or bare) form. The scheme part of the IRI is written in uppercase letter. Uppercase scheme names are not required to be processed
+ correctly. The specified document is not a cache manifest.
+ The document is non-conforming. An entity labeled as Internet media type
+ A cache manifest must start with a line whose content is
+ The element is in the call for implementation stage. Usually, using the element is safe. However, it is a new feature
+ so that it might not be implemented correctly. If it is found that
+ the feature is hard or impossible to implement, the feature
+ might be revised, or in some case it might be dropped. Elements defined by Atom 1.0 (IETF Proposed Standard), and XBL 2.0
+ (W3C Candidate Recommendation) belong to this class. The element is in the last call for comments stage. The element is relatively mature, though the standardization
+ is not done yet. It may be used for experiments. Since it is a new
+ feature, it might not be implemented correctly or at all. If it is
+ found that the feature is hard or impossible to implement, the feature
+ might be revised or might be dropped. Elements defined by Web Forms 2.0 as well as some elements
+ defined by HTML5 belong to this class. The element is documented in a working or editor's draft
+ and not yet completed. The element should not be used for any practical purpose.
+ The feature might be drastically changed later or might be
+ entirely removed. Most of new elements defined by HTML5 belong to this class. The element is not part of any standard or draft the conformance
+ checker is aware of. The element should not be used for any practical purpose unless
+ there is really a standard that defines the element. The attribute is in the call for implementation stage. Usually, using the attribute is safe. However, it is a new feature
+ so that it might not be implemented correctly. If it is found that
+ the feature is hard or impossible to implement, the feature
+ might be revised, or in some case it might be dropped. The attribute is in the last call for comments stage. The attribute is relatively mature, though the standardization
+ is not done yet. It may be used for experiments. Since it is a new
+ feature, it might not be implemented correctly or at all. If it is
+ found that the feature is hard or impossible to implement, the feature
+ might be revised or might be dropped. The attribute is documented in a working or editor's draft
+ and not yet completed. The attribute should not be used for any practical purpose.
+ The feature might be drastically changed later or might be
+ entirely removed. The attribute is not part of any standard or draft the conformance
+ checker is aware of. The attribute should not be used for any practical purpose unless
+ there is really a standard that defines the attribute. The conformant checker does not support the attribute.
+ The conformant checker does not support the element.
It cannot determine whether the document is conforming or not. The conformant checker does not support the element.
+ The conformant checker does not support the attribute.
It cannot determine whether the document is conforming or not. The No more information is available for this topic. A violation to a hard requirement of the specification.
+ The document is non‐conforming. A violation to a requirement of the specification.
+ The violation might be legitimize in some case. Otherwise,
+ the document is non‐conforming. A warning is an advice from the conformance checker
+ to avoid solving a problem in a confusing or possibly wrong way.
+ It does not affect to the conformance of the document, and
+ may sometimes be inappropriate. An informational message just provides an additional information
+ on the feature used in the document or the status of the retrieval
+ or so on.
+ It does not affect to the conformance of the document. Some feature that is not supported by the conformance checker
+ is used in the document. Copyright 2007 Wakaba This library is free software; you can redistribute it
+ Copyright ‐
+Wakaba
+ This document is free software; you can redistribute it
and/or modify it under the same terms as Perl itself.& (U+0026
- AMPERSAND) character which
+Character Encoding Layer Errors
+
+
+
+Octet sequence
{octets}
+ is not an allowed representation of the character
+ {char} — character reference
+ {char:hexref} should be used instead.
+
+No character is assigned to octet sequence
+
{octets}.
+
+Octet sequence
{octets}
+ is illegal.
+
+The input stream is broken.
+ ISO-2022-JP
+ or its variant but is partially broken.ISO-2022-JP stream must end in the ASCII
+ state.
+No character is assigned to octet sequence
+
{octets}.HTML5 Character Encoding Errors
+
+
+
+Character encoding
+ {text}
+ is not allowed for HTML document.
+
+Character encoding
+ {text}
+ should not be used for HTML document.
+
+Use of UTF-8 is encouraged (this document
+ is encoded in
+ {text}).
+
+Conformance for character encoding requirements
+ cannot be checked, since the input is not a byte stream.
+
+
+There is no character encoding
+ declaration.
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is obsolete. The new syntax is:
+
+
+ <meta charset="charset-name">encoding declaration in XML
+ declaration has no effect for HTML document.
+
+No character encoding metadata is found
+ in lower‐level protocol nor is there BOM, while
+ character encoding
+ {text}
+ is not a superset of ASCII.
+
+
+ Content-Type: text/html; charset=charset-name<meta charset="charset-name">,
+ does not allow to omit charset parameter
+ for HTML document encoded in non‐ASCII
+ compatible encoding.Shift_JIS, Windows-31J,
+ and ISO-2022-JP are not a superset of
+ ASCII for the purpose of HTML conformance.
+
+Character encoding of this document is sniffed
+ as
{text} (Sniffed because no explicit specification
+ for the character encoding of this document is found in the transfer
+ procotol headers).
+
+Character encoding of this document is defaulted
+ to
{text} because no explicit specification
+ for the character encoding of this document is found in the transfer
+ procotol headers.
+
+Results might be wrong, since the
+ conformance checker cannot find an appropriate decoder for the character
+ encoding used for the document.
+
+
+
+
+
+Conformance error checking for the character
+ encoding
{text} is not supported.
+
+Sniffed character encoding
+
{text} is same as the character encoding specified
+ in the character encoding declaration. This is not an
+ error.
+While parsing the document as
+
+ {text}, a character encoding declaration specifying
+ a different character encoding is found. The document
+ is reparsed.
+
+ charset parameter in the Content-Type
+ field in the HTTP header, as:
+
+
Content-Type: text/html; charset="charset-name"<meta charset="charset-name">)
+ just after <head> start tag.UTF-8.Coded Character Set Layer Errors
+
+
+
+The
NULL character
+ is not allowed.
+
+Code point
{text} is
+ not allowed.
+
+Noncharacter
+ {text}
+ is found in the input stream.
+
+Use of character
{text}
+ is deprecated.
+
+Use of character
{text}
+ is discouraged.
+
+Code point
{text}
+ is not the preferred representation of that character.
+
+Character
{text}
+ should not be used in many cases.HTML5 Parse Errors in Tokenization Stage
+
+
+
+Attribute name cannot contain characters
+
", ', and =.
+
+Attribute value must be quoted by
+ "
+ or ' if it contains a ", ', or
+ = character."
+ (U+0022 QUOTATION MARK),
+ ' (U+0026
+ APOSTROPHE), or =
+ (U+003D EQUAL SIGN)
+ is contained. These characters are not allowed in unquoted attribute
+ values, since they are used to quote attribute values or to separate
+ attribute name and value.<foo bar= baz=>;
+ in this example, baz= is
+ treated as an invalid attribute value for the attribute
+ bar, not as another attribute.
-The
+ & character must
+ be escaped as &.& character which
is not part of any reference appears in the input stream.
- The document is non-conforming.& character in URI (or IRI)
+ must be escaped as &.& character must
be the first character of a reference:
-
+
@@ -56,20 +301,40 @@
&entity-name;A
< character is not followed
+
+
+A
+ </ string is not followed
+ by a tag name.< (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.</ sequence immediately followed
+ by an EOF is
+ interpreted as a string data of </.</ sequence as string data must
+ be escaped as:
+
+
+
+ </
-A
- < character is not followed
by tag name or by a ! character.< (U+003C LESS-THAN
- SIGN) character which is not part of any markup appears
- in the input stream.< (U+003C
+ LESS-THAN SIGN) character which is not part
+ of any markup appears in the input stream.< character as a data character must
be escaped as:
-
+<lt;<
The decimal representation of the code position
+
-The decimal representation of the code position
of a character must be specified after
&#.& (U+0026
AMPERSAND) character immediately
@@ -79,9 +344,8 @@
The document is non-conforming.&# must be the first two characters
- NUMBER SIGN) character must be the first two characters
of a reference:
-
+
@@ -96,13 +360,13 @@
&#d;&# as data characters, use
- named entity reference:
+ a named entity reference for the & character:
&#The hexadecimal representation of the code position
+
-The hexadecimal representation of the code position
of a character must be specified after
&#x.&#x or &#X which
is not part of any reference appears in the input stream.
@@ -116,13 +380,69 @@
of the code point of the character to be referenced.&#x as data characters, use
- named entity reference:
+ a named entity reference for the & character:
&#xThere is a
-- sequence
+
+
+String
+ <! is not followed
+ by --.< (U+003C
+ LESS-THAN SIGN) character
+ followed by a ! (U+0021
+ EXCLAMATION MARK) character,
+ which is not followed by a -- or
+ !DOCTYPE. The document is non-conforming.
+
+ <!-- (<!
+ immediately followed
+ by two -s) and must be terminated by
+ -->.
+ Strings <! not followed
+ by -- and <!- not followed by
+ - are not valid open delimiters for comments.CDATA sectionsDOCTYPE
+ and comment declarations, are not allowed in HTML document.<!<! must be escaped as
+ <!.
+
+String
+ </ is not followed
+ by tag name.< (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.</ sequence not followed by a
+ tag name is parsed as an opening of bogus comment.</ sequence as string data must
+ be escaped as:
+
+
+
+ </
+
+Character reference to
+
{text} is not allowed.
+
+Character reference to
+
U+000D (CARRIAGE RETURN)
+ is not allowed.
-There is a
-- sequence
in a comment.- (U+002D
HYPHEN-MINUS) character
@@ -135,7 +455,8 @@
declaration.There are two attributes with same name.
+
-There are two attributes with name
+
{text}.img element with animation GIF instead.
Void element syntax (
/>) cannot be
+
+
+Empty start tag (
<>) is not
+ allowed.
+
+Empty end tag (
</>) is not
+ allowed.
+
+End tag cannot have attributes.
+
+Attribute value is not specified.
+ =
+ (U+003C EQUAL SIGN)
+ character.= character after
+ the attribute name must be specified as:<foo bar><foo bar=""><foo bar=''>
+
+Character reference to
+
{text} is not allowed.
+Polytheistic slash (
- />) cannot be
used for this element./>) must not be used
+ />) must not be used
for the element. The document is non-conforming.base, link, meta,
hr, br, img,
embed, param, area,
col, and input elements.
+
+
+ <script/>script
+ element. Even for an empty script element,
+ there must be an explicit end tag
+ </script>.script element as the
+ closing of the element, such usage is not allowed under
+ the current standard.<basefont/>, <bgsound/>,
+ <frame/>, <keygen/>,
+ <spacer/>, <wbr/><command/>, <event-source/>,
+ <nest/>, or <source/><a/>, <p/>
+
+ <p></p>
+
+After the string
<!DOCTYPE , the
+ document type name must be specified.
+
+After the keyword
PUBLIC, no
+ oublic identifier is specified.
+
+Character reference must be closed by a
+
; character.
-After the string
<!DOCTYPE, there
+ must be at least a white space character before the document type
+ name.Processing instruction
- (
+<?...?>) cannot be used.
+
+Attributes must be separeted by at least a
+ white space character.
+
+After the keyword
SYSTEM, no
+ system identifier is specified.
+Processing instruction
+ (
<?...>) is not allowed in HTML
+ document.<?...?>),
including XML declaration (<?xml ...?>)
and XML style sheet PI
- (<xml-stylesheet ...?>), are not allowed
+ (<?xml-stylesheet ...?>), are not allowed
in the HTML syntax. The document is non-conforming.link element whose rel
- attribute is set to stylesheet (or alternate
- stylesheet for an aleternate style sheet).
+
<?xbl?> (XBL Association)binding property in CSS
+ style sheet as:
+
+
+ <style>
+p {
+ binding: url(binding.xbl);
+}
+</style><?xml?> (XML declaration)<?xml-stylesheet?> (XML style sheet
+ PI)link element with rel
+ attribute set to stylesheet (or,
+ alternate stylesheet for an alternate style
+ sheet).
+
+
+ <link rel=stylesheet href="path/to/stylesheet.css"><?php?> or
+ <? ... PHP code ... ?>
+ (PHP code)ProcessingInstruction node by scripting.
+
+There is a bogus string after the document type
+ name.
+
+There is a bogus string after the keyword
+
PUBLIC.
+
+There is a bogus string after the public
+ identifier.
+
+There is a bogus string after the keyword
+
SYSTEM.
+
+There is a bogus string after the system
+ identifier.
+
+Attribute value is not closed by a quotation
+ mark.
+
+Comment is not closed by a string
+
-->.
+
+The
DOCTYPE is not closed by a
+ > character.
+
+The public identifier literal is not closed by a
+ quotation mark.
+
+The system identifier literal is not closed by a
+ quotation mark.
+
Tag is not closed by a
>
+ character.HTML5 Parse Errors in Tree Construction Stage
-The
+$0 element cannot be
- inserted between head and body elements.
+
+There is a start tag
+
<{text}> is after the html element
+ is closed.
+
+There is an end tag
+
</{text}> is after the html element
+ is closed.
+
+Start tag
<{text}> is
+ not allowed after the body is closed.
+
+End tag
</{text}> is
+ not allowed after the body is closed.
+
+Non‐white‐space characters are not allowed
+ after the
body is closed.
+
+Start tag
<{text}> is
+ not allowed after the frameset is closed.
+
+End tag
</{text}> is
+ not allowed after the frameset is closed.
+
+Non‐white‐space characters are not allowed
+ after the
frame is closed.
-The
{text} element cannot be
+ inserted between head and body
+ elements.head element is closed
but before the body element is opened.
The document is non-conforming.A
- DOCTYPE appears after any
- element or data character has been seen.DOCTYPE appears after any element or data character
- has been seen. The document is non-conforming.DOCTYPE must be placed before any
- tag, reference, or data character. Only white space characters
- and comments can be inserted before the DOCTYPE.
+
+Start tag
+ <{text}> is
+ not allowed after the html is closed.body element has been closed. The document is
+ non-conforming.head
+ contents and comments must be put into the body
+ element.
-End tag
+ </{text}> is
+ not allowed after the html is closed.body element has been closed. The document is
+ non-conforming.head
+ contents and comments must be put into the body
+ element.Anchor cannot be nested.
+
+
+Non‐white‐space characters are not allowed
+ after the
html is closed.
+
+The
image element is
+ obsolete.
-Anchor cannot be nested.
a elements cannot be nested.
The document is non-conforming.a element.
Tag
+<$0>
- is not allowed in body.
-Start tag
<{text}>
+ is not allowed in the body element.body element, appears
in the input stream while the body element has been opened.
The document is non-conforming.Tag
+<$0>
- is not allowed in table.
+
+Some element is not closed before the end of
+ file.
+
+The
button element cannot be
+ nested.
+
+Element is not closed before the end of
+ file.
+
+Start tag
<form> is
+ not allowed in a form element.
+
+Start tag
<{text}> is
+ not allowed in a framset element.
+
+End tag
</{text}> is
+ not allowed in a frameset element.
+
+Non‐white‐space characters are not allowed
+ in a
frameset element.
+
+Start tag
+ <head>
+ is not allowed in the head element.<head> in the
+ <head> element. The document is non-conforming.head element, therefore no more than one
+ start tag <head> can appear in the input stream.
+
+A
+ DOCTYPE appears after any
+ element or data character has been seen.DOCTYPE appears after any element or data character
+ has been seen. The document is non-conforming.DOCTYPE must be placed before any
+ tag, reference, or data character. Only white space characters
+ and comments can be inserted before the DOCTYPE.
+
+The
nobr element cannot be
+ nested.
+
+The
{text} element is not
+ allowed in a noscript element in the
+ head element.
+
+An end tag
</{text}>
+ appers before the noscript element is closed.
+
+A
noscript element is not closed
+ before the end of file.
+
+Non‐white‐space characters are not allowed
+ in a
noscript element in the head
+ element.
+
+Element is not closed before the end of
+ file.
+
+Start tag
<{text}>
+ is not allowed in a select element.
+
+End tag
</{text}>
+ is not allowed in a select element.
-Start tag
<{text}>
+ is not allowed in a table element.table element, appears
in the input stream while the table element has been opened
@@ -236,10 +805,13 @@
a table caption.Data character is not allowed in
-
- table.table. The document
- is non-conforming.
+
+End tag
</{text}>
+ is not allowed in a table element.
-Non‐white‐space character is not allowed within
+ the
+ table element, outside of the caption and cells.table.
+ The document is non-conforming.table, only table related elements
are allowed; any other element and data character must be contained in
@@ -248,7 +820,10 @@
a table caption.Start tag of
tr
+
+
+The
isindex element is
+ obsolete.
-Start tag of
tr
element is missing.tr element, which is not
optional, is missing. The document is non-conforming.This document does not start with the
+
-This document does not start with a
DOCTYPE.DOCTYPE.
The document is non-conforming.DOCTYPE.DOCTYPE. XML declaration is not
+ allowed in HTML document.
Element
$0 is not
+
+
+Element
{text} is not
closed.body, colgroup, dd,
+ dt, head, html, li,
+ ol, option, optgroup,
+ p, rb, rp, rt,
+ tbody, td, tfoot,
+ th, thead, tr,
+ ul end tag can be omitted in HTML documents.
+ For any element except for void element, there must be an explicit
+ end tag.
+
+
+ canvas elementcanvas element is no longer
+ defined as empty. There must be an end tag
+ </canvas>.<a><b></a></b>, are not
+ allowed and they also cause this error.
-This
+ <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.This document is written in an old version of
+
-This document is written in an old version of
HTML.
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.
Element
$0 is not
+
+
+Start tag
<{text}> is
+ not allowed here.
+
+Element
{text} is not
opened.
+
+ base, basefont,
+ bgsound, br, col,
+ embed, frame, hr,
+ image, img, input,
+ isindex, link, meta,
+ param, spacer, or wbr element
@@ -308,126 +953,413 @@
The
+ DOCTYPE legacy string is
+ used.DOCTYPE with the DOCTYPE legacy
+ string, i.e.
+ <!DOCTYPE HTML PUBLIC "XSLT-compat">
+ is used.DOCTYPE legacy string should not be used for documents
+ generated from XSLT transformation process. It is allowed only to enable
+ to use XSLT style sheets with the HTML output mode, which does not
+ support generation of the DOCTYPE with no PUBLIC
+ identifier. For other purposes, the DOCTYPE legacy
+ string, i.e. PUBLIC "XSLT-compat",
+ is useless and should not be used.Element Content Model Errors
-Data character is not allowed in this
+
+
+The
base element with the
+ href attribute specified cannot be placed after
+ any attribute with a URL.
+
+The
base element with the
+ target attribute specified cannot be placed after
+ any element that defines a hyperlink.
-Data character is not allowed in this
context.
-
+ a or span)body,
- section, and blockquote.p.div or hn)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.
+
body,
+ section, and blockquote.p.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.There must be a
+$0
- element as a child of this element.
+
+Non‐white‐space characters are not allowed in
+ an empty element.
+
+Non‐white‐space characters are not allowed in
+ Person construct.
+
+Non‐white‐space characters are not allowed in
+ Text construct.
-There must be an element
+
{text} as a child of this element.$0 child element.
The document is non-conforming.
-
-
+ head element must contain exactly one
- title child element.tr
- element must contain one or more td or th
- child element.
+
head elementtitle child element.html elementhead child element followed
+ by a body element.tr elementtd or th child element.There must be a
td
+
-There must be a
td
or th element as a child of this element.tr element must contain at least one
td or th child element. The document
is non-conforming.This element is not allowed in this
+
+
+There must be an element
+
{text} in the Atom namespace as a child of this
+ element.
+
+There must be an Atom
link element
+ whose rel attribute is set to alternate as a
+ child of this element.
+
+There should be an Atom
link element
+ whose rel attribute is set to self as a
+ child of this element.
+
+There must be at least one
+
hn element descendant.
+This element is not allowed in this
context.
-
a or span)
+
a, progress, or imgbody,
section, and blockquote.p.div or hn)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 elementhtml
- element must have an xmlns attribute
- whose value is set to
- http://www.w3.org/1999/xhtml.aside,
+ div, hn,
+ p, or section
+
div,
+ li, td, or thp.<div><p>Hello!</p> World!</div>
+ is non-conforming, since a word World!
does not belong
+ to any paragraph. (If not part of any paragraph, what is
+ it!?) A conforming example would be:
+
+
+ <div><p>Hello!</p> <p>World!</p></div>div element cannot be
+ a child of an h1 element.noscript 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.blink,
+ center, or marquee elementbutton, datalist,
+ fieldset, form,
+ input, label,
+ optgroup, option, output,
+ rb, rp, rt, ruby,
+ textarea, or textarea element
+
+An
area element cannot be used
+ outside of a map element.
+
+There is another
base
+ element.
+
+In a
datatemplate element, only
+ rule elements are allowed.
+
+In a
details element, only at the
+ beginning of the element a lengend element
+ may be used.
+
+Elements are not allowed in an empty
+ element.
+
+In a
figure element, only at the
+ beginning or only at the end of the element a lengend element
+ may be used.
+
+This element is not allowed where flow
+ content is expected.
+
+A
style element without
+ scoped attribute is not allowed in this context.
+
+This element is not allowed in a
+
noscript element in the head element.
+
+A
style element with
+ scoped attribute is not allowed in the head
+ element.
+
+There is another
title
+ element.
+
+This element is not allowed in this
+ context.
+
+The character encoding declaration is not the
+ first child element in the
+ head element.<meta charset="..."> or
+ <meta http-equiv=Content-Type content="text/html; charset=...">
+ must be the first child element in the head element.title element and other metadata elements must
+ appear after any character encoding declaration is processed.
+
+This element is not allowed where metadata
+ content is expected.
+
+This element is not allowed where phrasing
+ content is expected.
+
+This element is not allowed as the root
+ element of a document.
+
+
+ html element in an XHTML documenthtml
+ element must have an xmlns attribute as:
+
+
<html xmlns="http://www.w3.org/1999/xhtml">rss elementfeed elementfeed element must be
+ in the http://www.w3.org/2005/Atom
+ namespace as:
+
+
+
+ <feed xmlns="http://www.w3.org/2005/Atom">
+
+This element is not allowed as the root element
+ of an XML document.
+
+This element is not allowed in the
ruby
+ element.
+
+This element is not allowed in this
+ context.
+
+This element is not allowed in an Atom
+
content element.
+
+This element is not allowed in Person
+ construct.
+
+This element is not allowed in Text
+ construct.
+
+This element is not defined.
+
+
+ event-source elementeventsource
+ element (no hyphen).m elementmark
+ element.
+
+No significant content is contained
+ in this element.
+
+There is no significant content
+ before this element.
+
+No significant content is contained
+ at the end of this element.
+
+There is no
+ {text}
+ element before this element.dt element
+ before any dd element.
+
The content of a
rp element must
+ be a parenthesis.Attribute Errors
-
+
+Required attribute
$0
+
+ cannot provide full functionality of the element to the user.
+
+ Required attribute
{text}
is not specified.img element must have
- alt and src attributes specified.
Without required attributes specified, user agents
- cannot provide the full functionality of the element
- to the user.
+
+ img elementsrc attribute must be specified.
+ Additionally, the alt attribute must be specified
+ in many cases.link elementrel attribute must be specified.
+ Note that the rev attribute is obsolete.
+
+For an
object at least one of
+ data and type attributes must be
+ specified.
+
+For a
base element, at least one of
+ href and target attributes must be
+ specified.
+
+For a
meta element with the
+ content attribute specified, exactly one of
+ name and http-equiv attributes must be
+ specified.
+
+For a
meta element, exactly one of
+ name, http-equiv, and charset
+ attributes must be specified.Attribute
+
+ {local-name} is not allowed for
+ {element-local-name} element.
+
+The
- xml:lang attribute is not
- allowed in HTML document.xml:lang attribute is not allowed in
- HTML document. The document is non-conforming.lang attribute in the null
- namespace for HTML elements is defined as conforming only for
- XML document.
+
+ meta elementmeta element, only one of
+ name, http-equiv, or charset
+ attribute is allowed.
+
+The
ismap attribute may only be
+ used for the image contained in an a element.
+
+This attribute is not defined.
+
+
+ align attribute (various HTML elements)border attribute (various HTML elements)autosubmit attribute (menu element)language attribute (script element)<script>
/* JavaScript code */
</script>type attribute, as follows:
+
+
+ <script type="text/javascript">.<script type="text/vbscript">.
-The
+ xml:lang attribute in HTML
+ document is ignored.xml:lang attribute does not have an effect in
+ HTML document.xml:lang attribute is only applicable to XML
+ documents. In HTML document, it is only allowed to ease migration
+ from XML.lang attribute instead.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
charset attribute is not
+
-The
charset attribute is not
allowed in XML document.charset attribute of a
meta element is not allowed in XML document.
@@ -436,45 +1368,249 @@
-
+<?xml version="1.0" encoding="encoding-name"?><?xml version="1.0" encoding="encoding-name"?>
+The
- lang attribute is not
- allowed in XML document.lang attribute is not allowed in
- XML document. The document is non-conforming.lang attribute in null
- namespace for HTML elements is defined as conforming only for
- HTML document.
- A
noscript element cannot be
+ used in XML document.xml:lang attribute instead.
-The
xml:lang attribute in no namespace
+ is only allowed in HTML document.The
xmlns attribute
+
+The
xmlns attribute
in the null namespace is not allowed in
XHTML document. The document is non-conforming.xmlns attribute in the null
namespace is not allowed in XHTML document.
+
The
xml:lang attribute is only allowed
+ when the lang attribute is specified.Attribute Value Errors
-
+This attribute only allow a limited set of
- values and the specified value is not one of them.
+
+Attribute value
{@}
+ is not allowed. It must be an empty string or a string
+ {local-name}.
+
+The attribute value must be exactly one
+ character.
+
+A character reference cannot be used to
+ represent a character encoding name.
+
+Character encoding name
+
{value} is not the preferred name of that
+ character encoding.
+
+Character encoding name
+
+ {value} is not a registered name.
+
+
+ EUC-TWEUC-TW is not registered. Unfortunately, there
+ is no registered name for that character encoding. Use
+ Big5 encoding with character encoding name Big5
+ if it is enough to represent the document.ISO-2022-JP-1ISO-2022-JP-1 is not registered, nevertheless
+ this character encoding name is documented in
+ RFC 2237. Use
+ ISO-2022-JP-2 instead, since that character encoding
+ is a superset of ISO-2022-JP-1.ISO-2022-JP-3, ISO-2022-JP-3-plane1ISO-2022-JP-2004 and
+ ISO-2022-JP-2004-plane1.ISO-2022-JP-2003,
+ ISO-2022-JP-2003-plane1ISO-2022-JP-2004 and
+ ISO-2022-JP-2004-plane1.ISO-2022-JP-2004,
+ ISO-2022-JP-2004-plane1UTF-8NUTF-8N is not registered. Character encoding
+ name UTF-8 represents UTF-8 encoding with or
+ without BOM.
+
+Character encoding name
+
+ {value} is a private name.
+
+ x-euc-jpEUC-JP for the Japanese EUC
+ character encoding.x-sjisShift_JIS for standard Shift encoding scheme of
+ JIS coded character set, or Windows-31J
+ for Microsoft standard character set as implemented by
+ Microsoft Windows.
+
+The specified value
+ {value}
+ is syntactically not a character encoding name.
+
+The specified value is not a color
+ name or hexadecimal color number.
+
+The
coords attribute have to
+ contain three (3) numbers (specified:
+ {text}).
+
+The
coords attribute have to
+ contain four (4) numbers (specified:
+ {text}).
+
+The
coords attribute have to
+ contain more than or equal to six (6) numbers (specified:
+ {text}).
+
+The
coords attribute have to
+ contain even number of numbers (specified:
+ {text}).
+
+The specified value
{value}
+ is out of range.
+
+The specified value is not valid.
+
+Year number is out of range.
+
+Month number is out of range.
+
+Day number is out of range.
+
+Hour number is out of range.
+
+Minute number is out of range.
+
+Second number is out of range.
+
+Hour number of the timezone component is out of
+ range.
+
+Minute number of the timezone component is out of
+ range.
+
+The attribute value is not a datetime.
+
+The value is not a date or time.
+
+This attribute only allow a limited set of
+ values and the specified value
+ {@} is not one
+ of them.
+
+ meta element, http-equiv attributeDefault-Style and Refresh
+ are allowed.Content-Type is obsolete; for charset
+ declaration, the charset attribute can be used as:
+
+
+ ... where charset-name is a name of the character encoding
+ of the document, such as <meta charset="charset-name">utf-8.
+ Content-Style-Type and
+ Content-Script-Type are currently not allowed.Keywords is not allowed. Use
+ name attribute instead of http-equiv
+ attribute.Expires, Pragma,
+ and Cache-Control are not allowed;
+ use real HTTP header fields for cache control.
+
+Character encoding declaration syntax
+
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is obsolete.<meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is in use. The document is non‐conforming.
+
+
+ <meta charset="charset-name">
+
+Attribute value
{@}
+ is not allowed.
-There is another pragma
+
{value}.This identifier has already been
+
-This identifier has already been
assigned to another element.
The link type
$0
+
+
+The token
{value}
+ appears in the attribute value twice.
+
+The attribute value is empty.
+
+The value of the
+ title attribute
+ is empty.title attribute value of the link
+ element that defines an alternate style sheet is an empty value.link element whose rel attribute
+ is alternate stylesheet defines an alternate style sheet.
+ An alternate style sheet must be associated with a name using the
+ title attribute. The name cannot be empty.
+
+The specified value is out of range.
+
+The attribute value is not a real
+ number.
+
+A fragment identifier references the element
+ itself.
+
+A fragment identifier references no
+ node.
+
+A hash−name reference must start with a
+
# character.
+
+The
id attribute value is
+ different from the name attribute value.
+
+The attribute value is not an integer.
-The link type
{value}
cannot be specified for this element.link element.
+
+The link type
$0
+
+
+Attribute value
{@}
+ is not an allowed value.
+
+The attribute value is not a length
+ value.
+ The link type
- {value}
is non-conforming.copyright
- you must use link type license.
+
+ contentsindex.copyrightlicense.homeindex.previousprev.startfirst.toc or topindex.
+
+The specified value is not a valid as a long
+ character encoding declaration.
+
+The specified character encoding name
+
+ {value} is different from the actual document
+ character encoding {text}.
+
+Whether the specified character encoding name
+
{value} matches to the actual character encoding
+ name cannot be checked since the input is not a byte stream.
+
+The attribute value is not a valid mode
+ name.
+
+The specified value is out of range.
+
+The attribute value is not a non‐negative
+ integer.
+
+
+
+The
usemap attribute references
+ no image map.
+
+There is no table header cell whose
id
+ is {value} in the same table.
+
+the specified value is not a valid as part
+ of a
Refresh pragma.
+
+The attribute value is not an integer or
+ a string
template.
+
+Browsing context name
+
+ {@} is reserved.
+ This browsing context name is reserved.
_
+ (U+005F LOW LINE)
+ are reserved so that it must not be used._blank,
+ _main, and _replace.
+ However, they are not conforming attribute values.
-Namespace name
{text}
+ is reserved and cannot be used for an arbitrary prefix.Attribute Value Warnings
+
-Namespace prefix
{text}
+ is reserved and cannot be used for an arbitrary namespace name.Link type
$0
+
+Link type
{value}
is proposed but not accepted yet; it should not be
used until it has been accepted.
+
+The specified value
{value}
+ is not a valid value.
+
+White space characters are not allowed
+ in the
id attribute.
+
+The node referenced by the
template
+ attribute is not a template.
+
+Browsing context name must not be empty.
+
+Browsing context name
+
{value} is reserved.
+
+The word
{value} is not
+ allowed in this attribute.
+
+The specified value is not a legal XML Namespaces
+ 1.0
NCName.
+
The value of the
+ xml:lang attribute
+ is different from the value of the lang attribute.xml:lang attribute (either the
+ lang attribute in the xml (i.e.
+ http://www.w3.org/XML/1998/namespace) namespace, or
+ the xml:lang attribute in no namespace) for the element has
+ different value than that of the lang attribute in no
+ namespace.lang
+ and xml:lang. In HTML documents, only lang
+ attribute in no namespace is allowed and take effect; the
+ xml:lang attribute in no namespace is ignored in HTML
+ documents. In XHTML documents, both lang and
+ xml:lang attributes are allowed.lang attribute need to be
+ specified for an element.lang and xml:lang attributes are
+ specified on the same element, their values must be the same value.Table Model Errors
-This
colspan attribute
+
+
+Cell slot ({text}) is filled by
+ multiple cells.
-This
colspan attribute
results in creating a table column that does not contain
any cell anchored to it.The table has no cell (
td or
+
+
+This column has no anchored cell.
+The table has no cell (
td or
th) in the last row.
+
+This
+ rowspan attribute
+ results in creating a table row that does not contain
+ any cell anchored to it.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.
+
+ ... since the second row contains only
+ a cell that spans between first and second rows.
+ <table>
+<tbody>
+<tr><td rowspan=2></td></tr>
+</tbody>
+</table>
+
+This row has no anchored cell.
+
+
This
rowspan attribute
+ results in creating a table row that does not contain
+ any cell anchored to it.Internet Media Type Warnings
+Internet Media Type Errors
+
+
-The specified value is not a valid value
+ as a multipart boundary.
+An obsolete subtype is used.
-The specified value is not a valid value
+ for the attribute
e4x.
+A private (
x- or x.)
- subtype is used.
-The specified value,
+
{value}, is syntactically not a valid
+ attribute name.
+The subtype is not registered to IANA.
+
+The specified media type is a composite
+ type, which is not allowed in this context.
+
+An Internet Media Type whose intended usage
+ is limited use,
{value} is used.
+
+The specified value is not an Internet Media
+ Type.
+
+An obsolete parameter
+
{value} is used.
+
+An obsolete Internet Media Type
+
+ {value} is used.
+
+ text/ecmascripttext/ecmascript is obsoleted in
+ favor of application/ecmascript. Note that
+ text/javascript would be the better alternative
+ in many cases.text/javascripttext/javascript is obsoleted by
+ IETF with backward incompatible alternate
+ application/javascript for architectural
+ purity. Those who prefer reality to academic
+ purity may ignore this warning.
+
+Parameter
{text} have to
+ be specified for the Internet Media Type
+ {value}.
+
+Parameter
{value} is not
+ allowed for this Internet Media Type.
+
+Use of a private Internet Media Type
+
{value} is not encouraged.
+
+Use of a private type
+
{value} is not encouraged.
+
+Value
{value} is
+ syntactically not a valid subtype value of an Internet Media Type.
+
+Value
{value} is
+ syntactically not a valid type.
+
+An unknown parameter
{value}
+ is used. The conformance checker cannot determine whether use of this
+ parameter is valid or not.
+
+An unknown Internet Media Type
+
{value} is used. At the time of the update of
+ the conformance checker's Internet Media Type database, the subtype is
+ not reigstered to the IANA registry. The subtype, however, might be
+ registerd to the IANA registry thereafter. Please consult the IANA
+ registry.
+
+Use of an Internet Media Type
+
{value} is not encouraged since it is not
+ part of the IANA registry.
+
+Use of a type
+
{value} is not encouraged since it is not
+ a standardized type.A value that is not an Internet Media Type
+ is not allowed here.
URI (or IRI) Errors
+URL Errors
-
+This string is syntactically not an IRI.
-The specified value is syntactically not an
+ IRI.
+
+The specified value is syntactically not an IRI
+ reference.
+ URI (or IRI) Warnings
+
+
+
+ (U+0020
+ SPACE) character cannot be
+ used in IRI references.
+
+The specified value is syntactically not an RDF
+ URI reference.
+
+The specified value is syntactically not a
+ URI according to RFC 2396.
-The specified value is syntactically not a
+ URI.
Dot-segment (
+. or
- ..) should not occur in an absolute reference.
+
+URL host address format
+
{text} is not defined.
+
+Default port number should be omitted.
-A dot-segment (
. or
+ ..) occurs in an absolute reference.. or ..) should
not occur in an absolute reference.
+This IRI should explicitly end with
-
/.
+
+The host component of the URL is empty.
+
+The URL does not end with
+ a
/ character.
+
+The port component of the URL is empty.
-The fragment component of the URL is not
+ allowed.
Hexadecimal digit in percent-encoding
- should be in lowercase.
+
+
+The host component of the URL
+ is too long.
-A lowercase hexadecimal digit is used
+ in percent-encoding.
An unreserved character is
+
+
+The host component of the URL
+ is not a DNS host name.
+
+The host component of the URL
+ is not encoded in UTF-8.
+
+Password should not be included in a URL
+ for the security.
+An unreserved character is
percent-encoded.
+
+The host
{value}
+ should be spelt in lowercase.
+
+
+
+URL scheme name is in uppercase.
+ Media Query Errors
+
+
+
+The specified value has a syntax error as a
+ media query.
+
+Media type
{value} is
+ not supported by the conformance checker.Selectors Errors
+
+
+
+Argument list of the pseudo-class is
+ not closed by a
) character.
+
+Numbers in the argument
+
an+b have to be integers.
+
+Argument
an+b is
+ syntactically incorrect.
+
+Attribute selector is not closed by
+ a
] character.
+
+Argument list of the
:lang
+ selector is not closed by a ) character.
+
+Namespace prefix
{value}
+ is not declared.
+
+Attribute local name is missing.
+
+Attribute matching operator (e.g.
+
=) is missing.
+
+Attribute name is missing.
+
+Attribute namespace wildcard
*
+ is not followed by a | character.
+
+Attribute value is missing.
+
+Class name is missing.
+
+Combinator is missing.
+
+No string is specified in the argument
+ list of the
:-manakai-contains pseudo-class
+ selector.
+
+Language tag argument is missing.
+
+Local name part of the type selector (or
+
* for the universal selector) is missing.
+
+Pseudo-class name is missing.
+
+Pseudo-element name is missing.
+
+Sequence of simple selectors is
+ expected.
+
+Argument list of the
:not selector
+ is not closed by a ) character.
+
+Simple selector is not allowed after a
+ pseudo element.
+
+Pseudo-class
:{value}
+ is not supported by the conformance checker.
+
+Pseudo-element
::{value}
+ is not supported by the conformance checker.CSS Errors
+
+
+
+An
@{text} rule is not
+ allowed here.
+
+The
@{text} rule is
+ syntactically incorrect.
+
+Block is not closed before the end of
+ file.
+
+Component
<{text}> is
+ already specified.
+
+Value
hand is not valid as
+ <'cursor'>.
+
+Specified value is syntactically not a correct
+
<{text}>.
+
+No declaration block is found after a group of
+ selectors.
+
+A
: character is missing after
+ a property name.
+
+Property name is expected.
+
+A
; character is missing at the
+ end of the property.
+
+Priority part of the declaration is syntactically
+ incorrect.
+
+The
@{value} rule is
+ not supported by the conformance checker.
+
+Property
{value} is
+ not supported by the conformance checker.Cache Manifest Errors
+
+
+
+This URL is found both in the explicit or
+ fallback entries and in the online whitelist.
+
+The specified URL has different origin from
+ the manifest.
+
+The scheme component of the URL is
+ different from that of the manifest URL. The URL is ignored.
+
+This oppotunistic caching namespace is already
+ specified.
+
+Fallback entry URL is missing.
+
+This document is not a cache manifest.
+ text/cache-manifest must contain a cache manifest.CACHE MANIFEST
+ (exactly one space character between
+ CACHE and MANIFEST).
+
+This URL is same as the manifest URL.
Stability Information
+
+
+
+This attribute is deprecated.
+
+This element is deprecated.
+
+This element is in the
+ call for implementation stage.
+
+
+This element is in the last
+ call for comments stage.
+
+
+This element is documented in a working
+ draft.
+
+
+This element is not part of any
+ standard the conformance checker knows.
+
+
+This attribute is in the
+ call for implementation stage.
+
+
+This attribute is in the last
+ call for comments stage.
+
+
+This attribute is documented in a working
+ draft.
+
+This attribute is not part of any
+ standard the conformance checker knows.
+ Language Tag Errors
+
+
+
+There is another extension subtag
+
{value}.
+
+Subtag
{value} is
+ syntactically invalid.
+
+It is a good practice to represent ISO 639-1
+ language code
{value} in lowercase.
+
+Langauge tag
mul should not be
+ used.
+
+No semantics is defined for language subtag
+
{value}.
+
+The language subtag
{value}
+ is syntactically invalid.
+
+Langauge tag
und should not be
+ used.
+
+It would be better if a private use language
+ tag (
{value}) is not used.
+
+Private use subtag
{value}
+ is syntactically invalid.
+
+It is a good practice to represent ISO 3166
+ country code
{value} in uppercase.
+
+No semantics is defined for region subtag
+
{value}.
+
+Use of private use country code
+
{value} is not allowed.RDF/XML Errors
+
+
+
+The namespace URI of an element that
+ represents an RDF concept must be
+
http://www.w3.org/1999/02/22-rdf-syntax-ns#.
+
+The specified value is already used as an
+ ID.
+
+Both unqualified attribute and namespace‐qualified
+ RDF attribute are specified, which is not allowed.
+
+An invalid value is specified to
+ the
parseType attribute.
+
+There is another element, such that
+ this element is not allowed.
+
+Unqualified attribute is not allowed.
+
RDF attribute should be
+ namespace‐qualified.
Unsupported Messages
-This attribute is not supported by the
- conformance checker; it might or might not be conforming.
-
-Conformance checking for element
+
+ {local-name} is not supported; it might or
+ might not be conforming.This element is not supported by the
- conformance checker; it might or might not be conforming.
-
-Conformance checking for attribute
+
+ {local-name} of element
+ {element-local-name} is not supported;
+ it might or might not be conforming.The link type
$0 is not
+
-Link type
{value} is not
standardized or registered at the time of the release of the conformance
- checker; it is non-conforming unless it has now been
+ checker; it is non-conforming unless it now has been
registered.rel attribute is defined as a list of link types.
Some common link types are defined in the HTML5 specification.
@@ -613,37 +2355,293 @@
The link type might have been added to the registry since then.
In such case it might be conforming. Otherwise, the
document is non-conforming.
+
shortcut iconshortcut is not registered.
+ Use only icon for linking to so-called favicon.Conformance checking for event handler attribute
+
-Conformance checking for event handler attribute
is not supported; it might or might not be conforming.
Conformance checking for language tag
+
-Conformance checking for media query
is not supported; it might or might not be conforming.
Conformance checking for media query
+
-Conformance checking for an
addr-spec
is not supported; it might or might not be conforming.Conformance checking for script
- language
$0 is not supported;
+
-Conformance checking for script
+ language
{text} is not supported;
it might or might not be conforming.Conformance checking for style
- language
$0 is not supported;
+
+Conformance checking for style
+ language
{text} is not supported;
it might or might not be conforming.
+
+Conformance checking for an Atom
+
content element with type
+ {text} is not supported.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+No more information is available.
+
+
+MUST‐level
+ error
+
+
+SHOULD‐level
+ error
+
+
+Warning
+
+
+Information
+
+
Not
+ supported
+ License of This Document
-<w@suika.fam.cx>.