HTML5 Character Encoding Errors

+ + + Character encoding {text} + is not allowed for HTML document. + +

The character encoding used for the document is not allowed + for HTML document. The document is non‐conforming.

+ + + + + Character encoding {text} + 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 is encouraged (this document + is encoded in {text}). + +

Use of UTF-8 as the character encoding of the document is encouraged, + though the use of another character encoding is still conforming.

+ + + + + Conformance for character encoding requirements + cannot be checked, since the input is not a byte stream. + +

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.

+ + + + + There is no character encoding + declaration. + +

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.

+ + + + + No character encoding metadata is found + in lower‐level protocol nor is there BOM, while + character encoding {text} + 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-name

+ +

Existence 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.

+ + + + + 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. + + + + Since no decoder for the document character + encoding is found, decoder for the character encoding + {text} is used. Checking results might be + wrong. + + + + 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. + +

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:

Specify charset parameter in the Content-Type + field in the HTTP header, as: +
```
Content-Type: text/html; charset="charset-name"
```
Put the character encoding declaration + (<meta charset="charset-name">) + just after <head> start tag.
Use UTF-8.

+ + + + + The NULL character + is not allowed. + + + + Code point {text} is + not allowed. + + +

HTML5 Parse Errors in Tokenization Stage

@@ -28,19 +218,52 @@ + + Tag <$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.

+ + + + + Attribute name cannot contain characters + ", ', and =. + + + + Attribute value must be quoted by " + or ' if it contains a ", ', or + = character. + + + class="tokenize-error" + modules="HTML::Parser"> The & character must - introduce a reference. + be escaped as &. -

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.

+ The document is non‐conforming.

+ +

Any & character in URI (or IRI) + must be escaped as &.

The & character must be the first character of a reference: -

Named entity reference

&entity-name;

where entity-name is the name of the @@ -63,8 +286,50 @@ + + A </ 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: +

&lt;/

+ + + + + A < 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.

+ +

The < character as a data character must + be escaped as: +

&lt;

+ + + + class="tokenize-error" + modules="HTML::Parser"> The decimal representation of the code position of a character must be specified after &#. @@ -76,9 +341,8 @@ The document is non-conforming.

The string &# must be the first two characters - NUMBER SIGN) character must be the first two characters of a reference: -

Numeric character reference

&#d;

where d is the decimal representation of @@ -91,14 +355,15 @@

To represent &# as data characters, use - named entity reference: + a named entity reference for the & character:

&amp;#

+ class="tokenize-error" + modules="HTML::Parser"> The hexadecimal representation of the code position of a character must be specified after &#x. @@ -113,15 +378,108 @@ of the code point of the character to be referenced.

To represent &#x as data characters, use - named entity reference: + a named entity reference for the & character:

&amp;#x

+ + String <! is not followed + by --. + +

