- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Thu, 6 Sep 2012 14:51:39 +0200
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: Adrian Roselli <Roselli@algonquinstudios.com>, Mathew Marquis <mat@matmarquis.com>, Peter Winnberg <peter.winnberg@gmail.com>, Steve Faulkner <faulkner.steve@gmail.com>, HTML WG <public-html@w3.org>, "public-respimg@w3.org" <public-respimg@w3.org>
Laura Carlson, Thu, 6 Sep 2012 06:40:23 -0500: > Hi Leif, > >> Both ideas - <pictcaption> and <desc> - have the problem that until >> support is ready, it is hard to avoid that users receive both the short >> and the long alternative text. > > Yes. alt and and longdesc are native HTML attributes that could work > just fine for <picture>. No need to reinvent the wheel or add needless > complexity. Needless complexity: The complexity is related to lack of support for <picture> (and its required components - <desc>, <pictcaption>, <whatever>). When support is ready, then it should be simple to use <picture>. Even @longdesc is very complex if you want to implement support for it in AT which do not support it already: If you want to hide the long description inside <picture> and link to it via @longdesc, then we get the same problem of 'how to hide the description'. Yeah, the hiding problem (to avoid duplication) would arise even for ATs that support @longdesc. -- Leif Halvard Silli
Received on Thursday, 6 September 2012 12:52:20 UTC