W3C home > Mailing lists > Public > public-html@w3.org > November 2012

Re: rationale for keeping alt text spec as normative.

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 5 Nov 2012 14:23:38 +0000
Message-ID: <CA+ri+VkrCdPcyK89drz2UFUSmQb_y7B49WoZ9AH_ESXWS1EGMg@mail.gmail.com>
To: HTMLWG WG <public-html@w3.org>
Hi all, quoting from glenn adams [1] recent email:

> Regarding publishing as a NOTE or REC, I notice (upon rereading) that the
> W3C Process Document states:
>
> "A Working Group Note is published by a chartered Working Group to
indicate
> that work has ended on a particular topic."
>

The alt techniques document is an ongoing effort, which can only maintain
its releveance and usefulness if updated on a regular basis as
implementations change. So if indeed the note track indicates that work has
ended on it, then it should not be on the note track but on the REC track.

[1] http://lists.w3.org/Archives/Public/public-html/2012Nov/0047.html


regards
SteveF

On 2 November 2012 12:45, Steve Faulkner <faulkner.steve@gmail.com> wrote:

> The specification 'HTML5: Techniques for providing useful text
> alternatives' [1] contains normative authoring requirements because the
> HTML5 specification contains normative authoring requirements covering the
> same topic [2].
>
> The normativity of the authoring requirements in the HTML5 specification
> and what they require is the root of the issue, so if the normativity of
> the extension spec is called into question the normativity of the
> requirements in HTML5 must also be called into question.
>
> The content of the 2 documents on the provision of text alternatives
> differ:
>
> * The HTML5 specification contains requirements that contradict the
> requirements of the Web Content Accessibility Guidelines 2.0 [3] and the
> normative requirements do not have agreement within the accessibility
> community.
> * The Techniques document does not contain requirements that contradict
> Web Content Accessibility Guidelines 2.0 and the normative requirements do
> have agreement within the accessibility community.
>
>
> [1]http://dev.w3.org/html5/alt-techniques/
> [2] http://dev.w3.org/html5/spec/the-img-element.html#alt
> [3] http://www.w3.org/TR/WCAG20/
> --
> 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
>
>
>


-- 
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 Monday, 5 November 2012 14:24:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 November 2012 14:24:50 GMT