- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Wed, 14 Mar 2012 13:19:38 +0100
- To: "Schnabel, Stefan" <stefan.schnabel@sap.com>
- Cc: Joshue O Connor <joshue.oconnor@cfit.ie>, Laura Carlson <laura.lee.carlson@gmail.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Schnabel, Stefan, Wed, 14 Mar 2012 10:06:49 +0100: > In each case, it should be extended to all kinds of embedded and > graphical content, i.e. for <object>, <svg>, SVG lives in its own namespace. Hence, this working group cannot add @longdesc to <svg>. What we could do, is to extend @longdesc to any element with role='img': <div role=img longdesc=link ><svg/></div> <object role=img data=svg.svg type='image/svg+xml' longdesc=link ></object> > <canvas> etc. for these > may contain partially or completely inaccessible content that may > need an accessible description reference. Looking squarely at Laura's Change Proposal: Is there any reason not to expand it - before we go to a poll/survey - to cover any element where the author has given it role='img'? I mean: If we want to put the horse *before* the cart? It would be futile to ask the chairs to consider @longdesc a second time, for other use cases, if we are not able to the the single, most logical step. An element with role=img is - from an AT user's point of view - entirely closed. It is only the info that the author has placed there - in @title, @aria-label, @alt etc - specifically for that purpose, that makes a role=img element perceivable to that user group. Laura, Janina, Chairs? -- leif halvard silli
Received on Wednesday, 14 March 2012 12:20:24 UTC