<$0>
- is not allowed after the end tag </html>.The start or end tag of an element appears after the
- html element has been closed. The document is
- non-conforming.
Any content of the document other than comments
- must be put into the html element.
WebHACC + is a conformance checker (or validator) for Web documents, + supporting latest Web standards including + HTML5, + Atom 1.0, + CSS3.
+ +<$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.
{octets}
+ is not an allowed representation of the character
+ {char} — character reference
+ {char:hexref} should be used instead.{octets}.{octets}
+ is illegal.The input stream is encoded in ISO-2022-JP
+ or its variant but is partially broken.
Note that an ISO-2022-JP stream must end in the ASCII
+ state.
& character must
- introduce a reference.An & (U+0026
- AMPERSAND) character which
+
{octets}.{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.
+{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.
+{text}).Use of UTF-8 as the character encoding of the document is encouraged, + though the use of another character encoding is still conforming.
+The conformance checker cannot detect whether the input document + met the requirements on character encoding, since the document + is not inputed as a serialized byte sequence. The document is + not conforming if it is not encoded in an appropriate character + encoding with appropriate labeling.
+The document does not contain a character encoding + declaration. Unless the character encoding is explicitly + specified in lower‐level protocol, e.g. in HTTP, + or is implied by BOM, there must be a character + encoding declaration. The document is non‐conforming.
+ +The long character encoding declaration syntax
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is obsolete. The new syntax is:
+<meta charset="charset-name">
+
+ Note that the encoding declaration in XML
+ declaration has no effect for HTML document.
{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.
{text} (Sniffed because no explicit specification
+ for the character encoding of this document is found in the transfer
+ procotol headers).{text} because no explicit specification
+ for the character encoding of this document is found in the transfer
+ procotol headers.The conformance checker cannot find an appropriate decoder for + the character encoding used to encode characters in the document.
+ +This error is raised if:
+In either case, the result shown by the conformance checker might + contain wrong errors caused by errorneous decoder or might not contain + errors that should be raised if an appropriate decoder is used.
+ + +{text} is not supported.{text} is same as the character encoding specified
+ in the character encoding declaration. This is not an
+ error.{text}, a character encoding declaration specifying
+ a different character encoding is found. The document
+ is reparsed.While parsing a document in a character encoding, + a character encoding declaration which declares the character + encoding of the document as another character encoding is found. + The occurence of this warning itself does not make the document + non‐conforming. However, the failure of the first attempt to + to detect the character encoding might be a result of non‐conformance + of the document.
+ +The document will be reparsed from the beginning. Some error + or warning might be reported again.
+ +These are suggestions to avoid this warning:
+charset parameter in the Content-Type
+ field in the HTTP header, as:
+
+Content-Type: text/html; charset="charset-name"<meta charset="charset-name">)
+ just after <head> start tag.UTF-8.NULL character
+ is not allowed.{text} is
+ not allowed.{text}
+ is found in the input stream.Noncharacter code points are used in the input stream.
+ +Noncharacter code points are reserved for internal processings. + Their use for information interchanges are forbidden.
+ +In addition, they are not allowed in HTML document.
+ +{text}
+ is deprecated.{text}
+ is discouraged.{text}
+ is not the preferred representation of that character.{text}
+ should not be used in many cases.", ', and =."
+ or ' if it contains a ", ', or
+ = character.In an unquoted attribute value, a character "
+ (U+0022 QUOTATION MARK),
+ ' (U+0026
+ APOSTROPHE), or =
+ (U+003D EQUAL SIGN)
+ is contained. These characters are not allowed in unquoted attribute
+ values, since they are used to quote attribute values or to separate
+ attribute name and value.
This error is also raised if one try to use empty attribute
+ value like <foo bar= baz=>;
+ in this example, baz= is
+ treated as an invalid attribute value for the attribute
+ bar, not as another attribute.
& 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 &.
Any & character in URI (or IRI)
+ must be escaped as &.
The & character must
be the first character of a reference:
-
&entity-name;
@@ -70,7 +301,7 @@
</ string is not followed
+</ string is not followed
by a tag name.There is a < (U+003C
LESS-THAN SIGN) character
@@ -90,7 +321,7 @@
< character is not followed
+< character is not followed
by tag name or by a ! character.A < (U+003C
LESS-THAN SIGN) character which is not part
@@ -103,7 +334,7 @@
&#.An & (U+0026
AMPERSAND) character immediately
@@ -114,7 +345,7 @@
The string &# must be the first two characters
of a reference:
-
&#d;
@@ -135,7 +366,7 @@
&#x.The string &#x or &#X which
is not part of any reference appears in the input stream.
@@ -155,7 +386,7 @@
<! is not followed
+<! is not followed
by --.There is a < (U+003C
LESS-THAN SIGN) character
@@ -166,24 +397,26 @@
<!-- (<! immediately followed
+ <!-- (<!
+ immediately followed
by two -s) and must be terminated by
- -->. Strings <! not followed
+ -->.
+ Strings <! not followed
by -- and <!- not followed by
- are not valid open delimiters for comments.CDATA sectionsDOCTYPE
- and comment declarations, are not allowed in HTML documents.DOCTYPE
+ and comment declarations, are not allowed in HTML document.<!<! must be escaped as
- <!.<!.
</ is not followed
+</ is not followed
by tag name.There is a < (U+003C
LESS-THAN SIGN) character
@@ -202,7 +435,14 @@
-- sequence
+{text} is not allowed.U+000D (CARRIAGE RETURN)
+ is not allowed.-- sequence
in a comment.There is a - (U+002D
HYPHEN-MINUS) character
@@ -215,8 +455,8 @@
declaration.
$0.{text}.There are more than one attributes with the same name in a tag. The document is non-conforming.
@@ -224,7 +464,38 @@ Useimg element with animation GIF instead.
/>) cannot be
+<>) is not
+ allowed.</>) is not
+ allowed.The attribute value is not specified after the =
+ (U+003C EQUAL SIGN)
+ character.
When an attribute value is empty, the = character after
+ the attribute name must be specified as:
<foo bar>
Instead, quotation marks can be used to explicitly represent that + the attribute value is empty, as:
+ +<foo bar="">
... or like:
+ +<foo bar=''>
{text} is not allowed./>) cannot be
used for this element.Polytheistic slash (/>) must not be used
for the element. The document is non-conforming.
<script/>The polytheistic slash cannot be used for script
element. Even for an empty script element,
- there must be an explicit end tag </script>.
</script>.
NOTE: Though some user agents interpret
polytheistic slash for script element as the
@@ -256,16 +528,39 @@
to allow polytheistic slash for these elements.
<a/>, <p/>
+<p></p>
+
Note that, unlike in XML, the polytheistic slash has no effect in HTML.
<!DOCTYPE , the
+ document type name must be specified.PUBLIC, no
+ oublic identifier is specified.; character.<?...>) cannot be used.<!DOCTYPE, there
+ must be at least a white space character before the document type
+ name.SYSTEM, no
+ system identifier is specified.<?...>) is not allowed in HTML
+ document.Processing instructions (<?...?>),
including XML declaration (<?xml ...?>)
and XML style sheet PI
@@ -277,7 +572,14 @@
binding property in CSS
- style sheet.
+<style>
+p {
+ binding: url(binding.xbl);
+}
+</style>
+
<?xml?> (XML declaration)<?xml-stylesheet?> (XML style sheet
@@ -285,7 +587,10 @@
link element with rel
attribute set to stylesheet (or,
alternate stylesheet for an alternate style
- sheet).
+<link rel=stylesheet href="path/to/stylesheet.css">
+
<?php?> or
<? ... PHP code ... ?>
(PHP code)PUBLIC.SYSTEM.-->.DOCTYPE is not closed by a
+ > character.>
+ character.$0 element cannot be
- inserted between head and body elements.<{text}> is after the html element
+ is closed.</{text}> is after the html element
+ is closed.<{text}> is
+ not allowed after the body is closed.</{text}> is
+ not allowed after the body is closed.body is closed.<{text}> is
+ not allowed after the frameset is closed.</{text}> is
+ not allowed after the frameset is closed.frame is closed.{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.
DOCTYPE appears after any
- element or data character has been seen.A DOCTYPE appears after any element or data character
- has been seen. The document is non-conforming.
The DOCTYPE must be placed before any
- tag, reference, or data character. Only white space characters
- and comments can be inserted before the DOCTYPE.
<{text}> is
+ not allowed after the html is closed.The start 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.
</{text}> is
+ not allowed after the html is closed.The 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.
html is closed.image element is
+ obsolete.HTML a elements cannot be nested.
The document is non-conforming.
a element.
<$0>
+<{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
@@ -341,7 +724,28 @@
The document is non-conforming.
<head>
+button element cannot be
+ nested.<form> is
+ not allowed in a form element.<{text}> is
+ not allowed in a framset element.</{text}> is
+ not allowed in a frameset element.frameset element.<head>
is not allowed in the head element.There is a start tag <head> in the
<head> element. The document is non-conforming.
<head> can appear in the input stream.
<$0>
+DOCTYPE appears after any
+ element or data character has been seen.A DOCTYPE appears after any element or data character
+ has been seen. The document is non-conforming.
The DOCTYPE must be placed before any
+ tag, reference, or data character. Only white space characters
+ and comments can be inserted before the DOCTYPE.
nobr element cannot be
+ nested.{text} element is not
+ allowed in a noscript element in the
+ head element.</{text}>
+ appers before the noscript element is closed.noscript element is not closed
+ before the end of file.noscript element in the head
+ element.<{text}>
+ is not allowed in a select element.</{text}>
+ is not allowed in a select element.<{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
@@ -365,10 +805,13 @@
a table caption.
table.A data character appears in table. The document
- is non-conforming.
</{text}>
+ is not allowed in a table element.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
@@ -377,7 +820,10 @@
a table caption.
tr
+isindex element is
+ obsolete.tr
element is missing.Start tag of a tr element, which is not
optional, is missing. The document is non-conforming.
DOCTYPE.The document does not start with a DOCTYPE.
The document is non-conforming.
$0 is not
+{text} is not
closed.End tag of an element is not found before, for example, an end tag of another element appears or @@ -425,7 +871,7 @@
canvas element is no longer
defined as empty. There must be an end tag
- </canvas>.</canvas>.
Note that misnesting tags, such as @@ -433,7 +879,7 @@ allowed and they also cause this error.
<html> tag is not
+<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.
@@ -447,11 +893,12 @@
and comments.
The document contains a DOCTYPE declaration
that is different from HTML5 DOCTYPE (i.e.
- <!DOCTYPE HTML>). The document is non-conforming.
<!DOCTYPE HTML>).
+ The document is non‐conforming.
The document might or might not be conformant to some version of HTML. However, conformance to any HTML @@ -460,7 +907,10 @@ HTML document (roughly) as defined in HTML5.
$0 is not
+<{text}> is
+ not allowed here.{text} is not
opened.An end tag appears though no element with the same name has been opened. The document is non-conforming.
@@ -482,12 +932,36 @@DOCTYPE legacy string is
+ used.The DOCTYPE with the DOCTYPE legacy
+ string, i.e.
+ <!DOCTYPE HTML PUBLIC "XSLT-compat">
+ is used.
The DOCTYPE legacy string should not be used for documents
+ generated from XSLT transformation process. It is allowed only to enable
+ to use XSLT style sheets with the HTML output mode, which does not
+ support generation of the DOCTYPE with no PUBLIC
+ identifier. For other purposes, the DOCTYPE legacy
+ string, i.e. PUBLIC "XSLT-compat",
+ is useless and should not be used.
base element with the
+ href attribute specified cannot be placed after
+ any attribute with a URL.base element with the
+ target attribute specified cannot be placed after
+ any element that defines a hyperlink.A data character appears where it is not allowed in this context. The document is non-conforming.
@@ -510,8 +984,17 @@$0
- element as a child of this 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.
td
+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.
{text} in the Atom namespace as a child of this
+ element.link element
+ whose rel attribute is set to alternate as a
+ child of this element.link element
+ whose rel attribute is set to self as a
+ child of this element.hn element descendant.An element appears where it is not allowed. The document is non-conforming.
@@ -563,11 +1061,11 @@ block-level content, any inline-level content must be put in e.g. paragraph element such asp.
For example, an HTML document fragment
- <div><p>Hello!</p> World!</div>
+ <div><p>Hello!</p> World!</div>
is non-conforming, since a word World!
does not belong
to any paragraph. (If not part of any paragraph, what is
it!?) A conforming example would be:
-
+<div><p>Hello!</p> <p>World!</p></div>
area element cannot be used
+ outside of a map element.base
+ element.datatemplate element, only
+ rule elements are allowed.details element, only at the
+ beginning of the element a lengend element
+ may be used.figure element, only at the
+ beginning or only at the end of the element a lengend element
+ may be used.style element without
+ scoped attribute is not allowed in this context.noscript element in the head element.style element with
+ scoped attribute is not allowed in the head
+ element.title
+ element.head element.The character encoding declaration
+ (<meta charset="..."> or
+ <meta http-equiv=Content-Type content="text/html; charset=...">
+ must be the first child element in the head element.
The character encoding declaration have to occur near the beginning + of the document to ensure that Web browsers can be determine the + character encoding of the document.
+ +The title element and other metadata elements must
+ appear after any character encoding declaration is processed.
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 documentIn an XHTML document, the root html
- element must have an xmlns attribute
- whose value is set to
- http://www.w3.org/1999/xhtml.
In XHTML document, the root html
+ element must have an xmlns attribute as:
+
+<html xmlns="http://www.w3.org/1999/xhtml">rss elementThe document is written in some version of RSS.
The conformance checker does not support any version of RSS. Use Atom 1.0 for feed documents.
feed elementThe Atom feed element must be
- in the http://www.w3.org/2004/Atom
- namespace.
http://www.w3.org/2005/Atom
+ namespace as:
+
+<feed xmlns="http://www.w3.org/2005/Atom">
+
The conformance checker does not support Atom 0.3. Use Atom 1.0 for feed documents.
$0
+ruby
+ element.content element.The element is not one of elements allowed + in the latest version of relevant specifications.
+ +The element cannot be used.
+ +event-source elementeventsource
+ element (no hyphen).m elementmark
+ element.{text}
element before this element.There must be an element before another element, but there is not. The document is non-conforming.
@@ -634,12 +1238,15 @@ before anydd element.
rp element must
+ be a parenthesis.$0
+{text}
is not specified.A required attribute is not specified. The document is non-conforming.
@@ -659,7 +1266,24 @@object at least one of
+ data and type attributes must be
+ specified.base element, at least one of
+ href and target attributes must be
+ specified.meta element with the
+ content attribute specified, exactly one of
+ name and http-equiv attributes must be
+ specified.meta element, exactly one of
+ name, http-equiv, and charset
+ attributes must be specified.{local-name} is not allowed for
{element-local-name} element.An attribute is specified where it is not allowed. @@ -673,13 +1297,54 @@
xml:lang attribute is not
- allowed in HTML document.The xml:lang attribute is not allowed in
- HTML document. The document is non-conforming.
ismap attribute may only be
+ used for the image contained in an a element.The attribute is not one of attributes allowed for the element + in the latest version of relevant specifications.
-Use of the xml:lang attribute is conforming
- only in XML documents.
The attribute cannot be used.
+ +align attribute (various HTML elements)border attribute (various HTML elements)autosubmit attribute (menu element)language attribute (script element)<script>
/* JavaScript code */
</script>
type attribute, as follows:
+ <script type="text/javascript">.<script type="text/vbscript">.xml:lang attribute in HTML
+ document is ignored.The xml:lang attribute does not have an effect in
+ HTML document.
The xml:lang attribute is only applicable to XML
+ documents. In HTML document, it is only allowed to ease migration
+ from XML.
To specify natural language information in HTML document,
use lang attribute instead.
charset attribute is not
+charset attribute is not
allowed in XML document.The charset attribute of a
meta element is not allowed in XML document.
@@ -703,24 +1368,17 @@
To specify the character encoding used for serialization, if necessary, use XML declaration instead:
-<?xml version="1.0" encoding="encoding-name"?>
+<?xml version="1.0" encoding="encoding-name"?>
lang attribute is not
- allowed in XML document.The HTML lang attribute is not allowed in
- XML document. The document is non-conforming.
noscript element cannot be
+ used in XML document.The lang attribute in null
- namespace for HTML elements is conforming only in
- HTML documents.
xml:lang attribute in no namespace
+ is only allowed in HTML document.To specify natural language information in XML document,
- use xml:lang attribute instead.
xmlns attribute
+xmlns attribute
in the null namespace is not allowed in
XHTML document. The document is non-conforming.The xmlns attribute in the null
@@ -730,12 +1388,144 @@
static documents.
xml:lang attribute is only allowed
+ when the lang attribute is specified.{@}
+ is not allowed. It must be an empty string or a string
+ {local-name}.{value} is not the preferred name of that
+ character encoding.{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-TWEUC-TW is not registered. Unfortunately, there
+ is no registered name for that character encoding. Use
+ Big5 encoding with character encoding name Big5
+ if it is enough to represent the document.ISO-2022-JP-1ISO-2022-JP-1 is not registered, nevertheless
+ this character encoding name is documented in
+ RFC 2237. Use
+ ISO-2022-JP-2 instead, since that character encoding
+ is a superset of ISO-2022-JP-1.ISO-2022-JP-3, ISO-2022-JP-3-plane1ISO-2022-JP-2004 and
+ ISO-2022-JP-2004-plane1.ISO-2022-JP-2003,
+ ISO-2022-JP-2003-plane1ISO-2022-JP-2004 and
+ ISO-2022-JP-2004-plane1.ISO-2022-JP-2004,
+ ISO-2022-JP-2004-plane1UTF-8NUTF-8N is not registered. Character encoding
+ name UTF-8 represents UTF-8 encoding with or
+ without BOM.WARNING: This error might be raised for + a registered character encoding name, since the character encoding + name database of the conformance checker is not complete yet.
+{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-jpEUC-JP for the Japanese EUC
+ character encoding.x-sjisShift_JIS for standard Shift encoding scheme of
+ JIS coded character set, or Windows-31J
+ for Microsoft standard character set as implemented by
+ Microsoft Windows.{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.
+coords attribute have to
+ contain three (3) numbers (specified:
+ {text}).coords attribute have to
+ contain four (4) numbers (specified:
+ {text}).coords attribute have to
+ contain more than or equal to six (6) numbers (specified:
+ {text}).coords attribute have to
+ contain even number of numbers (specified:
+ {text}).{value}
+ is out of range.{@} is not one
of them.For this attribute only several values are allowed and the @@ -744,12 +1534,12 @@
meta element, http-equiv attributeOnly Default-Style and Refresh
- is allowed.
Only values Default-Style and Refresh
+ are allowed.
Value Content-Type is obsolete; for charset
declaration, the charset attribute can be used as:
-<meta charset="charset-name">
+<meta 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
@@ -763,23 +1553,64 @@
<meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+<meta http-equiv="Content-Type" content="text/html; charset=charset-name">
is obsolete.Old long charset declaration syntax
- <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+
Old long character encoding declaration syntax
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
is in use. The document is non‐conforming.
The new charset declaration syntax is: -
-<meta charset="charset-name">
+ The new character encoding declaration syntax is: +
+<meta charset="charset-name">
{@}
+ is not allowed.{value}.$0
+{value}
+ appears in the attribute value twice.title attribute
+ is empty.The title attribute value of the link
+ element that defines an alternate style sheet is an empty value.
A link element whose rel attribute
+ is alternate stylesheet defines an alternate style sheet.
+ An alternate style sheet must be associated with a name using the
+ title attribute. The name cannot be empty.
# character.id attribute value is
+ different from the name attribute value.{value}
cannot be specified for this element.The specified link type cannot be used for the element. The document is non-conforming.
@@ -792,7 +1623,13 @@ while it cannot be used withlink element.
$0
+{@}
+ is not an allowed value.{value}
is non-conforming.The specified link type is non-conforming, and therefore the document is non-conforming.
@@ -813,7 +1650,45 @@{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.
+{value} matches to the actual character encoding
+ name cannot be checked since the input is not a byte stream.usemap attribute references
+ no image map.id
+ is {value} in the same table.Refresh pragma.template.{@} is reserved.The specified browsing context name is reserved. The document is non-conforming.
@@ -829,12 +1704,13 @@ However, they are not conforming attribute values.{text}
+ is reserved and cannot be used for an arbitrary prefix.{text}
+ is reserved and cannot be used for an arbitrary namespace name.$0
+{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 @@ -848,19 +1724,68 @@ for the latest information.
{value}
+ is not a valid value.id attribute.template
+ attribute is not a template.{value} is reserved.{value} is not
+ allowed in this attribute.NCName.xml:lang attribute
+ is different from the value of the lang attribute.The value of the xml:lang attribute (either the
+ lang attribute in the xml (i.e.
+ http://www.w3.org/XML/1998/namespace) namespace, or
+ the xml:lang attribute in no namespace) for the element has
+ different value than that of the lang attribute in no
+ namespace.
For historical reason, there are two attributes applicable to HTML
+ elements to specify language information of an element: lang
+ and xml:lang. In HTML documents, only lang
+ attribute in no namespace is allowed and take effect; the
+ xml:lang attribute in no namespace is ignored in HTML
+ documents. In XHTML documents, both lang and
+ xml:lang attributes are allowed.
In general, only the lang attribute need to be
+ specified for an element.
If both lang and xml:lang attributes are
+ specified on the same element, their values must be the same value.
colspan attribute
+colspan attribute
results in creating a table column that does not contain
any cell anchored to it.td or
+td or
th) in the last row.rowspan attribute
+rowspan attribute
results in creating a table row that does not contain
any cell anchored to it.The rowspan attribute value of the cell
@@ -869,7 +1794,7 @@
The document is non-conforming.
For example, the table below is non-conforming: -
+<table> <tbody> <tr><td rowspan=2></td></tr> @@ -879,26 +1804,110 @@ a cell that spans between first and second rows.
rowspan attribute
+ results in creating a table row that does not contain
+ any cell anchored to it.e4x.{@}: An obsolete
- subtype is used.{value}, is syntactically not a valid
+ attribute name.{@}: A private
- (x- or x.) subtype is used.{@}: The subtype is
- not registered to IANA.{value} is used.{value} is used.{value} is used.The specified Internet Media Type is registered with its intended + usage as OBSOLETE.
+ +text/ecmascripttext/ecmascript is obsoleted in
+ favor of application/ecmascript. Note that
+ text/javascript would be the better alternative
+ in many cases.text/javascripttext/javascript is obsoleted by
+ IETF with backward incompatible alternate
+ application/javascript for architectural
+ purity. Those who prefer reality to academic
+ purity may ignore this warning.{text} have to
+ be specified for the Internet Media Type
+ {value}.{value} is not
+ allowed for this Internet Media Type.{value} is not encouraged.{value} is not encouraged.{value} is
+ syntactically not a valid subtype value of an Internet Media Type.{value} is
+ syntactically not a valid type.{value}
+ is used. The conformance checker cannot determine whether use of this
+ parameter is valid or not.{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.{value} is not encouraged since it is not
+ part of the IANA registry.{value} is not encouraged since it is not
+ a standardized type.The specified value does not satisfy the syntactical requirements for IRI references. The document is non-conforming.
@@ -913,12 +1922,21 @@{text} is not defined.. or
+. or
..) occurs in an absolute reference.Dot-segment (. or ..) should
not occur in an absolute reference.
/./ character.The hexadecimal digit in percent-encoding string in the IRI is in lowercase. Though the IRI is conforming, it should be in uppercase.
An unreserved character is percent-encoded in the IRI. Though it is conforming, it should be in the decoded (or bare) form.
{value}
+ should be spelt in lowercase.The scheme part of the IRI is written in uppercase letter.
Uppercase scheme names are not required to be processed
@@ -965,10 +2005,145 @@
+ The specified document is not a cache manifest.
The document is non-conforming. A cache manifest must start with a line whose content is
- The element is in the call for implementation stage. Usually, using the element is safe. However, it is a new feature
+ so that it might not be implemented correctly. If it is found that
+ the feature is hard or impossible to implement, the feature
+ might be revised, or in some case it might be dropped. Elements defined by Atom 1.0 (IETF Proposed Standard), and XBL 2.0
+ (W3C Candidate Recommendation) belong to this class. The element is in the last call for comments stage. The element is relatively mature, though the standardization
+ is not done yet. It may be used for experiments. Since it is a new
+ feature, it might not be implemented correctly or at all. If it is
+ found that the feature is hard or impossible to implement, the feature
+ might be revised or might be dropped. Elements defined by Web Forms 2.0 as well as some elements
+ defined by HTML5 belong to this class. The element is documented in a working or editor's draft
+ and not yet completed. The element should not be used for any practical purpose.
+ The feature might be drastically changed later or might be
+ entirely removed. Most of new elements defined by HTML5 belong to this class. The element is not part of any standard or draft the conformance
+ checker is aware of. The element should not be used for any practical purpose unless
+ there is really a standard that defines the element. The attribute is in the call for implementation stage. Usually, using the attribute is safe. However, it is a new feature
+ so that it might not be implemented correctly. If it is found that
+ the feature is hard or impossible to implement, the feature
+ might be revised, or in some case it might be dropped. The attribute is in the last call for comments stage. The attribute is relatively mature, though the standardization
+ is not done yet. It may be used for experiments. Since it is a new
+ feature, it might not be implemented correctly or at all. If it is
+ found that the feature is hard or impossible to implement, the feature
+ might be revised or might be dropped. The attribute is documented in a working or editor's draft
+ and not yet completed. The attribute should not be used for any practical purpose.
+ The feature might be drastically changed later or might be
+ entirely removed. The attribute is not part of any standard or draft the conformance
+ checker is aware of. The attribute should not be used for any practical purpose unless
+ there is really a standard that defines the attribute. The conformant checker does not support the element.
It cannot determine whether the document is conforming or not. No more information is available for this topic. A violation to a hard requirement of the specification.
+ The document is non‐conforming. A violation to a requirement of the specification.
+ The violation might be legitimize in some case. Otherwise,
+ the document is non‐conforming. A warning is an advice from the conformance checker
+ to avoid solving a problem in a confusing or possibly wrong way.
+ It does not affect to the conformance of the document, and
+ may sometimes be inappropriate. An informational message just provides an additional information
+ on the feature used in the document or the status of the retrieval
+ or so on.
+ It does not affect to the conformance of the document. Some feature that is not supported by the conformance checker
+ is used in the document. Copyright
+ Copyright ‐
Wakaba
Media Query Errors
+
+
+
+The specified value has a syntax error as a
+ media query.
+
+Media type
{value} is
+ not supported by the conformance checker.Selectors Errors
+
+
+
+Argument list of the pseudo-class is
+ not closed by a
) character.
+
+Numbers in the argument
+
an+b have to be integers.
+
+Argument
an+b is
+ syntactically incorrect.
+
+Attribute selector is not closed by
+ a
] character.
+
+Argument list of the
:lang
+ selector is not closed by a ) character.
+
+Namespace prefix
{value}
+ is not declared.
+
+Attribute local name is missing.
+
+Attribute matching operator (e.g.
+
=) is missing.
+
+Attribute name is missing.
+
+Attribute namespace wildcard
*
+ is not followed by a | character.
+
+Attribute value is missing.
+
+Class name is missing.
+
+Combinator is missing.
+
+No string is specified in the argument
+ list of the
:-manakai-contains pseudo-class
+ selector.
+
+Language tag argument is missing.
+
+Local name part of the type selector (or
+
* for the universal selector) is missing.
+
+Pseudo-class name is missing.
+
+Pseudo-element name is missing.
+
+Sequence of simple selectors is
+ expected.
+
+Argument list of the
:not selector
+ is not closed by a ) character.
+
+Simple selector is not allowed after a
+ pseudo element.
+
+Pseudo-class
:{value}
+ is not supported by the conformance checker.
+
+Pseudo-element
::{value}
+ is not supported by the conformance checker.CSS Errors
+
+
+
+An
@{text} rule is not
+ allowed here.
+
+The
@{text} rule is
+ syntactically incorrect.
+
+Block is not closed before the end of
+ file.
+
+Component
<{text}> is
+ already specified.
+
+Value
hand is not valid as
+ <'cursor'>.
+
+Specified value is syntactically not a correct
+
<{text}>.
+
+No declaration block is found after a group of
+ selectors.
+
+A
: character is missing after
+ a property name.
+
+Property name is expected.
+
+A
; character is missing at the
+ end of the property.
+
+Priority part of the declaration is syntactically
+ incorrect.
+
+The
@{value} rule is
+ not supported by the conformance checker.
+
+Property
{value} is
+ not supported by the conformance checker.Cache Manifest Errors
-This document is not a cache manifest.
+
+
+This URL is found both in the explicit or
+ fallback entries and in the online whitelist.
+
+The specified URL has different origin from
+ the manifest.
+
+The scheme component of the URL is
+ different from that of the manifest URL. The URL is ignored.
+
+This oppotunistic caching namespace is already
+ specified.
+
+Fallback entry URL is missing.
+
+This document is not a cache manifest.
text/cache-manifest must contain a cache manifest.
CACHE MANIFEST (exactly one space character between
+ CACHE MANIFEST
+ (exactly one space character between
CACHE and MANIFEST).
+
+
+
+This URL is same as the manifest URL.
Stability Information
+
+
+
+This attribute is deprecated.
+
+This element is deprecated.
+
+This element is in the
+ call for implementation stage.
+
+
+This element is in the last
+ call for comments stage.
+
+
+This element is documented in a working
+ draft.
+
+
+This element is not part of any
+ standard the conformance checker knows.
+
+
+This attribute is in the
+ call for implementation stage.
+
+
+This attribute is in the last
+ call for comments stage.
+
+
+This attribute is documented in a working
+ draft.
+
+This attribute is not part of any
+ standard the conformance checker knows.
+ Language Tag Errors
+
+
+
+There is another extension subtag
+
{value}.
+
+Subtag
{value} is
+ syntactically invalid.
+
+It is a good practice to represent ISO 639-1
+ language code
{value} in lowercase.
+
+Langauge tag
mul should not be
+ used.
+
+No semantics is defined for language subtag
+
{value}.
+
+The language subtag
{value}
+ is syntactically invalid.
+
+Langauge tag
und should not be
+ used.
+
+It would be better if a private use language
+ tag (
{value}) is not used.
+
+Private use subtag
{value}
+ is syntactically invalid.
+
+It is a good practice to represent ISO 3166
+ country code
{value} in uppercase.
+
+No semantics is defined for region subtag
+
{value}.
+
+Use of private use country code
+
{value} is not allowed.RDF/XML Errors
+
+
+
+The namespace URI of an element that
+ represents an RDF concept must be
+
http://www.w3.org/1999/02/22-rdf-syntax-ns#.
+
+The specified value is already used as an
+ ID.
+
+Both unqualified attribute and namespace‐qualified
+ RDF attribute are specified, which is not allowed.
+
+An invalid value is specified to
+ the
parseType attribute.
+
+There is another element, such that
+ this element is not allowed.
+
+Unqualified attribute is not allowed.
+
RDF attribute should be
+ namespace‐qualified.
Unsupported Messages
-Conformance checking for element
+
-Conformance checking for element
{local-name} is not supported; it might or
might not be conforming.Conformance checking for attribute
+
-Conformance checking for attribute
@@ -999,7 +2341,7 @@
It cannot determine whether the document is conforming or not.
{local-name} of element
{element-local-name} is not supported;
it might or might not be conforming.Link type
$0 is not
+
-Link type
@@ -1021,71 +2363,278 @@
{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.Conformance checking for event handler attribute
+
-Conformance checking for event handler attribute
is not supported; it might or might not be conforming.
Conformance checking for media query
+
-Conformance checking for media query
is not supported; it might or might not be conforming.
Conformance checking for script
- language
$0 is not supported;
+
+
+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
$0 is not supported;
+
+Conformance checking for style
+ language
{text} is not supported;
it might or might not be conforming.
+
+Conformance checking for an Atom
+
content element with type
+ {text} is not supported.
+
-No more information is available.
+ 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.
-
-
-
-Not supported
-Unknown.
-Some feature that is not supported by the conformance checker
-is used in the document.
-
+
+MUST‐level
+ error
+
+
+SHOULD‐level
+ error
+
+
+Warning
+
+
+Information
+ Not
+ supported
+ License of This Document
-<w@suika.fam.cx>.