[Bug 21579] Empty @alt should not imply role="presentation" if the <img> has @usemap

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

steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #2 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to comment #0)
> See comment number 10 in bug 21565
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21565#c10
> 
> If empty @alt on @usemap were to imply role="presentation", then the entire
> image map would have to stop working. This follows from ARIA’s requirement
> that elements that are "linked" should be altogether disabled if one
> disables the "main" elment. (E.g. if you do <table role="presentation">,
> then all the childrene elements will be disabled as well)
> 
> Looking in Safari + VoiceOver, there is thus a difference between doing
> 
> 1) <img role="presentation" usemap="#map" alt="alt" src="src" />
> 
> on one side, and on the other side only use empty alt:
> 
> 2) <img usemap="#map" alt="" src="src" />
> 
> In the first case, the entire image map stops working, while in the other
> case, the image map works just fine. (Also, in Safari + VoiceOver, the alt
> of the img in the image map seems to not be presented to the user - only the
> alt of the area elements are presented.)
> 
> I think we can take for granted that there are many image maps around where
> there is an empty @alt, and where the author have not intended that this
> would make the image map stop working in AT.
> 
> Further more, adding role="presentation" on an anchor element does as well
> not remove its interactivity. And given that image maps are links, to the
> extent that HTML5 requires the CSS img:link{} selector work for images that
> are image maps, it does not make sense to say that empty alt should remove
> the image map <img> elements from the accessibility tree.

Can you provide a concise description of the chnages you think need to be made?

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

Received on Tuesday, 28 May 2013 09:13:36 UTC