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 accessibility and tests for <map> and <layer> polyfills #89

Closed
prushforth opened this issue Mar 11, 2020 · 3 comments
Closed

Define accessibility and tests for <map> and <layer> polyfills #89

prushforth opened this issue Mar 11, 2020 · 3 comments

Comments

@prushforth
Copy link
Member

Per this comment, have created an issue to track what issues we encounter with polyfilling the <map> element

@prushforth
Copy link
Member Author

prushforth commented Mar 11, 2020

@Malvoz

I have updated the demo site so that it will work on Safari, a bit (I don't have routine access to Safari, so hard to test it), by replacing the use of the <map> element with a <mm-app> element (renamed <geo-map> to <mm-app>, because it's not geo-specific, and I seriously hope we are able to get the platform to consider <map> for I think pretty good reasons). I take "transparent content model" to mean it presents content that you put there as though the <map> element didn't actually exist. If that is true, the polyfill content should present a root node, perhaps a div as currently implemented, as though it is a future element. I believe at least a part of accessibility means that the map element should be focusable, so that the user can pan/zoom/query using key strokes appropriately mapped. The controls inside the shadow root should themselves be reachable using tab stops, and each should be completely actionable using key strokes.

@Malvoz
Copy link
Member

Malvoz commented Jun 13, 2020

FYI I filed w3c/html-aam#292.

@Malvoz Malvoz changed the title Define accessibility and tests for same for <map> and <layer> polyfills Define accessibility and tests for <map> and <layer> polyfills Oct 19, 2021
@Malvoz Malvoz added the tests label Dec 28, 2021
@prushforth
Copy link
Member Author

Re-open if/when necessary. I would like to not have to discuss the <map> element more than necessary in future.

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

No branches or pull requests

2 participants