- From: joanmarie via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Sep 2021 11:13:11 +0000
- To: public-svg-issues@w3.org
joanmarie has just created a new issue for https://github.com/w3c/svg-aam: == When is the "symbol" element mappable? == The SVG-AAM states that `symbol` is mapped as `graphics-object` *if it meets the criteria for inclusion*. What could make it meet that criteria? The SVG spec's [Notes on symbols](https://svgwg.org/svg2-draft/struct.html#SymbolNotes) states: > ‘symbol’ elements must never be rendered directly; their only usage is as something that can be referenced using the ‘use’ element. The user agent must set the display property on the ‘symbol’ element to none, as part of the user agent style sheet, and this declaration must have importance over any other CSS rule or presentation attribute. So I'm having a hard time coming up with what would make this never-rendered, template object be directly included in the accessibility tree. But the associated role-mapping note ends with: > Either the symbol or the use element, or both, may have an associated accessible object, depending on where the author has provided names, descriptions, roles, or interactivity. Assuming this is indeed correct, it would be helpful to have some concrete example(s) for when: * The `symbol` element is exposed instead of the `use` element(s) * The `symbol` element is exposed along with the `use` element(s) Thanks! Please view or discuss this issue at https://github.com/w3c/svg-aam/issues/17 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 September 2021 11:13:13 UTC