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

Re: How to obsolete @longdesc

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 19 Sep 2012 17:47:55 +0200
To: Sam Ruby <rubys@intertwingly.net>
Cc: public-html-a11y@w3.org
Message-ID: <20120919174755794970.f8616372@xn--mlform-iua.no>
Sam Ruby, Wed, 19 Sep 2012 11:40:23 -0400:
> On 09/19/2012 11:32 AM, Laura Carlson wrote:
>> Hi Leif,
>> Obsoleting longdesc in any way is not under consideration.
> That is not a factual statement.  It may not be something that you 
> personally would be willing to consider.  It may not be something 
> that actually happens.  But it is a factual statement that some 
> people are not only considering that, but actively proposing to 
> obsolete longdesc.

What I would like say is that I think David is right when he suggested 
that it should not be a an ARIA feature but a HTML feature. I would be 
more comfortable with such a solution. When we start to mix in ARIA - 
such as in the debates about 'hidden but revealable on such and such 
conditions', then the waters become unclear. Plus that the argument 
could be made that ARIA would be getting that feature, anyhow, at some 
point. And so, it has the smack of appear to be getting something but 
not getting anything anyhow.

Leif H Silli

>> Best Regards,
>> Laura
> - Sam Ruby
>> On Wed, Sep 19, 2012 at 10:29 AM, Leif Halvard Silli
>> <xn--mlform-iua@xn--mlform-iua.no> wrote:
>>> Laura Carlson, Wed, 19 Sep 2012 10:19:53 -0500:
>>>> Hi Leif,
>>>>> Thank you for pointing to David's message. Clearly, name change might
>>>>> be a better idea than we have admitted.
>>>>> In that case, a logical 'deal' to consider
>>>> No 'deal' is in consideration. This is an inquiry only.
>>> Sorry, I don't want to disturb the inquiry so I change the topic so you
>>> don't feel you need to stand for my words.
>>> The argument has been mad, in this recent discussion, that HTML5 has no
>>> means for deprecation of features. In the first longdesc poll, there
>>> were no alternatives to replace it with and thus, true deprecation was
>>> not possible. But if an alternative emerged, then HTML5 has some
>>> mechanisms for making features obsolete but conforming, as pointed out
>>> with in my message with the unlucky word 'deal'.[1]
>>> [1]
>>> http://www.w3.org/mid/20120919165642623450.594a22b3@xn--mlform-iua.no
>>> Leif Halvard Silli
Received on Wednesday, 19 September 2012 15:48:34 UTC

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