- From: joanmarie via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Oct 2021 14:53:08 +0000
- To: public-svg-issues@w3.org
joanmarie has just created a new issue for https://github.com/w3c/svg-aam: == Should the mappings of a nested 'svg' be different from that of a root 'svg'? == The SVG-AAM's role mappings does not state any distinction between a nested `svg` element and the root `svg` element. Thus every `svg` is a `graphics-document` role (modulo the pending issue #12). I wasn't sure if that was intended or not. Nor is it what Chromium currently does. Before filing a silly bug here, [I asked my silly question on Twitter](https://twitter.com/Joanmarie/status/1450107864626913283). @AmeliaBR said: > It should at least be the same rules as a `<g>` (which means, role/whether it gets exposed depends on the presence of a name or other ARIA attributes). and > Yeah, I think a group role would usually be better than calling out `<svg><svg>` as a nested graphic. Although the `graphics-doc` role allows for nesting, using a nested `<svg>` vs `<g>` is usually a technical distinction with no semantics. Please view or discuss this issue at https://github.com/w3c/svg-aam/issues/18 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 October 2021 14:53:10 UTC