Skip to content
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

Define computedrole for the SVG roles table #24

Open
Tracked by #69
cookiecrook opened this issue Mar 29, 2023 · 2 comments
Open
Tracked by #69

Define computedrole for the SVG roles table #24

cookiecrook opened this issue Mar 29, 2023 · 2 comments
Assignees

Comments

@cookiecrook
Copy link

cookiecrook commented Mar 29, 2023

Based on the outcome of this ARIA issue…

And this graphics-aam issue/pull:

And this html-aam issue/pull:

SVG-AAM (or svg-aria) may need an update similar to this issue/pull:

However, since SVG-AAM primarily points to the role mappings of core-aam, html-aam, and graphics-aam, it's possible this isn't needed in svg-aam... To avoid duplication. Not sure.

@cookiecrook
Copy link
Author

cookiecrook commented Nov 7, 2023

Reminder to self on this approach discussed in the ARIA F2F Meeting, May 2023 in Seattle.

Quoting:

Consensus from the ARIA F2F was that I would draft a PR for SVG-AAM adding a computedrole column to each of the elements... Many would be "not mapped" but the ones that use the graphics-aria superclass roles would be return svg-<tagname> such as svg-polygon for the <polygon> element. The role instance would still be graphics-image, which is a subclass of the image Core-AAM role... Though the returned computedrole svg-polygon is just a string.

@cookiecrook
Copy link
Author

cookiecrook commented Nov 16, 2023

Until there is a resolution on:

…I'm not certain there is a need to add the host-language defined computedrole values, and I don't want to write spec changes or tests for either assertion (the graphics-aria roles or these new svg-specific computedrole return values) until there's group consensus on the other issue.

…so I think the default-role-for-element portions of web-platform-tests/interop-accessibility#69 may be blocked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant