W3C home > Mailing lists > Public > wai-xtech@w3.org > April 2012

Re: Alternative to @aria-describedAT: <a role=img>

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 6 Apr 2012 18:41:08 +0200
To: Alexander Surkov <surkov.alexander@gmail.com>
Cc: wai-xtech@w3.org
Message-ID: <20120406184108063620.be982b2e@xn--mlform-iua.no>
Alexander Surkov, Fri, 6 Apr 2012 13:06:55 +0900:
> <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.

Hi! I'm not sure I understand what you mean by "jump". But I agree that 
a link is a "primary" option, while a longdesc/aria-describedAT offers 
a secondary option.

However, I would describe this as a role hierarchy: In the case of the 
micro format <a role=link href><img alt="Lorem ipsum."></a>, the 
primary option of is associated with the role of the outer element - 
the link. And, for instance  VoiceOver, will present the above micro 
format like so: "Lorem ipsum. Link.".

Whereas in the micro format <a role=img href><img alt="Lorem 
ipsum."></a>, VoiceOver will say: "Lorem Ipsum. Image.". In this case, 
the "primary option" is to consume the <img> as an image. While the 
secondary option is to activate the link.

And so, the goal with <a role=img> or <a role=desclink> is to make sure 
the link is *not* presented as the primary role/option.

Do you get me? Or are we talking past each others with regard to 
primary/secondary and "jump"?
-- 
Leif H Silli
Received on Friday, 6 April 2012 16:41:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:16 GMT