An illegal octet in the input stream.

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.

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

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.

The & character must be escaped as &.

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

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

Named entity reference

&entity-name;

where entity-name is the name of the character entity to be referenced.

Numeric character reference

&#d;

where d is the decimal representation of the code position of the character to be referenced.

Hexadecimal character reference

&#xh;

where h is the hexadecimal representation of the code position of the character to be referenced.

To represent & as a data character, use named entity reference:

&

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:

</

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:

<

The decimal representation of the code position of a character must be specified after &#.

An & (U+0026 AMPERSAND) character immediately followed by a # (U+0023 NUMBER SIGN) character which is not part of any reference appears in the input stream. The document is non-conforming.

The string &# must be the first two characters of a reference:

Numeric character reference

&#d;

where d is the decimal representation of the code point of the character to be referenced.

Hexadecimal character reference

&#xh;

where h is the hexadecimal representation of the code point of the character to be referenced.

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

&#

The hexadecimal representation of the code position of a character must be specified after &#x.

The string &#x or &#X which is not part of any reference appears in the input stream. The document is non-conforming.

The string &#x or &#X must be the first three characters of a hexadecimal reference:

&#xh;

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

&#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 <!-- (<! 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.

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.

There is a < (U+003C LESS-THAN SIGN) character immediately followed by a / (U+005F SOLIDUS) character, which is not part of any end tag, in the input stream. The document is non-conforming.

The </ sequence not followed by a tag name is parsed as an opening of bogus comment.

The </ sequence as string data must be escaped as:

</

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 name {text}.

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

The motion attribute is not part of the HTML standard. Use img element with animation GIF instead.

Empty start tag (<>) is not allowed.

Empty end tag (</>) is not allowed.

End tag cannot have attributes.

Character reference to {text} is not allowed.

Polytheistic slash (/>) cannot be used for this element.

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

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

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

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.

A start tag appears after the head element is closed but before the body element is opened. The document is non-conforming.

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, 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 td or th element to form a part of the table, or caption element to create a table caption.

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 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 td or th element to form a part of the table, or caption element to create a table caption.

The isindex element is obsolete.

Start tag of tr element is missing.

Start tag of a tr element, which is not optional, is missing. The document is non-conforming.

In a table section, a <tr> start tag must occur before any <td> or <th> start tag. Though the HTML5 parser implies the <tr> start tag before these start tags, it must be explicitly specified.

This document does not start with a DOCTYPE.

The document does not start with a DOCTYPE. The document is non-conforming.

An HTML document must start by a DOCTYPE:

<!DOCTYPE HTML>

Only white space characters and comments are allowed before the DOCTYPE. XML declaration is not allowed in HTML document.

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.

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.

The document might or might not be conformant to some version of HTML. However, conformance to any HTML specification other than HTML5 provides for no practical convenience, since Web borwsers will parse any HTML document (roughly) as defined in HTML5.

Start tag <{text}> is not allowed here.

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.

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

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.

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

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.

There must be a td or th element as a child of this element.

The tr element must contain at least one td or th child element. The document is non-conforming.

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.

An element appears where it is not allowed. The document is non-conforming.

Possible causes:

If the element with the error is an inline-level element, such as a, progress, or img

An inline-level element cannot be a child of certain sectioning elements such as body, section, and blockquote.

Any inline-level content must be put in e.g. paragraph element such as p.

If it is a block-level elements, such as aside, div, hn, p, or section

If the parent element is div, li, td, or th

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

For example, an HTML document fragment <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>

If the parent element does not allow block-level elements as content

The element is not allowed to be inserted here. For example, a div element cannot be a child of an h1 element.

If the element with the error is a noscript element

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

If the element with the error is blink, center, or marquee element

These elements are not part of the HTML standard. Use CSS for styling control.

button, datalist, fieldset, form, input, label, optgroup, option, output, rb, rp, rt, ruby, textarea, or textarea element

These elements are intentionally not supported by the conformance checker yet.

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 must be the first element in the head element.

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.

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.

html element in an XHTML document

In XHTML document, the root html element must have an xmlns attribute as:

<html xmlns="http://www.w3.org/1999/xhtml">

rss element

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.

feed element

The Atom feed element must be in the 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.

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.

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.

There must be an element before another element, but there is not. The document is non-conforming.

For example, there must be a dt element before any dd element.

The content of a rp element must be a parenthesis.

Required attribute {text} is not specified.

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

Some attribute is defined as required. Without required attributes specified, user agents 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.

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.

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

The charset attribute is not allowed in XML document.

The charset attribute of a meta element is not allowed in XML document. The document is non-conforming.

To specify the character encoding used for serialization, if necessary, use XML declaration instead:

<?xml version="1.0" encoding="encoding-name"?>

The lang attribute is not allowed in XML document.

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

The lang attribute in null 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.

The xmlns attribute in the null namespace is not allowed in XHTML document. The document is non-conforming.

The xmlns attribute in the null namespace is not allowed in XHTML document.

This error should not occur in conformance-checking of static documents.

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.

This attribute only allow a limited set of 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.

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.

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

Names of browsing contexts starting with _ (U+005F LOW LINE) are reserved so that it must not be used.

Old version of HTML, non-HTML markup languages, and Web browsers define or implements special reserved 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.

The specified value is not a legal XML Namespaces 1.0 NCName.

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.

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.

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>

This row has no anchored cell.

This rowspan attribute results in creating a table row that does not contain any cell anchored to it.

The specified value is not a valid value as a multipart boundary.

The specified value is not a valid value for the attribute e4x.

The specified value, {value}, is syntactically not a valid attribute name.

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.

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.

The specified value is syntactically not an IRI.

The specified value is syntactically not an IRI reference.

The specified value does not satisfy the syntactical requirements for IRI references. The document is non-conforming.

Possible causes:

• The string might contain one or more white space characters. Especially, the (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.

URL host address format {value} is not supported by the conformance checker.

Default port number should be omitted.

A dot-segment (. or ..) occurs in an absolute reference.

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

In relative references, dot-segments are used to represent the current (.) or the parent (..) hierarchy of the path. Though they are also allowed in absolute references, it should be resolved to the canonical form before it has been published.

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.

The host component of the URL is too long.

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.

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.

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

The host {value} should be spelt in lowercase.

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

The specified value has a syntax error as a media query.

Media type {value} is not supported by the conformance checker.

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.

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.

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.

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

This URL is same as the manifest URL.

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.

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.

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.

Conformance checking for element {local-name} is not supported; it might or might not be conforming.

The conformant checker does not support the element. It cannot determine whether the document is conforming or not.

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 attribute. It cannot determine whether the document is conforming or 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 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. Additional link types can be registered to the WHATWG Wiki. use of any other link type is non-conforming.

The specified link type is not part of the standard or registry when the database used by the conformance cheker is created. 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 an addr-spec 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.

Conformance checking for an Atom content element with type {text} is not supported.

これ以上の詳しい情報はありません。

これについての詳しい情報はありません。