There is a < (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.

+ +

Comments: In HTML document, comments must be introduced by + . + Strings <! not followed + by -- and <!- not followed by + - are not valid open delimiters for comments.
Marked sections, including CDATA sections: Marked sections are not allowed in HTML document.
Markup declarations: Markup declarations, except for DOCTYPE + and comment declarations, are not allowed in HTML document.
String <!: String <! must be escaped as + <!.

+ + + + + String </ is not followed + by tag name. + +

+ +

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: +

&lt;/

+ + + + + Character reference to + {text} is not allowed. + + + + Character reference to + U+000D (CARRIAGE RETURN) + is not allowed. + + + + There is a -- sequence + in a comment. + +

There is a - (U+002D + HYPHEN-MINUS) character + at the end of the comment or a -- sequence + in the comment. The document is non-conforming.

+ +

Comments cannot contain a string --, as in XML. + Unlike SGML, there cannot be more than one comments + (where comment is an SGML term) in the comment + declaration.

+ + + - There are two attributes with same name. + class="tokenize-error" + modules="HTML::Parser"> + There are two attributes with name + {text}.

There are more than one attributes with the same name in a tag. The document is non-conforming.

@@ -131,34 +489,306 @@ + + Empty start tag (<>) is not + allowed. + + + + Empty end tag (</>) is not + allowed. + + + + End tag cannot have attributes. + + + + Character reference to + {text} is not allowed. + + - Void element syntax (/>) cannot be + class="tokenize-error" + modules="HTML::Parser"> + Polytheistic slash (/>) cannot be used for this element. -

Void element syntax (/>) must not be used +

Polytheistic slash (/>) must not be used for the element. The document is non-conforming.

The void element syntax can only be +

The polytheistic slash can only be used for base, link, meta, hr, br, img, embed, param, area, col, and input elements.

Note that, unlike in XML, the void element syntax has +

<script/>

The polytheistic slash cannot be used for script + element. Even for an empty script element, + there must be an explicit end tag + </script>.

+ +

NOTE: Though some user agents interpret + polytheistic slash for script element as the + closing of the element, such usage is not allowed under + the current standard.

<basefont/>, <bgsound/>, + <frame/>, <keygen/>, + <spacer/>, <wbr/>

These elements are themselves non-conforming.

<command/>, <event-source/>, + <nest/>, or <source/>

Future revision of HTML5 parsing algorithm is expected + to allow polytheistic slash for these elements.

<a/>, <p/>

These elements are not always empty and therefore + polytheistic slash is not allowed. Use explicit end tag + to represent empty element as: +

<p></p>

+ +

Note that, unlike in XML, the polytheistic slash has no effect in HTML.

+ + 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. + + + + 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. + +

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.

+ +

<?xbl?> (XBL Association)

An XBL binding cannot be associated by + PI in HTML + document. Use binding property in CSS + style sheet as: +

<style>
+p {
+  binding: url(binding.xbl);
+}
+</style>

<?xml?> (XML declaration)

XML declaration is unnecessary for HTML documents.

<?xml-stylesheet?> (XML style sheet + PI)

Use HTML 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)

The conformance checker does not support + checking for PHP source documents.

Other processing instructions

Processing instructions cannot be inserted in an HTML + document. Use XML document or insert + ProcessingInstruction node by scripting.

+ +

Web browsers will parse processing instructions as bogus + comments. Some legacy Web browsers, such as IE:mac and + some mobile Web browsers, will display processing instructions + as string.

+ + + + + 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

