W3C home > Mailing lists > Public > www-archive@w3.org > April 2012

Re: another example of HTML5 conformance and advice divergence

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Wed, 18 Apr 2012 14:36:21 +0200
Message-ID: <CA+ri+VnNG4QXxhKhVW4oFfBK_7O6EkQOqO7YOYJpfd1eU7oJeQ@mail.gmail.com>
To: Philippe Le Hegaret <plh@w3.org>
Cc: Jeff Jaffe <jeff@w3.org>, www-archive <www-archive@w3.org>, Sam Ruby <rubys@intertwingly.net>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "Michael(tm) Smith" <mike@w3.org>, Ian Hickson <ian@hixie.ch>
Hi Philippe,



"Historically speaking, it has always been the case that
developer documentation on browser websites or alternative websites have
differences."

Yes and historically this has lead to problems for developers and users. In
any case we are not talking about alternative, unofficial differences, we
are talking about 2 specifications both claiming to canonically define
HTML5, how it is to be implemented and how it is to be used.

1.2 Is this HTML5?
>
> In short: Yes.
>
source:
http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#is-this-html5
?

Anyway, I understand that the W3C has no control of the HTML standard.


regards

Stevef

On 18 April 2012 11:39, Philippe Le Hegaret <plh@w3.org> wrote:

> Hi Steve,
>
> Thank you for the information.
>
> The HTML Working Group only controls what goes in the W3C HTML5
> specification and makes the decision of how much such divergence needs
> to be. At the end of the day however, the Working Group doesn't control
> documents from other Working Groups or that are being published outside
> the W3C website. Historically speaking, it has always been the case that
> developer documentation on browser websites or alternative websites have
> differences. We also have to recognize that we don't control authoring
> tools or Web developers either. That's the nature of the Web and the
> nature of our effort to spread what we believe are good practices and
> advices. People and groups are entitled to their own opinions. We
> certainly expect that the Working Group seek convergence instead of
> divergence and makes informed decisions when divergence happens. That's
> part of the value of the Working Group and, while the current group
> operation mode isn't smooth and has a high toll on the Group
> participants, it is still important to move HTML forward.
>
> Philippe
>
> On Wed, 2012-04-18 at 09:58 +0200, Steve Faulkner wrote:
> >
> > FYI
> >
> > Recent HTML WG decisions have resulted in title attribute use on an
> > image without an alt attribute no longer being conforming in W3C HTML5
> > but continuing to be conforming in WHATWG HTML. The WHATWG HTML also
> > continues to advocate the use of the title attribute in cases that
> > have a negative impact on accessibility for a range of users, while
> > the advice has been removed from W3C HTML5
> >
> >         1.2 Is this HTML5?
> >         The W3C HTML specification omits a number of suggestions
> >         regarding using the title attribute, and makes using the title
> >         attribute for captions non-conforming in certain specific
> >         cases, because of a number of working group chair decisions
> >         from March 2012: first, second, third.
> >
> > source:
> >
> http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#is-this-html5
> ?
> >
> > regards
> > Stevef
> >
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Wednesday, 18 April 2012 12:37:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:44:03 UTC