$0
+ is not allowed for HTML document.The character encoding used for the document is not allowed + for HTML document. The document is non‐conforming.
+$0
+ should not be used for HTML document.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
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is obsolete. The new syntax is:
<meta charset="charset-name">Note that the encoding declaration in XML
+ declaration has no effect for HTML document.
$0
+ is not a superset of ASCII.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:
+Content-Type: text/html; charset=charset-nameExistence of HTML character encoding declaration, i.e.
+ <meta charset="charset-name">,
+ does not allow to omit charset parameter
+ for HTML document encoded in non‐ASCII
+ compatible encoding.
Character encodings Shift_JIS, Windows-31J,
+ and ISO-2022-JP are not a superset of
+ ASCII for the purpose of HTML conformance.
{text} (Sniffed because no explicit specification
+ for the character encoding of this document is found in the transfer
+ procotol headers).{text} because no explicit specification
+ for the character encoding of this document is found in the transfer
+ procotol headers.{text} is used. Checking results might be
+ wrong.{text} is not supported.{text} is same as the character encoding specified
+ in the character encoding declaration. This is not an
+ error.{text}, a character encoding declaration specifying
+ a different character encoding is found. The document
+ is reparsed.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:
+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.NULL character
+ is not allowed.{text} is
+ not allowed.", ', and =."
+ or ' if it contains a ", ', or
+ = character.& character must
- introduce a reference.&.
An & (U+0026
- AMPERSAND) character which
+
An & character which
is not part of any reference appears in the input stream.
- The document is non-conforming.
Any & character in URI (or IRI)
- must be escaped as &.
Any & character in URI (or IRI)
+ must be escaped as &.
The & character must
be the first character of a reference:
-
&entity-name;</ string is not followed
by a tag name.< character is not followed
by tag name or by a ! character.&#.The string &# must be the first two characters
of a reference:
-
&#d;&#x.<! is not followed
by --.<!-- (<! immediately followed
+ <!-- (<!
+ immediately followed
by two -s) and must be terminated by
- -->. Strings <! not followed
+ -->.
+ 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 documents.DOCTYPE
+ and comment declarations, are not allowed in HTML document.<!<! must be escaped as
- <!.<!.
</ is not followed
by tag name.{text} is not allowed.U+000D (CARRIAGE RETURN)
+ is not allowed.-- sequence
in a comment.$0.{text}.
There are more than one attributes with the same name in a tag. The document is non-conforming.
@@ -259,8 +487,36 @@<>) is not
+ allowed.</>) is not
+ allowed.{text} is not allowed./>) cannot be
used for this element.<script/>The polytheistic slash cannot be used for script
element. Even for an empty script element,
- there must be an explicit end tag </script>.
</script>.
NOTE: Though some user agents interpret
polytheistic slash for script element as the
@@ -294,7 +551,10 @@
to allow polytheistic slash for these elements.
<a/>, <p/><p></p>Note that, unlike in XML, the polytheistic slash has @@ -302,11 +562,55 @@
<!DOCTYPE , the
+ document type name must be specified.PUBLIC, no
+ oublic identifier is specified.; character.<!DOCTYPE, there
+ must be at least a white space character before the document type
+ name.SYSTEM, no
+ system identifier is specified.<?...>) cannot be used.<?...>) is not allowed in HTML
+ document.
Processing instructions (<?...?>),
including XML declaration (<?xml ...?>)
@@ -319,7 +623,13 @@
binding property in CSS
- style sheet.<style>
+p {
+ binding: url(binding.xbl);
+}
+</style><?xml?> (XML declaration)<?xml-stylesheet?> (XML style sheet
@@ -327,7 +637,9 @@
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)PUBLIC.SYSTEM.-->.DOCTYPE is not closed by a
+ > character.>
+ character.<{text}> is
+ not allowed after the body is closed.</{text}> is
+ not allowed after the body is closed.body is closed.<{text}> is
+ not allowed after the frameset is closed.</{text}> is
+ not allowed after the frameset is closed.frame is closed.$0 element cannot be
- inserted between head and body elements.{text} element cannot be
+ inserted between head and body
+ elements.A start tag appears after the head element is closed
but before the body element is opened.
@@ -362,22 +794,37 @@
DOCTYPE appears after any
- element or data character has been seen.A DOCTYPE appears after any element or data character
- has been seen. The document is non-conforming.
The DOCTYPE must be placed before any
- tag, reference, or data character. Only white space characters
- and comments can be inserted before the DOCTYPE.
<{text}> is
+ not allowed after the html is closed.</{text}> is
+ not allowed after the html is closed.html is closed.image element is
+ obsolete.HTML a elements cannot be nested.
@@ -389,8 +836,9 @@
<$0>
+ class="parse-error"
+ modules="HTML::Parser">
+ <{text}>
is not allowed in the body element.The start or end tag of an element, which @@ -400,8 +848,58 @@
button element cannot be
+ nested.<form> is
+ not allowed in a form element.<{text}> is
+ not allowed in a framset element.</{text}> is
+ not allowed in a frameset element.frameset element.<head>
is not allowed in the head element.DOCTYPE appears after any
+ element or data character has been seen.A DOCTYPE appears after any element or data character
+ has been seen. The document is non-conforming.
The DOCTYPE must be placed before any
+ tag, reference, or data character. Only white space characters
+ and comments can be inserted before the DOCTYPE.
nobr element cannot be
+ nested.{text} element is not
+ allowed in a noscript element in the
+ head element.</{text}>
+ appers before the noscript element is closed.noscript element is not closed
+ before the end of file.noscript element in the head
+ element.<{text}>
+ is not allowed in a select element.</{text}>
+ is not allowed in a select element.<$0>
+ class="parse-error"
+ modules="HTML::Parser">
+ <{text}>
is not allowed in a table element.The start or end tag of an element, which @@ -432,13 +1006,21 @@
table.</{text}>
+ is not allowed in a table element.table element, outside of the caption and cells.A data character appears in table. The document
- is non-conforming.
A non‐white‐space character appears in table.
+ The document is non-conforming.
In table, only table related elements
are allowed; any other element and data character must be contained in
@@ -448,8 +1030,16 @@
isindex element is
+ obsolete.tr
element is missing.DOCTYPE.$0 is not
+ class="parse-error"
+ modules="HTML::Parser">
+ {text} is not
closed.End tag of an element is not found before, for example, @@ -506,7 +1098,7 @@
canvas element is no longer
defined as empty. There must be an end tag
- </canvas>.</canvas>.
Note that misnesting tags, such as @@ -516,7 +1108,8 @@
<html> tag is not
the first start tag.The document contains a DOCTYPE declaration
that is different from HTML5 DOCTYPE (i.e.
- <!DOCTYPE HTML>). The document is non-conforming.
<!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 @@ -550,9 +1145,17 @@
<{text}> is
+ not allowed here.$0 is not
+ class="parse-error"
+ modules="HTML::Parser">
+ {text} is not
opened.An end tag appears though no element with the same name
@@ -672,11 +1275,11 @@
block-level content, any inline-level content must be
put in e.g. paragraph element such as p.
For example, an HTML document fragment
- <div><p>Hello!</p> World!</div>
+ <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><p>Hello!</p> <p>World!</p></div>html element in 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.
In XHTML document, the root html
+ element must have an xmlns attribute as:
+
<html xmlns="http://www.w3.org/1999/xhtml">rss elementThe 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.
feed elementThe Atom feed element must be
- in the http://www.w3.org/2004/Atom
- namespace.
http://www.w3.org/2005/Atom
+ namespace as:
+ <feed xmlns="http://www.w3.org/2005/Atom">The conformance checker does not support Atom 0.3. Use Atom 1.0 for feed documents.
$0
+ is not registered.The specified character encoding name is not registered to + IANA. Use of registered character encoding name + is a good practice to facilitate interoperability.
+ +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.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.
+$0 is a private
+ character encoding name.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.
+ +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 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.
+meta element, http-equiv attributeOnly Default-Style and Refresh
- is allowed.
Only values Default-Style and Refresh
+ are allowed.
Value Content-Type is obsolete; for charset
declaration, the charset attribute can be used as:
<meta charset="charset-name"><meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
is obsolete.Old long charset declaration syntax
- <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+
Old long character encoding declaration syntax
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
is in use. The document is non‐conforming.
The new charset declaration syntax is: -
<meta charset="charset-name">The new character encoding declaration syntax is: +
<meta charset="charset-name">$1
+ is different from document character encoding
+ $0.The specified character encoding name is different from + the character encoding of the document. The document + is non‐conforming.
+For example, the table below is non-conforming: -
<table>
+ <table>
<tbody>
<tr><td rowspan=2></td></tr>
</tbody>
@@ -1210,12 +1907,77 @@
text/cache-manifest must contain a cache manifest.
A cache manifest must start with a line whose content is
- CACHE MANIFEST (exactly one space character between
+ CACHE MANIFEST
+ (exactly one space character between
CACHE and MANIFEST).
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.
+innerHTML of HTML elementinnerHTML に値を設定する HTML 要素charset parametercharset 引数versionversionencodingencodingstandalonestandaloneBOM)BOM つき){text}){text})Important: This conformance checking service + is under development. The result above might be wrong.
+重要: この適合性検査サービスは開発中です。 + この結果は間違いかもしれません。
+Copyright +
Copyright ‐
Wakaba
<w@suika.fam.cx>.