- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Wed, 14 Mar 2012 05:36:30 +0100
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Laura Carlson, Tue, 13 Mar 2012 15:33:14 -0500: >> want it used for more than just <img>. > > No reason why longdesc could not do that. John has longdesc > incorporated into a couple of his media change proposals. Could we expand your CP - now - to cover any element of role=img? You should have all image use cases for role=img covered already. Apart from <iframe>, which has some support, I can only think of lack of implementation as reason for not permitting this. Such a move would e.g. make the following conforming, and thus take away some of the objection to the fact that e.g. embedded <svg> cannot use longdesc: <pre role=img longdesc >ASCII-art</pre> <iframe role=img longdesc ></iframe> <div role=img longdesc ><svg/></div> Personally, I find longdesc on <table> a much longer shot. But if you agree to the above, then we could perhaps also consider longdesc on elements which * have explicit role=img, role=application or role=document; * or - even without explicit role declartion - if the element is prohibited from taking any other role than 'img', 'application' or 'document'. This would actually allow longdesc on <table>, if one of the above roles is explicitly declared. And it would allow longdesc on <audio>, <video> and <iframe> even without the role being declared, because these elements are are limited to role=img/document/application. Please let me hear your opinions. -- Leif Halvard Silli
Received on Wednesday, 14 March 2012 04:37:07 UTC