- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Fri, 6 Apr 2012 13:06:55 +0900
- To: wai-xtech@w3.org
<a role="img" href="">img link</a> or even <a href=""><img></a> are exposed with "jump" as primary accessible action. Longdesc or aria-describedat is exposed as secondary accessible action which is as I understand sort of URL to image description and not a link. Thanks. Alex. On Fri, Apr 6, 2012 at 12:24 PM, Jason White <jason@jasonjgw.net> wrote: > Leif Halvard Silli <xn--mlform-iua@målform.no> wrote: >> Proposal for ARIA.next: <a role=img> and/or <a role=descLink>. >> >> In more detail: Yesterday, I published a PROTOTYPE of an ARIA based >> long description link technique for the <img> element. [1] Based on >> what ARIA *currently* allows, this is the technique, in one sentence: >> >> An <a> element with @role=img and whose @aria-label >> contains an image description plus an announcement of >> the long description link, is wrapped around the <img>. > > How do you handle the case in which the image is already a link? That is, the > image is a link to a resource, hence the child of an anchor element, but you > also want to associate with it a second link to a description. > >
Received on Friday, 6 April 2012 04:07:24 UTC