- From: Matthew Tylee Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 May 2022 14:59:44 +0000
- To: public-svg-issues@w3.org
APA comment on the SVG Native Editor's Draft at: https://svgwg.org/specs/svg-native/ We are concerned that removing the ability to specify an accessible name and description for the image (i.e. `<title>` and `<desc>`) would present accessibility barriers, and would limit the capabilities of SVG Native compared to other image formats. We're concerned about the lack of ability to specify an accessible name and description because content authors would have to take extra steps to provide that information when working in the native context versus on the web. By allowing the use of `<title>` and `<desc>` in SVG Native, authors could use the same file in both contexts. Many operating environments provide a platform accessibility API, and accessibility properties onto which the `<title>` and `<desc>` values could be mapped. Other image formats provide for similar metadata: [the PNG spec provides for various metadata, including an image description](https://www.w3.org/TR/PNG/#4Concepts.AncillInfo); GIF and JPEG files provide for metadata and text comment storage. We request that, when the underlying platform supports the exposure of accessible names or descriptions, that an SVG Native renderer (RFC 2119) MUST expose their contents to the accessibility API. *[Record of the group's approval of this comment](https://lists.w3.org/Archives/Public/public-apa-admin/2022May/0008.html)* -- GitHub Notification of comment by matatk Please view or discuss this issue at https://github.com/w3c/svgwg/issues/874#issuecomment-1119714456 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 May 2022 14:59:46 UTC