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

Features are not announced (by NVDA, at least) when <map is="web-map" ...> is used #472

Closed
prushforth opened this issue May 21, 2021 · 6 comments

Comments

@prushforth
Copy link
Member

For example.

@Malvoz I know you have mentioned this issue before, perhaps it is the major accessibility issue with the custom built-in <map>. Can you link to where you've discussed this before, or explain again. Thanks for your patience.

@Malvoz
Copy link
Member

Malvoz commented May 21, 2021

Yes that's correct. The HTML AAM issue is: w3c/html-aam#292.

It's mostly (or only) a chromium bug, which Scott O'Hara filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1208405.

@Malvoz
Copy link
Member

Malvoz commented May 21, 2021

BTW we've mentioned the issue in:

And yeah, that Chromium bug is really bad. The <map> polyfill will always have this accessibility issue in all the browser versions that existed before the fix landed.

@prushforth
Copy link
Member Author

Hopefully the evergreen browser trick will make the problem evaporate eventually.

@Malvoz

This comment has been minimized.

@Malvoz

This comment has been minimized.

@Malvoz
Copy link
Member

Malvoz commented Jul 19, 2021

I'll go ahead and close this, as it is an issue due to a browser bug.

@Malvoz Malvoz closed this as completed Jul 19, 2021
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