- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Feb 2020 23:43:32 +0000
- To: public-svg-issues@w3.org
AmeliaBR has just labeled an issue for https://github.com/w3c/svg-aam as "Needs Implementer Input": == Should SVG with no accessible children have role=img? == See discussion: https://github.com/w3c/html-aam/issues/43 (This came up recently on Twitter and I couldn't find the issue because it was on HTML-AAM instead of SVG-AAM.) Summary of issue: Currently, the SVG element is mapped to the `graphics-document` ARIA role. Most uses of inline SVG on the web are for simple icons, where the "document" nature of the SVG tree isn't relevant — there are no interactive or named child nodes. It may be better for end users if these simple SVGs are just treated as regular images. I'd like some feedback from implementers if they see any problem with having an element's role depend on it's child tree. If it seems feasible to include that check, then I agree that using the `img` role for this case, and reserving the `graphics-document` role for cases where there is accessible child content. See https://github.com/w3c/svg-aam/issues/12
Received on Monday, 3 February 2020 23:43:33 UTC