Re: On HTML5 conformance and conformance checking

Hi Henri,

"stamp of approval" was tongue in cheek.

I am not saying that the conformance checker needs to flag these
issues, I am only pointing out the limitations of conformance checkers
to provide  a measure of HTML5 "conformance" other than syntactic.

So the holy grail of conformance (to a checker) may well not be real
conformance to the requirements in HTML5.

PS; think your idea about providing alt checking fetaure in
va, is would be a useful addition.


On 14/04/2008, Henri Sivonen <> wrote:
> On Apr 14, 2008, at 17:43, Steven Faulkner wrote:
> > So while the web may one day contain many documents that get the HTML5
> > conformance checker "stamp of approval" It will actually be littered
> > with non conforming HTML5 documents..
> >
> Assuming that a conformance checker issue stamps of approval emerges.
> However, regardless alt, there are many other reasons why passing
> machine-checkable conformance criteria does not imply that the
> non-machine-checkable conformance criteria was passed as well.
> For example, HTML 5 seeks to make layout tables non-conforming, which I
> think it is an exercise in futility. Anyway, it isn't machine-checkable.
> (WCAG 2.0 allows layout tables and ARIA even caters to them, by the way.
> Both pragmatic choices.)
> --
> Henri Sivonen

with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium |
Web Accessibility Toolbar -

Received on Monday, 14 April 2008 16:42:07 UTC