Peter Rushforth
Peter Rushforth
Assigning this to new milestone, so we can create other issues and assign the milestone instead of trying to fit it all in under one issue via comments.
Regarding: > Should be a programmatically identifiable element. Fixed in 7c86ddc. Upstream: Leaflet/Leaflet#7193. Shouldn't this be on the mapml-viewer / map element? The leaflet-container is in shadow DOM.
Looks like the zoom control is affected too, but not the full screen button.
Also, the reload button has both `title` and `aria-label` attributes, so it announces itself as "reload button reload", redundantly. Let's fix that as part of this issue.
I'm just surprised that shadow DOM is traversable by AT, but probably because I am not too familiar with how it works and how it fails.
Relates to Technical Drawings [Use Case](https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements/issues/1)
This looks interesting! I would not hide the search box behind a hover icon, I would put a big texty hard-to-miss text entry up a the top of the map,...
> I had only considered img to be used for graceful degradation Indeed I think `img` is only needed for graceful degradation. I think that means that the existing client...
I think the behaviour should be like this: https://openlayers.org/en/latest/examples/static-image.html
I think you need to associate the search suggestion link to the search link. I think you should consider that there could be multiple `map-link rel=search` links, so they need...