[Bug 21565] Should it be an error to use @longdesc on presentational images? And/Or should it _affect_ the role of the image?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21565

--- Comment #10 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to comment #9)

> OK but how does that equate to implementation?
> 
> the current implemnentation of role=presentation is supported across
> browsers and does was i said - removes the element from the acc tree, so AT
> that use the acc tree don't get it or its attributes.

NOTE 1: So, in reality, role="presentation" on void elements such as <img>, has
an effect similar to aria-hidden="true". (Sidenote: But in Firefox, at least on
Mac, it seems aria-hidden="true" + alt="not-empty", makes assitive technology
not remove the <img>.)

NOTE 2: Actually, <img> elements with @usemap, then in Safari+VoiceOver, there
is a difference between doing role="presentation" and doing alt="". Namely, if
you do  role="presentation", then the entire image map is removed from the
accessibility tree. But if you do alt="" and do not add role="presentation",
then the image map will function normally.

So there is presedence, it seems, for ignoring the implied presentation role of
an empty alt attribute whenever the <img> has the usemap attribute set.

NOTE 3: I recommend someone with access to Jaws, NVDA etc to check whether an
image with alt="<empty>" + longdesc="foo" causes the screenreader to ignore the
image.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 4 April 2013 13:32:05 UTC