+ + 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 $0 element cannot be - inserted between head and body elements. + The {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. @@ -166,13 +796,209 @@ - - Tag <$0> - is not allowed in table. + + Start tag <{text}> is + not allowed after the html is closed. + + + + End tag </{text}> is + not allowed after the html is closed. + + + + Non‐white‐space characters are not allowed + after the html is closed. + + + + The image element is + obsolete. + + + + Anchor cannot be nested. + +

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.

+ + + + + Start tag <{text}> + is not allowed in the body element. -

The start or end tag of an element appears in table. +

The start or end tag of an element, which + cannot be a descendant of body element, appears + in the input stream while the body element has been opened. The document is non-conforming.

+ + + + + 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. + +

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.

+ + + + + A 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.

+ + + + + 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. + +

The start or end tag of an element, which + cannot be a child of table element, appears + in the input stream while the table element has been opened + but no other element has been opened. The document is non-conforming.

In table, only table related elements are allowed; any other element must be contained in @@ -182,13 +1008,21 @@ - - Data character is not allowed in - table. + + 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. -

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 @@ -198,8 +1032,16 @@ + + The isindex element is + obsolete. + + + class="parse-error" + modules="HTML::Parser"> Start tag of tr element is missing. @@ -215,8 +1057,9 @@ - This document does not start with the + class="parse-error" + modules="HTML::Parser"> + This document does not start with a DOCTYPE.

The document does not start with a DOCTYPE. @@ -227,29 +1070,74 @@

Only white space characters and comments are allowed - before the DOCTYPE.

+ before the DOCTYPE. XML declaration is not + allowed in HTML document.

- Element $0 is not + class="parse-error" + modules="HTML::Parser"> + Element {text} is not closed.

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 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.

+ +

HTML canvas element: Though the element is void in earlier versions of Safari, + the canvas element is no longer + defined as empty. There must be an end tag + </canvas>.

+ +

Note that misnesting tags, such as + <a><b></a></b>, are not + allowed and they also cause this error.

+ + + + + This <html> tag is not + the first start tag. + +

There is a start tag of the html element + that it not the first start tag in the input stream. + The document is non-conforming.

+ +

In an HTML document, there cannot be more than one + 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.

+ class="parse-error" + modules="HTML::Parser"> This document is written in an old version of HTML.

The document contains a DOCTYPE declaration - that is different from HTML5 DOCTYPE (i.e. <!DOCTYPE - HTML>). The document is non-conforming.

+ that is different from HTML5 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 @@ -259,10 +1147,38 @@ + + Start tag <{text}> is + not allowed here. + + - Element $0 is not + class="parse-error" + modules="HTML::Parser"> + Element {text} is not opened. + +

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.

+ +

HTML base, basefont, + bgsound, br, col, + embed, frame, hr, + image, img, input, + isindex, link, meta, + param, spacer, or wbr element: End tag is not allowed for these elements, since + those content must always be empty. Remove end tag.

Element Content Model Errors

+ + 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. + + + modules="ContentChecker::HTML"> Data character is not allowed in this context. @@ -279,46 +1209,49 @@ context. The document is non-conforming.

Possible causes: -

If the erred element is an inline-level element (such - as 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.

If the erred element is a block-level element (such as - 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.

+ + Non‐white‐space characters are not allowed in + an empty element. + + - There must be a $0 + modules="ContentChecker::HTML"> + There must be a {text} element as a child of this element.

The content model of the element is so defined that it must contain a $0 child element. The document is non-conforming.

For example: -

The head element must contain exactly one - title child element.
The tr - element must contain one or more td or th - child element.

HTML head element: There must be a title child element.
HTML html element: There must be a head child element followed + by a body element.
HTML tr element: There must be + one or more td or th child element.

@@ -333,6 +1266,12 @@ + + There must be at least one + hn element descendant. + + This element is not allowed in this @@ -341,80 +1280,364 @@

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: -

If the erred element is an inline-level element (such - as a or span)

Attribute Errors

- Required attribute $0 + modules="ContentChecker::HTML"> + Required attribute {text} is not specified.

A required attribute is not specified. The document is non-conforming.

Some attribute is defined as required. - For example, any 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.

+ cannot provide full functionality of the element to the user.

+ +

HTML img element: The src attribute must be specified. + Additionally, the alt attribute must be specified + in many cases.
HTML link element: The rel 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. + +

An attribute is specified where it is not allowed. + The document is non-conforming.

+ +

HTML meta element: For HTML meta 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. + + + class="attribute-error" + modules="ContentChecker::XML"> The xml:lang attribute is not allowed in HTML document. - +

The xml:lang attribute is not allowed in HTML document. The document is non-conforming.

The xml:lang attribute in null - namespace for HTML elements is defined as conforming only for - XML document.

Use of the xml:lang attribute is conforming + only in XML documents.

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).

+ + modules="ContentChecker::HTML"> The charset attribute is not allowed in XML document. @@ -430,7 +1653,7 @@ + modules="ContentChecker::HTML"> The lang attribute is not allowed in XML document. @@ -438,16 +1661,22 @@ XML document. The document is non-conforming.

The lang attribute in null - namespace for HTML elements is defined as conforming only for - HTML document.

+ namespace for HTML elements is conforming only in + HTML documents.

To specify natural language information in XML document, use xml:lang attribute instead.

+ + A noscript element cannot be + used in XML document. + + + modules="ContentChecker::HTML"> The xmlns attribute in the null namespace is not allowed in XHTML document. The document is non-conforming. @@ -455,7 +1684,7 @@

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.

@@ -465,23 +1694,455 @@

Attribute Value Errors

+ + 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. + +

The specified character encoding name is not registered to + IANA. Use of registered character encoding name + is a good practice to facilitate interoperability.

+ +

EUC-TW: EUC-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-1: ISO-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-plane1: These names are not registered and obsoleted in favor of + ISO-2022-JP-2004 and + ISO-2022-JP-2004-plane1.
ISO-2022-JP-2003, + ISO-2022-JP-2003-plane1: These names are not registered and corrected to + ISO-2022-JP-2004 and + ISO-2022-JP-2004-plane1.
ISO-2022-JP-2004, + ISO-2022-JP-2004-plane1: These names are not registered. Unfortunately, there is + no registered name for these character encodings.
UTF-8N: UTF-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.

+ + + + + Character encoding name + {value} is a private 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-jp: Use EUC-JP for the Japanese EUC + character encoding.
x-sjis: Use Shift_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 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.

+ + + + + 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 attribute value is not a date or + time. + + + modules="ContentChecker::HTML"> This attribute only allow a limited set of - values and the specified value is not one of them. + values and the specified value {@} 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.

+ +

HTML meta element, http-equiv attribute

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">

+ ... where charset-name is a name of the character encoding + of the document, such as 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.

+ - + Character encoding declaration syntax + <meta http-equiv="Content-Type" content="text/html; charset=charset-name"> + is obsolete. + +

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 character encoding declaration syntax is: +

<meta charset="charset-name">

+ + + + + Attribute value {@} + is not allowed. + + + + There is another pragma + {value}. + + + This identifier has already been assigned to another element. + + The token {value} + appears in the attribute value twice. + + + + The attribute value must not 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. + +

The specified link type cannot be used for the element. + The document is non-conforming.

+ +

Link types are associated with limited set of elements. + They cannot be used with other elements.

+ +

For example, link type bookmark + can be used with a or area element, + while it cannot be used with link element.

+ + + + + Attribute value {@} + is not an allowed value. + + + + The attribute value is not a length + value. + + + + The link type {value} + is non-conforming. + +

The specified link type is non-conforming, and therefore + the document is non-conforming.

+ +

Link type contents: Use link type index.
Link type copyright: Use link type license.
Link type home: Use link type index.
Link type previous: Use link type prev.
Link type start: Use link type first.
Link type toc or top: Use link type index.

+ + + + + 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}. + +

The specified character encoding name is different from + the character encoding of the document. The document + is non‐conforming.

+ + + + + 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. + + + + The contextmenu attribute references + no menu. + + + + the specified value is not a valid as part + of a Refresh pragma. + + + + The attribute value is not an integer or + a string template. + + - This browsing context name is reserved. - + Browsing context name + {@} is reserved. +

The specified browsing context name is reserved. The document is non-conforming.

@@ -494,7 +2155,72 @@ browsing context names _blank, _main, and _replace. However, they are not conforming attribute values.

- + + + + + Namespace name {text} + is reserved and cannot be used for an arbitrary prefix. + + + + Namespace prefix {text} + is reserved and cannot be used for an arbitrary namespace name. + + + + Link type {value} + is proposed but not accepted yet; it should not be + used until it has been accepted. + +

The link type is in the proposed status; it + should not be used until it has been + accepted.

+ +

Warning: The data served to the + conforming checker might be out of date; it might have already + been accepted or rejected. The document might or might not be + conforming depending on the status. See WHATWG Wiki + for the latest information.

+ + + + + 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.

@@ -515,25 +2241,72 @@ th) in the last row. + + This 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>

