[svg-aam] Browsers off spec? SVG maps to "group" but the spec suggests it should map to "graphics-document" (#22)

brennanyoung has just created a new issue for https://github.com/w3c/svg-aam:

== Browsers off spec? SVG maps to "group" but the spec suggests it should map to "graphics-document" ==
I ended up on a bit of a wild goose chase because the SVG-AAM spec indicates that SVG should map to `graphics-document` by default, although it is unclear whether this is SVG in the context of SVG, or whether it also applies to SVG in the context of HTML. I simply can't figure it out.

https://www.w3.org/TR/svg-aam-1.0/#mapping_role mentions a default mapping for SVG
https://github.com/w3c/html-aam/issues/43 contains the discussion which led to the change.

Questions:
Where does an author look to find unambiguous specifications about SVG default role mappings? Is it actually specified? Where?

If a SVG conveys meaning (e.g. a histogram) and an author omits an explicit role, will other aria (such as `aria-roledescription` or `aria-label`) still work?

Is this important enough to worry about? 
If it is, I suggest that either we revert the change in the spec, or lobby the browser vendors to implement the change.

In general, I find the role mapping for SVG and graphics-aria horribly complicated and difficult to understand. Is there any chance we could clarify this?

Please view or discuss this issue at https://github.com/w3c/svg-aam/issues/22 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:26:35 UTC