- From: Peter Winnberg <peter.winnberg@gmail.com>
- Date: Thu, 30 Aug 2012 18:33:09 +0200
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Mathew Marquis <mat@matmarquis.com>, HTML WG <public-html@w3.org>, public-respimg@w3.org
2012/8/30 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>: > I don't understand what you say here. What I am trying to say is basically that ARIA attributes on the img element cannot replace the alt attribute because the alt attribute has been around so much longer. If we take your example: > <picture alt="Alernative text" id="pict" > > <img src=file aria-labelledby="pict" /> > </picture> What a browser / AT that lacks support for ARIA and the picture element would "see" (i.e., what parts of this markup is supported) is most likely this: <img src=file /> Which means that it has an image with no alt text. I have previously expressed concern that people would abuse this element to show images that don’t share the same content [1]. Having an alt attribute on the picture element makes it fairly clear that they should share the same alternate text and therefor also content. On the other hand, repeating the alt text for both the img and the picture elements is problematic (for example, what if the alt text isn’t the same on both attributes?) just like you pointed out. > <picture aria-labelledby="pict" > > <img src=file id="pict" alt="Alernative text" /> > </picture> Placing aria-labelledby on the picture element instead of the img element seems like a possible solution. Just not made up my mind if this still sends that "signal" that all images inside the picture element should share the same content or not. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=18384#c5
Received on Thursday, 30 August 2012 16:33:36 UTC