You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is great work. I'm a big accessibility fan and have been trying to push the limits on accessibility in the mapping space as its definitely something the industry has been neglecting. I work on Azure Maps which leverages Mapbox gl js for rendering, but have wrapped it, created our own UI controls and spent a lot of time adding accessibility features. For example, we leverage the vector tiles to help power the screen reader descriptions when the map moves. This ended up being generating much more accurate descriptions than what we were seeing when using a reverse geocoder based on the center of the map. We have also documented a bunch of accessibility features and tips here: https://docs.microsoft.com/en-us/azure/azure-maps/map-accessibility
One key accessibility item that we are still working on is a better high contract light style. Currently we are just using our light greyscale style as I didn't have a designer available when we got to that work item, but plan to address this in the next six months.
The text was updated successfully, but these errors were encountered:
Thanks for the kind words, and for reaching out! That's great documentation, nice job!
Adding Azure to the evaluation report is currently out of scope as it only targets the reference tools for the Use Cases and Requirements for Standardizing Web Maps report. @AmeliaBR do we intend to extend the list of reference tools?
This is great work. I'm a big accessibility fan and have been trying to push the limits on accessibility in the mapping space as its definitely something the industry has been neglecting. I work on Azure Maps which leverages Mapbox gl js for rendering, but have wrapped it, created our own UI controls and spent a lot of time adding accessibility features. For example, we leverage the vector tiles to help power the screen reader descriptions when the map moves. This ended up being generating much more accurate descriptions than what we were seeing when using a reverse geocoder based on the center of the map. We have also documented a bunch of accessibility features and tips here: https://docs.microsoft.com/en-us/azure/azure-maps/map-accessibility
One key accessibility item that we are still working on is a better high contract light style. Currently we are just using our light greyscale style as I didn't have a designer available when we got to that work item, but plan to address this in the next six months.
The text was updated successfully, but these errors were encountered: