- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Wed, 21 Jan 2015 12:27:04 -0600
- To: Fred Esch <fesch@us.ibm.com>
- Cc: public-svg-a11y@w3.org
- Message-ID: <OF100089CC.29132295-ON86257DD4.0064FC2D-86257DD4.00655AB2@us.ibm.com>
Hi Fred, No. an IFrame really needs to behave like a div unless the author puts a particular role on it. IFrames are used like divs today but with the additional added value of isolating code for security and other reasons. Yes, ellipse needed to behave like a circle. I noticed that when I was doing the final walk through of the docs. It is now fixed in both the SVG2 spec. and the Accessibility API mapping spec. Good pick up! Title is used in the name computation. It is an xml grammar where <title> is like the title attribute in HTML. See the name computation section. Additionally, <desc> maps to the accessible description. Title does not get mapped to an accessible object. It gets mapped to the name for in the associated parent element accessible object. Rich Rich Schwerdtfeger From: Fred Esch/Arlington/IBM@IBMUS To: public-svg-a11y@w3.org Date: 01/16/2015 11:17 AM Subject: SVG2 Accessibility API Mappings Rich, The document looks good. I have couple of questions/suggestions. Ellipse should be treated similar to a circle :) Should iFrame be treated similarly to a view or possibly like a canvas? I don't understand why a SVG title element does not get a Default Platform WAI-ARIA role mapping or a platform WAI-Role role mapping? http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html Regards, Fred Fred Esch Accessibility, Watson Innovations AARB Complex Visualization Working Group Chair W3C SVG A11y Task Force IBM Watson Group
Attachments
- image/gif attachment: graycol.gif
- image/jpeg attachment: 77412907.jpg
- image/jpeg attachment: 77266842.jpg
Received on Wednesday, 21 January 2015 18:27:38 UTC