+ ... since the second row contains only + a cell that spans between first and second rows.

+ + +

URI (or IRI) Warnings

URI (or IRI) Should-level Errors

- Dot-segment (. or - ..) should not occur in an absolute reference. + A dot-segment (. or + ..) occurs in an absolute reference.

Dot-segment (. or ..) should not occur in an absolute reference.

@@ -570,40 +2357,248 @@ - This IRI should explicitly end with - /. + This IRI does not end with + a /. + +

The IRI does not end with a /. If there is an + authority component in an IRI, a / should be present + instead of empty path component.

+ +

For example, http://www.example.com/ + is preferred to http://www.example.com.

+ + + + + A lowercase hexadecimal digit is used + in percent-encoding. + +

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. + +

An unreserved character is percent-encoded in the IRI. + Though it is conforming, it should be in the + decoded (or bare) form.

+ + + + + URI scheme name is in uppercase. + +

The scheme part of the IRI is written in uppercase letter.

+ +

Uppercase scheme names are not required to be processed + correctly.

+ + + + +

+ +

Cache Manifest Errors

+ + + This document is not a cache manifest. + +

The specified document is not a cache manifest. + The document is non-conforming.

+ +

An entity labeled as Internet media type + 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 and MANIFEST).

+ + +

+ +

Stability Information

