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}.{value}
+ is not supported and the explicit character encoding specification is
+ ignored. The result of the conformance checking might be
+ wrong.{text}
@@ -135,10 +222,33 @@
{text} is used. Checking results might be
- wrong.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}, a character encoding declaration specifying
@@ -186,70 +295,105 @@
NULL character
is not allowed.{text} is
not allowed.<$0>
- is not allowed after the end tag </html>.{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
be escaped as &.</ 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.{text} is not allowed.U+000D (CARRIAGE RETURN)
- is not allowed.-- sequence
in a comment.{text}.<>) 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
@@ -594,21 +735,18 @@
SYSTEM, no
system identifier is specified.<?...>) is not allowed in HTML
@@ -661,77 +799,66 @@
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.{text} element cannot be
inserted between head and body
elements.<{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.<{text}>
is not allowed in the body element.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.nobr element cannot be
nested.{text} element is not
allowed in a noscript element in the
@@ -947,21 +1087,18 @@
</{text}>
appers before the noscript element is closed.noscript element is not closed
before the end of file.noscript element in the head
@@ -969,28 +1106,24 @@
<{text}>
is not allowed in a select element.</{text}>
is not allowed in a select element.<{text}>
is not allowed in a table element.</{text}>
is not allowed in a table element.table element, outside of the caption and cells.isindex element is
obsolete.tr
element is missing.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.
details element, only at the
- beginning of the element a lengend element
+ details or fieldset
+ element, only at the beginning of the element a legend element
may be used.head 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.
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.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">.value attribute cannot be
+ specified to an input element whose type
+ is hidden and name is
+ _charset_.xml:lang attribute is not
- allowed in HTML document.xml:lang attribute in HTML
+ document is ignored.The xml:lang attribute is not allowed in
- HTML document. The document is non-conforming.
The xml:lang attribute does not have an effect in
+ HTML document.
Use of the xml:lang attribute is conforming
- only in XML documents.
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.
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.
noscript element cannot be
used in XML document.xml:lang attribute in no namespace
+ is only allowed in HTML document.xml:lang
+ 属性が認められているのは HTML 文書中だけです。xmlns attribute
@@ -1740,6 +1967,28 @@
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 属性が指定されている時だけです。{value}
+ is not ASCII compatible.{value}
+ は ASCII 互換ではありません。{value} is already
+ used for another element.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.
form
+ attribute is not a form element, or no element is
+ found.usemap attribute references
- no image map.usemap
+ attribute is not a map element, or no element is
+ found.contextmenu attribute references
- no menu.contextmenu attribute is not a menu element, or
+ no element is found.value attribute value is longer
+ than the value of the maxlength 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
+ 属性の両方を同じ要素に指定する場合、
+ 両者の値は同じでなければなりません。
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.{value} is not supported by the
- conformance checker.{text} is not defined.
{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.
@@ -2601,6 +3357,563 @@
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.{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.{text} is not supported.
-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.
+| Level | -Conforming? | -Description | -
|---|---|---|
| MUST‐level error | -Non‐conforming. | -A violation to a hard requirement of the specification. -The document is non‐conforming. | -
| SHOULD‐level error | -Non‐conforming, but in some case -conforming. | -A violation to a requirement of the specification. -The violation might be legitimize in some case. Otherwise, -the document is non‐conforming. | -
| Warning | -Conforming. | -A warning is an advice from the conformance checker to avoid -to solve a problem in a confusing or possibly wrong way. -It does not affect to the conformance of the document, and -may sometimes be inappropriate. | -
| Information | -Conforming. | -An informational message just provides an additional information -on the feature used in the document or the status of the retrieval -or so on. -It does not affect to the conformance of the document. | -
| Not supported | -Unknown. | -Some feature that is not supported by the conformance checker -is used in the document. | -