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 標準に対応しています。
+ + + + +{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-nameExistence 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.{text} is used. Checking results might be
+ wrong.{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.<$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.
", ', and =."
+ or ' if it contains a ", ', or
+ = character.& character must
- introduce a reference.&.
An & (U+0026
- AMPERSAND) character which
+
An & character which
is not part of any reference appears in the input stream.
- The document is non-conforming.
Any & character in URI (or IRI)
+ must be escaped as &.
The & character must
be the first character of a reference:
-
&entity-name;</ string is not followed
+ by a tag name.There is a < (U+003C
+ LESS-THAN SIGN) character
+ immediately followed by a / (U+005F
+ SOLIDUS) character, which is not part
+ of any end tag, in the input stream. The document
+ is non-conforming.
The </ sequence immediately followed
+ by an EOF is
+ interpreted as a string data of </.
The </ sequence as string data must
+ be escaped as:
+
</< character is not followed
by tag name or by a ! character.&#.The string &# must be the first two characters
of a reference:
-
&#d;&#x.<! is not followed
+ by --.There is a < (U+003C
+ LESS-THAN SIGN) character
+ followed by a ! (U+0021
+ EXCLAMATION MARK) character,
+ which is not followed by a -- or
+ !DOCTYPE. The document is non-conforming.
<!-- (<!
+ immediately followed
+ by two -s) and must be terminated by
+ -->.
+ Strings <! not followed
+ by -- and <!- not followed by
+ - are not valid open delimiters for comments.CDATA sectionsDOCTYPE
+ and comment declarations, are not allowed in HTML document.<!<! must be escaped as
+ <!.</ is not followed
+ by tag name.There is a < (U+003C
+ LESS-THAN SIGN) character
+ immediately followed by a / (U+005F
+ SOLIDUS) character, which is not part
+ of any end tag, in the input stream. The document
+ is non-conforming.
The </ sequence not followed by a
+ tag name is parsed as an opening of bogus comment.
The </ sequence as string data must
+ be escaped as:
+
</{text} is not allowed.U+000D (CARRIAGE RETURN)
+ is not allowed.-- sequence
in a comment.$0.{text}.
There are more than one attributes with the same name in a tag. The document is non-conforming.
@@ -164,64 +531,306 @@<>) is not
+ allowed.</>) is not
+ allowed.{text} is not allowed./>) cannot be
+ class="tokenize-error"
+ modules="HTML::Parser">
+ />) cannot be
used for this element.Void element syntax (/>) must not be used
+
Polytheistic slash (/>) must not be used
for the element. The document is non-conforming.
The void element syntax can only be +
The polytheistic slash can only be
used for base, link, meta,
hr, br, img,
embed, param, area,
col, and input elements.
Note that, unlike in XML, the void element syntax has +
<script/>The polytheistic slash cannot be used for script
+ element. Even for an empty script element,
+ there must be an explicit end tag
+ </script>.
NOTE: Though some user agents interpret
+ polytheistic slash for script element as the
+ closing of the element, such usage is not allowed under
+ the current standard.
<basefont/>, <bgsound/>,
+ <frame/>, <keygen/>,
+ <spacer/>, <wbr/><command/>, <event-source/>,
+ <nest/>, or <source/><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.<!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 ...?>)
and XML style sheet PI
- (<xml-stylesheet ...?>), are not allowed
+ (<?xml-stylesheet ...?>), are not allowed
in the HTML syntax. The document is non-conforming.
If it is necessary to embed a processing instruction - in the HTML document, you must use the XML syntax instead.
- -In the HTML syntax, XML declaration is not necessary.
- -Instead of XML style sheet,
- PIs, you must
- use the HTML link element whose rel
- attribute is set to stylesheet (or
- alternate stylesheet for an aleternate style sheet).
<?xbl?> (XBL Association)binding property in CSS
+ style sheet as:
+ <style>
+p {
+ binding: url(binding.xbl);
+}
+</style><?xml?> (XML declaration)<?xml-stylesheet?> (XML style sheet
+ PI)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)ProcessingInstruction node by scripting.Web browsers will parse processing instructions as bogus comments. Some legacy Web browsers, such as IE:mac and - some mobile browsers, will display processing instructions + some mobile Web browsers, will display processing instructions as string.
PUBLIC.SYSTEM.-->.DOCTYPE is not closed by a
+ > character.>
+ character.<{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.
@@ -229,22 +838,37 @@
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.</{text}> is
+ not allowed after the html is closed.html is closed.image element is
+ obsolete.HTML a elements cannot be nested.
@@ -256,9 +880,10 @@
<$0>
- is not allowed in a body element.<{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
@@ -267,9 +892,59 @@
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>
+ class="parse-error"
+ modules="HTML::Parser">
+ <head>
is not allowed in the head element.There is a start tag <head> in the
@@ -281,9 +956,85 @@
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>
+ class="parse-error"
+ modules="HTML::Parser">
+ <{text}>
is not allowed in a table element.The start or end tag of an element, which @@ -299,13 +1050,21 @@
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
@@ -315,8 +1074,16 @@
isindex element is
+ obsolete.tr
element is missing.DOCTYPE.Only white space characters and comments are allowed
- before the DOCTYPE.
DOCTYPE. XML declaration is not
+ allowed in HTML document.
$0 is not
+ class="parse-error"
+ modules="HTML::Parser">
+ {text} is not
closed.End tag of an element is not found before, for example, an end tag of another element appears or the end of the document. The document is non-conforming.
+ +Only body, colgroup, dd,
+ dt, head, html, li,
+ ol, option, optgroup,
+ p, rb, rp, rt,
+ tbody, td, tfoot,
+ th, thead, tr,
+ ul end tag can be omitted in HTML documents.
+ For any element except for void element, there must be an explicit
+ end tag.
canvas elementcanvas element is no longer
+ defined as empty. There must be an end tag
+ </canvas>.Note that misnesting tags, such as
+ <a><b></a></b>, are not
+ allowed and they also cause this error.
<html> tag is not
the first start tag.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 @@ -394,9 +1189,17 @@
<{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 @@ -404,6 +1207,19 @@
For any end tag in HTML document, there must be a corresponding start tag.
+ +base, basefont,
+ bgsound, br, col,
+ embed, frame, hr,
+ image, img, input,
+ isindex, link, meta,
+ param, spacer, or wbr elementbase 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.
The document is non-conforming.
For example: -
head element must contain exactly one
- title child element.tr
- element must contain one or more td or th
- child element.head elementtitle child element.html elementhead child element followed
+ by a body element.tr elementtd or th child element.{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.
-Note: The conformance checker does - not support form elements yet.
-Possible causes:
Any inline-level content must be put
in e.g. paragraph element such as p.
div, hn, or
- sectionThough some elements such as div,
- li, and td allow
- either one of block-level or inline-level content
- is allowed. If there is a block-level content,
- any inline-level content must be put
- in e.g. paragraph element such as p.
aside,
+ div, hn,
+ p, or sectiondiv,
+ li, td, or thThe parent element allows either
+ block-level or inline-level content. If there is a
+ block-level content, any inline-level content must be
+ put in e.g. paragraph element such as p.
For example, an HTML document fragment
+ <div><p>Hello!</p> World!</div>
+ is non-conforming, since a word World!
does not belong
+ to any paragraph. (If not part of any paragraph, what is
+ it!?) A conforming example would be:
+
<div><p>Hello!</p> <p>World!</p></div>div element cannot be
+ a child of an h1 element.noscript elementnoscript element is allowed only in the context
where a block-level or inline-level content is expected
and in the head element.
It cannot be used in e.g. ul, table,
or select.html element
- that is the root element of 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.
blink,
+ center, or marquee elementbutton, datalist,
+ fieldset, form,
+ input, label,
+ optgroup, option, output,
+ rb, rp, rt, ruby,
+ textarea, or textarea elementarea 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.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 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/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.
ruby
+ element.content element.$0
+ modules="ContentChecker::HTML">
+ {text}
element before this element.There must be an element before another element, but there @@ -531,39 +1610,110 @@
rp element must
+ be a parenthesis.$0
+ modules="ContentChecker::HTML">
+ {text}
is not specified.A required attribute is not specified. The document is non-conforming.
Some attribute is defined as required.
- For example, any img element must have
- alt and src attributes specified.
Without required attributes specified, user agents
- cannot provide the full functionality of the element
- to the user.
img elementsrc attribute must be specified.
+ Additionally, the alt attribute must be specified
+ in many cases.link elementrel attribute must be specified.
+ Note that the rev attribute is obsolete.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. + The document is non-conforming.
+ +meta elementmeta element, only one of
+ name, http-equiv, or charset
+ attribute is allowed.ismap attribute may only be
+ used for the image contained in an a element.xml:lang attribute is not
allowed in HTML document.The xml:lang attribute is not allowed in
HTML document. The document is non-conforming.
The lang attribute in the null
- namespace for HTML elements is defined as conforming only for
- XML document.
Use of the xml:lang attribute is conforming
+ only in XML documents.
To specify natural language information in HTML document,
use lang attribute instead.
charset attribute is not
allowed in XML document.lang attribute is not
allowed in XML document.The lang attribute in null
- namespace for HTML elements is defined as conforming only for
- HTML document.
To specify natural language information in XML document,
use xml:lang attribute instead.
noscript element cannot be
+ used in XML document.xmlns attribute
in the null namespace is not allowed in
XHTML document. The document is non-conforming.The xmlns attribute in the null
namespace is not allowed in XHTML document.
This error should not occur in conformance-checking +
This error should not occur in conformance-checking of static documents.
{@}
+ 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 + value of the attribute is not one of them. The document + is non-conforming.
+ +meta element, http-equiv attributeOnly 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">utf-8.
+ Values Content-Style-Type and
+ Content-Script-Type are currently not allowed.
Value Keywords is not allowed. Use
+ name attribute instead of http-equiv
+ attribute.
Values Expires, Pragma,
+ and Cache-Control are not allowed;
+ use real HTTP header fields for cache control.
<meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is obsolete.Old long character encoding declaration syntax
+ <meta http-equiv="Content-Type" content="text/html; charset=charset-name">
+ is in use. The document is non‐conforming.
The new character encoding declaration syntax is: +
<meta charset="charset-name">{@}
+ is not allowed.{value}.{value}
+ appears in the attribute value twice.# 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. @@ -662,29 +2127,116 @@
{@}
+ is not an allowed value.$0
+ modules="ContentChecker::HTML">
+ {value}
is non-conforming.The specified link type is non-conforming, and therefore the document is non-conforming.
-contentsindex.copyrightlicense.homeindex.previousprev.startfirst.toctoc or topindex.{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.contextmenu attribute references
+ no menu.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.Warning: The data served to the conforming checker might be out of date; it might have already - been accepted or rejected, depending on which the document - might be conforming or non-conforming. See WHATWG Wiki + been accepted or rejected. The document might or might not be + conforming depending on the status. See WHATWG Wiki 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.colspan attribute
results in creating a table column that does not contain
any cell anchored to it.td or
@@ -758,47 +2369,187 @@
The document is non-conforming.
For example, the table below is non-conforming: -
<table>
+ <table>
<tbody>
<tr><td rowspan=2></td></tr>
</tbody>
</table>
- ... is non-conforming, since the second row contains only
- a cell that spans the first and the second rows.
+ ... since the second row contains only
+ 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.{value}, is syntactically not a valid
+ attribute name.{value} is used.{value} is used.{@}: An obsolete
- subtype is used.{value} is used.The specified Internet Media Type is registered with status + of OBSOLETE.
+ +text/ecmascripttext/ecmascript is obsoleted in
+ favor of application/ecmascript. Note that
+ text/javascript would be better alternative
+ for 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.. or
- ..) should not occur in an absolute reference.. or
+ ..) occurs in an absolute reference.Dot-segment (. or ..) should
not occur 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
+ instead of empty path component.
For example, http://www.example.com/
+ is preferred to http://www.example.com.
The hexadecimal digit in percent-encoding string in the IRI is in lowercase. Though the IRI is conforming, @@ -854,8 +2660,26 @@
{value}
+ should be spelt in lowercase.The scheme part of the IRI is written in uppercase letter.
@@ -887,34 +2717,588 @@{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. + The document is non-conforming.
+ +An entity labeled as Internet media type
+ text/cache-manifest must contain a cache manifest.
A cache manifest must start with a line whose content is
+ CACHE MANIFEST
+ (exactly one space character between
+ CACHE and MANIFEST).
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
+ syntactically invalid.{value} in lowercase.mul should not be
+ used.{value}.{value}
+ is syntactically invalid.und should not be
+ used.{value}) is not used.{value}
+ is syntactically invalid.{value} in uppercase.{value}.{value} is not allowed.http://www.w3.org/1999/02/22-rdf-syntax-ns#.parseType attribute.{local-name} is not supported; it might or
+ might not be conforming.The conformant checker does not support the attribute. +
The conformant checker does not support the element. It cannot determine whether the document is conforming or not.
{local-name} of element
+ {element-local-name} is not supported;
+ it might or might not be conforming.The conformant checker does not support the element. +
The conformant checker does not support the attribute. It cannot determine whether the document is conforming or not.
$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 has now been
+ checker; it is non-conforming unless it now has been
registered.The rel attribute is defined as a list of link types.
@@ -927,60 +3311,673 @@
The link type might have been added to the registry since then.
In such case it might be conforming. Otherwise, the
document is non-conforming.
shortcut iconshortcut is not registered.
+ Use only icon for linking to so-called favicon.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.
+これについての詳しい情報はありません。
+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 2007 Wakaba
-This library is free software; you can redistribute it +
Copyright ‐
+Wakaba
+<w@suika.fam.cx>.
This document is free software; you can redistribute it and/or modify it under the same terms as Perl itself.