- From: Brennan Young via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Dec 2022 13:48:18 +0000
- To: public-svg-issues@w3.org
This appears to be a mistake or oversight. My understanding is that symbol is something like an abstract class in Java (etc.) and is therefore not "real" content until it is referenced by something that is "real" content. For the same reason, a symbol should not permit naming. (The name belongs on the `use`). IMO a `use` element should inherit descriptions, roles, or interactivity from the ancestor `symbol` (with the potential for the `use` element to override those fields), but the symbol itself should **never** be included in the accessibility tree, whether or not it is referenced by `use`. -- GitHub Notification of comment by brennanyoung Please view or discuss this issue at https://github.com/w3c/svg-aam/issues/17#issuecomment-1342764993 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 December 2022 13:48:20 UTC