The table below summarizes Web standards supported by WebHACC. See following subsections for more details.
| Standard | Version | Note |
|---|---|---|
| HTML | Web Applications 1.0 | Most parts |
| XHTML | ||
| Atom | Atom 1.0 RFC | |
| Atom Threading 1.0 RFC | ||
| XML | 1.0 Fourth Edition | Tentative |
| 1.1 Second Edition | Tentative | |
| XML Namespaces | 1.0 Second Edition | Tentative |
| 1.1 First Edition | Tentative | |
| CSS | CSS 2.1 Candidate Recommendation | Most parts |
| CSS Color Level 3 LCWD | Most parts | |
| Selectors | 3 | |
| Cache Manifest | Web Applications 1.0 | |
| WebIDL | Editor's Draft 1.96 | Out of date! |
| HTTP | Tentative (no validation) |
The current implementation assumes that there are following requirements:
html element in http://www.w3.org/1999/xhtml
namespace is allowed to be a root element by the HTML5
specification.Conformance checking as per the Web
Applications 1.0 (including HTML5) specification and the manakai's
Conformance Checking Guideline for Obsolete HTML Elements and
Attributes is supported, except for a few newer features such as
Microdata and device (those features will be implemented
later).
The cache manifest syntax is also supported.
Atom 1.0 and Atom Threading 1.0 are supported.
However, conformance to some SHOULD-level requirements, as well as some informational guidelines, are currently not checked. In addition, whether an email-address or a Base64 encoding is correct or not is not checked either.
Use of XML digital signature and encryption is not supported.
The current implementation assumes that there are following requirements:
type of an
in-reply-to element in the Atom Threading 1.0 namespace
[RFC 4685], the
attribute value MUST be a valid
MIME type [WA1].
CSS @namespace and Selectors Level 3 are fully implemented.
Most of CSS 2.1 ( Candidate Recommendation) is implemented.
Most of CSS Color Module Level 3 ( Last Call Working Draft) is implemented.
Since the CSS 2.1 specification is sometimes ambigious or disagree with browsers, our implementation is tend to copy what browsers do unless there is strong resaon to do different thing.
In addition, the current implementation assumes that there are following requirements:
charset parameter of the media
type text/css MUST be treated as if it
were an unknown parameter for the purpose of determining styling langauge for
an HTML style element.style
element whose content is interpreted as a CSS style sheet
MUST consist of zero or more
text nodes.
Note that it may also contain zero or more comment and/or processing
instruction nodes.Regular expression defined in ECMAScript Third Edition Section 15.10.1 is implemented, with the addition of the support for obsolete octal escape notation commonly supported by Web browsers.
To identify ECMAScript regular expressions, the Internet Media Type
text/x-regexp-js
is used.