WebHACC + is a conformance checker (or validator) for Web documents, + supporting latest Web standards including + HTML5, + Atom 1.0, + CSS3.
+ + +WebHACC + は、 Web 文書のための適合性検査器 (妥当性検証器) です。 + HTML5、 + Atom 1.0、 + CSS3 + などの最新の Web 標準に対応しています。
+ + + + +{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.
{octets}.$0
+{value}
+ is not supported and the explicit character encoding specification is
+ ignored. The result of the conformance checking might be
+ wrong.{text}
is not allowed for HTML document.The character encoding used for the document is not allowed @@ -23,9 +119,9 @@
$0
+{text}
should not be used for HTML document.The character encoding used for the document is not recommended @@ -34,19 +130,20 @@
{text}).Use of UTF-8 as the character encoding of the document is encouraged, - though the use of another character encoding is conforming.
+ 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 @@ -56,8 +153,8 @@
$0
+ character encoding {text}
is not a superset of ASCII.The document is not labeled with character encoding name @@ -107,11 +204,72 @@
{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.$0, a character encoding declaration specifying
- character encoding as $1 is found. The document
+ {text}, a character encoding declaration specifying
+ a different character encoding is found. The document
is reparsed.While parsing a document in a character encoding, @@ -119,7 +277,7 @@ 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 the result of non‐conformance + 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 @@ -139,42 +297,106 @@
<$0>
- is not allowed after the end tag </html>.NULL character
+ is not allowed.{text} is
+ not allowed.{text}
+ is found in the input stream.The start or end tag of an element appears after the
- html element has been closed. The document is
- non-conforming.
Noncharacter code points are used in the input stream.
+ +Noncharacter code points are reserved for internal processings. + Their use for information interchanges are forbidden.
-Any content of the document other than comments
- must be put into the html element.
In addition, they are not allowed in HTML document.
+<$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.
{text} is not
+ a Unicode character.Any content of the document other than head
- contents and comments must be put into the body
- element.
{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
- introduce a reference.&.
An & character which
is not part of any reference appears in the input stream.
@@ -209,7 +431,7 @@
</ string is not followed
by a tag name.< character is not followed
by tag name or by a ! character.&#.&#x.<! is not followed
by --.</ is not followed
by tag name.-- sequence
in a comment.$0.{text}.
There are more than one attributes with the same name in a tag. The document is non-conforming.
@@ -388,8 +610,60 @@<>) 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.<!DOCTYPE , the
+ document type name must be specified.PUBLIC, no
+ oublic identifier is specified.; character.<!DOCTYPE, there
+ must be at least a white space character before the document type
+ name.SYSTEM, no
+ system identifier is specified.<?...>) cannot be used.<?...>) is not allowed in HTML
+ document.
Processing instructions (<?...?>),
including XML declaration (<?xml ...?>)
@@ -487,15 +798,136 @@
PUBLIC.SYSTEM.-->.DOCTYPE is not closed by a
+ > character.>
+ character.<{text}> is after the html element
+ is closed.html 要素が閉じられた後に開始タグ
+ <{text}> があります。</{text}> is after the html element
+ is closed.html 要素が閉じられた後に終了タグ
+ </{text}> があります。<{text}> is
+ not allowed after the body is closed.</{text}> is
+ not allowed after the body is closed.body is closed.<{text}> is
+ not allowed after the frameset is closed.</{text}> is
+ not allowed after the frameset is closed.frame is closed.$0 element cannot be
- inserted between head and body elements.{text} element cannot be
+ inserted between head and body
+ elements.A start tag appears after the head element is closed
but before the body element is opened.
@@ -503,22 +935,50 @@
DOCTYPE appears after any
- element or data character has been seen.<{text}> is
+ not allowed after the html is closed.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 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.
@@ -530,8 +990,8 @@
<$0>
+ modules="HTML::Parser">
+ <{text}>
is not allowed in the body element.The start or end tag of an element, which @@ -541,8 +1001,50 @@
button element cannot be
+ nested.<form> is
+ not allowed in a form element.<{text}> is
+ not allowed in a framset element.</{text}> is
+ not allowed in a frameset element.frameset element.<head>
is not allowed in the head element.DOCTYPE appears after any
+ element or data character has been seen.A DOCTYPE appears after any element or data character
+ has been seen. The document is non-conforming.
The DOCTYPE must be placed before any
+ tag, reference, or data character. Only white space characters
+ and comments can be inserted before the DOCTYPE.
nobr element cannot be
+ nested.{text} element is not
+ allowed in a noscript element in the
+ head element.</{text}>
+ appers before the noscript element is closed.noscript element is not closed
+ before the end of file.noscript element in the head
+ element.<{text}>
+ is not allowed in a select element.</{text}>
+ is not allowed in a select element.<$0>
+ modules="HTML::Parser">
+ <{text}>
is not allowed in a table element.The start or end tag of an element, which @@ -573,13 +1141,19 @@
table.</{text}>
+ is not allowed in a table element.table element, outside of the caption and cells.A data character appears in table. The document
- is non-conforming.
A non‐white‐space character appears in table.
+ The document is non-conforming.
In table, only table related elements
are allowed; any other element and data character must be contained in
@@ -589,8 +1163,14 @@
isindex element is
+ obsolete.tr
element is missing.DOCTYPE.$0 is not
+ class="parse-error"
+ modules="HTML::Parser">
+ {text} is not
closed.End tag of an element is not found before, for example, @@ -657,7 +1239,8 @@
<html> tag is not
the first start tag.<{text}> is
+ not allowed here.$0 is not
+ class="parse-error"
+ modules="HTML::Parser">
+ {text} is not
opened.An end tag appears though no element with the same name @@ -718,13 +1310,50 @@
DOCTYPE legacy string is
+ used.DOCTYPE
+ 遺物文字列が使われています。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
+ not 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.$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.
@@ -783,8 +1430,35 @@
{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.area element cannot be used
+ outside of a map element.base
+ element.datatemplate element, only
+ rule elements are allowed.details or fieldset
+ element, only at the beginning of the element a legend 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.head
+ 要素の最初の子要素ではありません。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 @@ -881,9 +1663,92 @@
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.label element.$0
+ modules="ContentChecker::HTML">
+ {text}
element before this element.There must be an element before another element, but there @@ -894,14 +1759,20 @@
rp element must
+ be a parenthesis.$0
+ modules="ContentChecker::HTML">
+ {text}
is not specified.A required attribute is not specified. The document @@ -923,7 +1794,37 @@
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.xml:lang attribute is not
- allowed in HTML document.ismap attribute may only be
+ used for the image contained in an a element.The xml:lang attribute is not allowed in
- HTML document. The document is non-conforming.
The attribute is not one of attributes allowed for the element + in the latest version of relevant specifications.
+ +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">.Use of the xml:lang attribute is conforming
- only in XML documents.
value attribute cannot be
+ specified to an input element whose type
+ is hidden and name is
+ _charset_.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
allowed in XML document.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.
noscript element cannot be
+ used in XML document.To specify natural language information in XML document,
- use xml:lang attribute instead.
xml:lang attribute in no namespace
+ is only allowed in HTML document.xml:lang
+ 属性が認められているのは HTML 文書中だけです。xmlns attribute
in the null namespace is not allowed in
XHTML document. The document is non-conforming.input element whose type is
+ {text}.value attribute cannot be
+ specified to a li element whose parent element is
+ not an ol element.xml:lang attribute is only allowed
+ when the lang attribute is specified.xml:lang 属性を指定できるのは
+ lang 属性が指定されている時だけです。$0
- is not registered.{@}
+ is not allowed. It must be an empty string or a string
+ {local-name}.{value}
+ is not ASCII compatible.{value}
+ は ASCII 互換ではありません。{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 @@ -1063,10 +2074,10 @@
$0 is a private
- 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 @@ -1085,10 +2096,10 @@
{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. @@ -1098,8 +2109,121 @@
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.{@}
+ is not allowed.{value} is already
+ used for another element.{value}.{value}
+ appears in the attribute value twice.alt attribute value is
+ empty.alt attribute value is
+ empty.alt 属性値が空です。The value of the alt attribute of an area
+ element is an empty value.
In general, the alt attribute value cannot be empty.
+ It must provide an alternative text for the hyperlink represented by
+ the area element. The alternative text is to be used
+ when the Web browser cannot display the image, or is configured not
+ to display images.
As an exception, the alt attribute may be left blank
+ if the same image map (i.e. the ancestor map element)
+ contains another area element whose href
+ attribute references the same resource as the href
+ attribute of the area element in question, and the other
+ area element has an alt attribute with
+ non‐empty value.
title attribute
+ is empty.title 属性の値が空です。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.$0
+ modules="ContentChecker::HTML">
+ {value}
cannot be specified for this element.The specified link type cannot be used for the element. @@ -1169,9 +2414,22 @@
{@}
+ is not an allowed value.$0
+ modules="ContentChecker::HTML">
+ {value}
is non-conforming.The specified link type is non-conforming, and therefore @@ -1194,11 +2452,17 @@
$1
- is different from document character encoding
- $0.{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 @@ -1206,6 +2470,69 @@
{value} matches to the actual character encoding
+ name cannot be checked since the input is not a byte stream.form
+ attribute is not a form element, or no element is
+ found.usemap
+ attribute is not a map element, or no element is
+ found.contextmenu attribute is not a menu element, or
+ no element is found.id
+ is {value} in the same table.Refresh pragma.template.{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.{value}
+ is not a valid value.id attribute.template
+ attribute is not a template.value attribute value is longer
+ than the value of the maxlength attribute.{value} is reserved.{value} is not
+ allowed in this attribute.NCName.xml:lang attribute
+ is different from the value of the lang attribute.xml:lang 属性の値が lang
+ 属性の値と異なります。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.
xml:lang 属性 (xml (=
+ http://www.w3.org/XML/1998/namespace) 名前空間の
+ lang 属性や名前空間に属さない
+ xml:lang 属性) の値が同じ要素の名前空間に属さない
+ lang 属性の値と異なっています。
歴史的な理由により、 HTML 要素の言語指定のための属性は
+ lang と xml:lang の2つがあります。 HTML
+ 文書では名前空間に属さない lang 属性だけが認められており、
+ かつ効力があります。名前空間に属さない
+ xml:lang 属性は HTML 文書では無視されます。 XHTML 文書では
+ lang 属性も xml:lang 属性も認められています。
通常、要素の言語情報は lang
+ 属性だけを使って指定すれば十分です。
lang 属性と xml:lang
+ 属性の両方を同じ要素に指定する場合、
+ 両者の値は同じでなければなりません。
colspan attribute
results in creating a table column that does not contain
any cell anchored to it.td or
@@ -1289,54 +2732,180 @@
rowspan attribute
+ results in creating a table row that does not contain
+ any cell anchored to it.e4x.{value}, is syntactically not a valid
+ attribute name.{value} is used.{value} is used.{@}: An obsolete
- subtype is used.The specified Internet Media Type is registered with status - of OBSOLETE.
+ modules="IMTChecker"> +{value} is used.{value} が使われています。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 better alternative
- for many cases.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. Realist may ignore this warning.{text} have to
+ be specified for the Internet Media Type
+ {value}.{value} is not
+ allowed for this Internet Media Type.{@}: A private
- (x- or x.) subtype is used.{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.{@}: The subtype is
- not registered to IANA.{value} is not encouraged since it is not
+ part of the IANA registry.{value} is not encouraged since it is not
+ a standardized type.{text} is not defined.. or
..) occurs in an absolute reference././ character.The IRI does not end with a /. If there is an
authority component in an IRI, a / should be present
@@ -1389,8 +2987,25 @@
{value}
+ should be spelt in lowercase.The scheme part of the IRI is written in uppercase letter.
@@ -1433,10 +3072,277 @@{value} is
+ not supported by the conformance checker.) character.an+b have to be integers.an+b is
+ syntactically incorrect.] character.:lang
+ selector is not closed by a ) character.{value}
+ is not declared.=) is missing.*
+ is not followed by a | character.:-manakai-contains pseudo-class
+ selector.* for the universal selector) is missing.:not selector
+ is not closed by a ) character.:{value}
+ is not supported by the conformance checker.::{value}
+ is not supported by the conformance checker.@{text} rule is not
+ allowed here.@{text} rule is
+ syntactically incorrect.<{text}> is
+ already specified.hand is not valid as
+ <'cursor'>.<{text}>.: character is missing after
+ a property name.; character is missing at the
+ end of the property.@{value} rule is
+ not supported by the conformance checker.{value} is
+ not supported by the conformance checker.The specified document is not a cache manifest.
@@ -1451,13 +3357,1014 @@
CACHE and MANIFEST).
(?{text}...) is not implemented
+ by Perl.(?#... is
+ not terminated by ).(?p{...}) is
+ obsolete.(?p{}) is obsolete. It was deprecated in
+ Perl 5.8 and is no longer supported in Perl 5.10.
You can use (??{...}) instead.
(?{...})
+ is not terminated or {...} is not
+ balanced.(?(condition)...|...|...)
+ contains too many branches.(?({text} is used.(?... is
+ incomplete.(?{text})
+ in a regular expression has no effect.(?{text}...) is used.(... sequence
+ is not terminated by ).) is found.{n,m}
+ cannot be n > m.{text} matches
+ the empty string too many times.[...
+ is not terminated by ].\{text} sequence
+ is not followed by {...}.\{text}{...
+ is not terminated by }.\ character is not followed by
+ another character,\{text}
+ is used.\{text}
+ is used in a character class.[:{text}:] is used.[{text}...{text}] is used
+ outside of character classes.\{text}{}
+ is empty.{text}.{text}
+ is invalid., character or a ) character., character or a ) character.unsigned
+ keyword is not short or long.unsigned の後の字句が
+ short か long ではありません。, character or a ] character.Variadic extended attribute is seen.{text} is
+ specified for an attribute that is not read-only.{text}
+ is specified for an attribute whose type is not an interface.} character is expected.} character is expected.{text}
+ is not followed by a { character.Definition is
+ expected).Definition (optionally preceded by an extended attribute list)
+ is expected.{text} is
+ not specified.[ character.{value}
+ is outside of the range of the type for the constant,
+ {text}.{value}, is different from the type of the constant,
+ {text}.{text}
+ is already specified for another operation in the same interface.{value}
+ specified by extended attribute {text} is already
+ used for an interface.{text} is
+ already used.{text} is
+ already used.{text}
+ is already specified.{text} is
+ not defined in the fragment.{text} is
+ not defined in the fragment.in keyword for an argument is
+ found.( character for an argument
+ list is found.raises (or getraises
+ or setraises) keyword is not followed by a (
+ character.sequence<> type is not
+ terminated by a > character.sequence is not followed
+ by a < character.sequence<>.{text}.{text} cannot be
+ used in valuetype.}; sequences.{value} is
+ not defined in the interface specified for the attribute to which
+ extended attribute {text} is set.:: token is not followed by
+ an identifier or a DOMString keyword.{text} is not
+ defined.typedef of name DOMString
+ is ignored.{text} is used.valuetype definition does
+ not define DOMString as
+ sequence<unsigned short>.valuetype of name
+ DOMString is ignored.{text}, since its signature different from
+ the expected one.{text} is not allowed.{text}
+ is not applicable for an attribute whose type is not
+ DOMString.{text} is not specified.{text} is not allowed.{value} is
+ not an allowed value for extended attribute
+ {text}.{text}
+ is not applicable to this kind of object.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.
+{value}.{value}
+ is placed after subtag {text}.{value} is not
+ defined when the conformance checker is written.{value} is not in the preferred form, i.e. in
+ lowercase.{value} is deprecated.{text} is not allowed in the combination with this
+ language (and extended language) subtag(s).{text} is not registered.{value} is
+ not in the preferred case combination.{value} is deprecated.{value} is
+ not a combination of RFC 4646 subtags and is not a registered grandfathered
+ tag.{value} is
+ syntactically invalid.{value} in lowercase.{value} is deprecated.{value}
+ is not registered.mul should not be
+ used.{value}.{value}
+ is a private use code.{value}
+ is syntactically invalid.und should not be
+ used.{value}) is not used.{value}
+ is used.{value} is not
+ represented in the preferred case format.{value}
+ is syntactically invalid.{value} is
+ not in the preferred case combination.{value} is deprecated.{value} in uppercase.{value} is deprecated.{value}.{value}
+ is not registered.{value} is not allowed.{value} is
+ not in the preferred form, i.e. titlecase.{value} is deprecated.{value}
+ is not registered.{value}
+ is a private use code.{value}
+ should be suppressed when the language subtag is
+ {text}.{value} is
+ not in the preferred form, i.e. lowercase.{text} might
+ not be meaningful when it is used in combination with
+ {value}.{value} is deprecated.{value}
+ is specified twice.{value}
+ is not registered.{value}
+ cannot be used in this context.http://www.w3.org/1999/02/22-rdf-syntax-ns#.parseType attribute.{local-name} is not supported; it might or
might not be conforming.{local-name} of element
{element-local-name} is not supported;
@@ -1479,9 +4386,9 @@
$0 is not
+{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.addr-spec
+ is not supported; it might or might not be conforming.$0 is not supported;
+ language {text} is not supported;
it might or might not be conforming.$0 is not supported;
+ language {text} is not supported;
it might or might not be conforming.content element with type
+ {text} is not supported.No more information is available for this topic.
+これについての詳しい情報はありません。
+| 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. | -
innerHTML of HTML elementinnerHTML に値を設定する HTML 要素charset parametercharset 引数versionversionencodingencodingstandalonestandaloneBOM)BOM つき){text}){text})Important: This conformance checking service + is under development. The result above might be wrong.
+重要: この適合性検査サービスは開発中です。 + この結果は間違いかもしれません。
+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
<w@suika.fam.cx>.