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

[prushforth]

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]

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]

BTW we've mentioned the issue in:

• https://github.com/Maps4HTML/Web-Map-Custom-Element#a-parellel-customized-built-in-element
• https://github.com/Maps4HTML/MapML-Proposal/blob/master/high-level-api.md#polyfill

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]

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

[Malvoz]

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