+ + + This attribute is deprecated. + + + + This element is deprecated. + + + + This element is in the + call for implementation stage. + +

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.

+ + + + + This element is in the last + call for comments stage. + +

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.

+ + + + + This element is documented in a working + draft. + +

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.

+ + + + + This element is not part of any + standard the conformance checker knows. + +

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.

+ + + + + This attribute is in the + call for implementation stage. + +

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.

+ + + + + This attribute is in the last + call for comments stage. + +

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.

+ + + + + This attribute is documented in a working + draft. + +

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.

+ + + This attribute is not part of any + standard the conformance checker knows. + +

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.

+ +

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. -

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.

- - 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 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 link type $0 is not standardized - or registered at the time of the release of the conformance checker; - it is non-conforming unless it has now been registered. + + Link type {value} is not + standardized or registered at the time of the release of the conformance + checker; it is non-conforming unless it now has been + registered.

The rel attribute is defined as a list of link types. Some common link types are defined in the HTML5 specification. @@ -615,28 +2610,622 @@ 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.

+ +

Link types shortcut icon: Link type shortcut is not registered. + Use only icon for linking to so-called favicon.

+ + Conformance checking for event handler attribute + is not supported; it might or might not be conforming. + + + + Conformance checking for media query + is not supported; it might or might not be conforming. + + + + Conformance checking for script + language {text} is not supported; + it might or might not be conforming. + + + + Conformance checking for style + language {text} is not supported; + it might or might not be conforming. + +

- -manakaiCompatMode:quirks;;Quirks Mode -manakaiCompatMode:limited quirks;;Limited Quirks Mode -manakaiCompatMode:no quirks;;No Quirks Mode - -manakaiIsHTML:1;;HTML Document -manakaiIsHTML:0;;XML Document - + + WebHACC (β) + + + + +

+ + +

+ + + + + Input + 入力 + + + + By URL + URL で指定 + + + + By direct input + 直接入力 + + + + More options + 検査オプション + + + + Check an error page + 誤り頁を検査する + + + + Content type + 内容型 + + + + Character encoding + 文字符号化 + + + + As specified + 指定通り + + + + Japanese character encodings + 日本語用文字符号化 + + + + European character encodings + 欧米言語用文字符号化 + + + + Asian character encodings + アジア諸語用文字符号化 + + + + Unicode character encodings + Unicode 系文字符号化 + + + + Document source to check + 検査する文書のソース + + + + Check + 検査 + + + + Setting innerHTML of HTML element + innerHTML に値を設定する HTML 要素 + + + + Information + 情報 + + + + HTTP + Header + HTTP + 頭部 + + + + Parse Errors + 構文誤り + + + + Parse Errors + 構文誤り + + + + Document Source + 文書のソース + + + + Source + ソース + + + + Structure of Tables + 表の構造 + + + + Tables + 表 + + + + Document Tree + 文書木 + + + + Tree + 木 + + + + Document + 文書 + + + + Document Structure + 文書構造 + + + + Structure + 構造 + + + + Reformatted Document Source + 再整形した文書のソース + + + + Reformatted + 再整形 + + + + Structural Errors + 構造的誤り + + + + Struct. Errors + 構造誤り + + + + Transfer Errors + 転送誤り + + + + Trans. Errors + 転送誤り + + + + Result + 結果 + + + + Quirks Mode + 奇癖モード + + + + Limited Quirks Mode + 限定奇癖モード + + + + No Quirks Mode + 無奇癖モード + + + + HTML Document + HTML 文書 + + + + XML Document + XML 文書 + + + + charset parameter + charset 引数 + + + + Input character encoding + 入力に用いた文字符号化 + + + + XML version + XML version + + + + XML encoding + XML encoding + + + + XML standalone + XML standalone + + + + (with BOM) + (BOM つき) + + + + URL + URL + + + + URLs + URL + + + + Container Node + この文書を含む節点 + + + + Table Element + 表要素 + + + + Base URL + 基底 URL + + + + Internet Media Type + インターネット媒体型 + + + + Character Encoding + 文字符号化 + + + + Byte Length + バイト長 + + + + Character Length + 文字長 + + + + (overridden) + (上書き) + + + + (overridden; official type is + {text}) + (上書き, 公式型は + {text}) + + + + (sniffed) + (探知結果) + + + + byte + バイト + + + + bytes + バイト + + + + character + 文字 + + + + characters + 文字 + + + + Line {text} + {text} 行 + + + + column {text} + {text} 列 + + + + Index {text} + 索引 #{text} + + + + Unknown location + 位置不明 + + + + Structure of Table #{text} + 表 #{text} の構造 + + + + Subdocument #{text} + 部分文書 #{text} + + + + Sub #{text} + 部分 #{text} + + + + .. + 〜 + + + + Score + 得点 + + + + Subtotal + 小計 + + + + Total + 合計 + + + + Main document + 主文書 + + + + Subdocuments + 部分文書 + + + + Transfer + 転送 + + + + Encoding + 符号 + + + + Character + 文字 + + + + Syntax + 構文 + + + + Structure + 構造 + + + + Semantics + 意味 + + + + N/A + − + + + + No error found. + 誤りは見つかりませんでした。 + + + + This document has no transfer protocol header error. + 転送プロトコルの頭部に誤りは見つかりませんでした。 + + + + This document has no parse error. + 構文解析中に誤りは見つかりませんでした。 + + + + This document has no structral error. + 構造上の誤りは見つかりませんでした。 + + + + +

