Keyboard focus does not work with <area is="map-area">

[prushforth]

If you tab to focus the map, with scripting enabled, the next tab will take you to the zoom in control, bypassing the <area is="map-area"> elements; if you disable scripting you tab to the area elements in sequence, with the focus indicator showing where you are.

https://maps4html.org/experiments/progressive-enhancement/

[Malvoz]

bypassing the <area is="map-area"> elements

Note that when scripting is enabled <area> and <img usemap> are themselves not actually active (since 05aadb1). I think that's still expected.

The rendered SVG should essentially be feature links though?

[prushforth]

The rendered SVG should essentially be feature links though?

Exactly, but that's not the case, because the map-area code does not use the same implementation as map-feature. I think that maintaining map-area has been mostly overlooked, because we haven't received positive feedback about leveraging the <map> element, quite the opposite, unfortunately.

I've had the impression that talking about <map> has the opposite of the desired effect on old time Web standards folks: they aren't enthusiastic about extending this part of HTML because they don't see the <mapml-viewer> semantics in <map> that I/we do, and they are very very cautious about touching old code that is widely depended upon and could break existing Web sites, maybe not in that order. I might be wrong, but it might be time to retire map-area entirely.