- From: <bugzilla@jessica.w3.org>
- Date: Mon, 30 Aug 2010 22:59:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10455 --- Comment #41 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2010-08-30 22:59:45 --- (In reply to comment #34) > > <a href="URL" rel="longdesc"><img src="*" alt="*"/></a> > > What does one do if the image itself is already wrapped in an anchor? The underlying premise of that question is that the justification of @longdesc has to do with _technology_. That @longdesc provides a workaround for technical challenge. But, no. Reading what Laura said [1], one has to come to the conclusion that it is about semantics - @longdesc is supposed to link to a description of some particular quality. [1] http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0190 However, in practise, @longdesc does _not_ provide a workaround: when taking in the corrections that I pointed out in Comment #28, then most of the @longdesc examples in the wild that Laura has documented, duplicate the @longdesc URL in anordinary anchor link. A link without any link type information whatsoever. Also, if we concentrate on @rel="longdesc" and use of image maps, then we can in fact smash the longdesc usecase together with the image map issue - which also needs to be solved better in HTML5. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 30 August 2010 22:59:49 UTC