Important: This conformance checking service + is under development. The result above might be wrong.

+ + +

重要: この適合性検査サービスは開発中です。 + この結果は間違いかもしれません。

+ + + + + No conformance‐error is + found in this document. + この文書に適合性に関わる誤りは見つかりませんでした。 + + + + This document + is likely non-conforming, but in rare case + it might be conforming. The checker cannot determine whether + this document is in the rare case or not. + この文書はおそらく不適合ですが、 + 稀に適合している場合もあります。適合性検査器はこの文書が稀な場合に該当するかどうか判定できません。 + + + + This document is + non-conforming. + この文書は不適合です。 + + + + The conformance + checker cannot decide whether the document is conforming or + not, since the document contains one or more unsupported + features. The document might or might not be conforming. + 適合性検査器はこの文書が適合するかどうか判定できませんでした。 + この文書は適合性検査器が対応していない機能を使っています。 + この文書は適合しているかもしれませんし、していないかもしれません。 + + + + MUST‐level + error + 必須級の誤り + + + + SHOULD‐level + error + 推奨級の誤り + + + + Warning + 警告 + + + + Information + 情報 + + + + Not + supported + 未対応 + + +

Error Levels

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Level	Conforming?	Description
MUST‐level error	Non‐conforming.	A violation to a hard requirement of the specification. +The document is non‐conforming.
SHOULD‐level error	Non‐conforming, but in some case +conforming.	A violation to a requirement of the specification. +The violation might be legitimize in some case. Otherwise, +the document is non‐conforming.
Warning	Conforming.	A warning is an advice from the conformance checker to avoid +to solve a problem in a confusing or possibly wrong way. +It does not affect to the conformance of the document, and +may sometimes be inappropriate.
Information	Conforming.	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.
Not supported	Unknown.	Some feature that is not supported by the conformance checker +is used in the document.

License of This Document

This library is free software; you can redistribute it +

+ +

This document is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

- + \ No newline at end of file

Description of Errors

Character Encoding Layer Errors

HTML5 Character Encoding Errors

HTML5 Parse Errors in Tokenization Stage

HTML5 Parse Errors in Tree Construction Stage

Element Content Model Errors

Attribute Errors

Attribute Value Errors

Internet Media Type Warnings

Internet Media Type Errors

URI (or IRI) Warnings

URI (or IRI) Should-level Errors

Cache Manifest Errors

Stability Information

Unsupported Messages

Error Levels

License of This Document