- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Fri, 6 Apr 2012 18:19:17 +0200
- To: Jason White <jason@jasonjgw.net>
- Cc: wai-xtech@w3.org
Jason White, Fri, 6 Apr 2012 13:24:22 +1000:
> Leif Halvard Silli … wrote:
>> Proposal for ARIA.next: <a role=img> and/or <a role=descLink>.
>> 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.
EITHER: The technique doesn't handle it = need @describedAT too.
OR: HTML is modified to allow <a href> as wrapper around
<a role=descLink href><foo></a>. Example:
<a href><a role=descLink href><foo></a></a>
The latter option has the problem that, in the DOM, the outer <a href>
would be transformed into an empty, parallel element:
<a href=a></a>
<a href=b><FOO></a>
Thus, the simplest thing is to say that <a role=descLink> would not
serve the use case of e.g. an <img> that already is wrapped inside a
link. I guess that counts as another disadvantage of this technique.
--
leif halvard silli
Received on Friday, 6 April 2012 16:19:52 UTC