-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should the mappings of a nested 'svg' be different from that of a root 'svg'? #18
Comments
Map nested 'svg' elements to the group role rather than the generic- container role. Doing so should increase the likelihood that assistive technologies will present the author-provided names of nested 'svg' elements. Note that at the present time the SVG-AAM does not have distinct role mappings for root and nested 'svg' elements. However, initial feedback is that treating nested 'svg' elements as 'g' is the right thing to do. See w3c/svg-aam#18 AX-Relnotes: Expose nested 'svg' as a group rather than a generic container so that ATs are more likely to present author-provided names. Bug: 231654 Change-Id: I7ca09e425b46704f43fbb29cd38139849012b660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3231175 Commit-Queue: Joanmarie Diggs <jdiggs@igalia.com> Reviewed-by: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/main@{#933052}
Map nested 'svg' elements to the group role rather than the generic- container role. Doing so should increase the likelihood that assistive technologies will present the author-provided names of nested 'svg' elements. Note that at the present time the SVG-AAM does not have distinct role mappings for root and nested 'svg' elements. However, initial feedback is that treating nested 'svg' elements as 'g' is the right thing to do. See w3c/svg-aam#18 AX-Relnotes: Expose nested 'svg' as a group rather than a generic container so that ATs are more likely to present author-provided names. Bug: 231654 Change-Id: I7ca09e425b46704f43fbb29cd38139849012b660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3231175 Commit-Queue: Joanmarie Diggs <jdiggs@igalia.com> Reviewed-by: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/main@{#933052} NOKEYCHECK=True GitOrigin-RevId: 6892d3a75290f138c2cc815344c50e8105ac45da
I ended up doing the foolish thing, and trusting the spec. Turns out, the browsers don't follow the spec, and map SVG to Perhaps we should start with the question: In which spec should the default mapping for SVG-in-HTML belong? |
The SVG-AAM's role mappings does not state any distinction between a nested
svg
element and the rootsvg
element. Thus everysvg
is agraphics-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. @AmeliaBR said:
and
The text was updated successfully, but these errors were encountered: