- From: joanmarie via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Oct 2021 12:57:42 +0000
- To: public-svg-issues@w3.org
Right now, Chromium is exposing these (and also non-link `a`) in the same was as does a `div` and (included) `span`, namely using its internal "generic-container" role. While that's not 100% consistent with what is described here, it IS consistent with what I state in the opening report, namely: These things should NOT be mapped the same as an ARIA `group` role. Now that ARIA has the `generic` role for role parity with `div` and `span`, I think the thing to do is update SVG-AAM to make that the mapping rather than have platform-specific mappings. Then the Core-AAM can be where we deal with how badly we want to distinguish inline generics from block generics on a platform-by-platform basis. -- GitHub Notification of comment by joanmarie Please view or discuss this issue at https://github.com/w3c/svg-aam/issues/2#issuecomment-945738901 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 12:57:44 UTC