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

Re: Next Tasks on the Text Alternatives Document

From: Shane McCarron <shane@aptest.com>
Date: Mon, 10 Nov 2014 13:23:48 -0600
Message-ID: <CAOk_reE7CtAe6U6ngGBHfG8X9tbLVu59RB=ZJ107vxXr0EMaUg@mail.gmail.com>
To: Sam Ruby <rubys@intertwingly.net>
Cc: HTML A11Y TF Public <public-html-a11y@w3.org>, steve Faulkner <faulkner.steve@gmail.com>
Oh.  It is just a position to discuss.  If the task force agrees, then the
task force can raise a bug or whatever.  To be honest I don't want to waste
a lot of time debating it.  The content of the document is way more
important to me than whether it is in more than one place.  Also, I am sure
the HTML working group has opinions on this.  As the M12N activity moves
ahead, I expect that all sorts of things are going to change.

Anyway, don't panic Sam!

On Mon, Nov 10, 2014 at 1:17 PM, Sam Ruby <rubys@intertwingly.net> wrote:

> On 11/10/2014 01:45 PM, Shane McCarron wrote:
>>  3. Duplicated text shouldn't be in html specification - it will diverge
>>     with this note and there is always a risk that there will be
>>     conflicting advise.  Moreover, the HTML spec already references this
>>     note.
> I was afraid this would happen.
> As an editor of the Text Alternatives document feel free to decide what
> should be in the Text Alternatives Document.
> If you have feedback on what should be in the HTML specification, I
> encourage you to post your suggestions on public-html.
> - Sam Ruby

Shane McCarron
Managing Director, Applied Testing and Technology, Inc.
Received on Monday, 10 November 2014 19:24:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:42 UTC