WebAIM - Web Accessibility In Mind

E-mail List Archives

for

From: Dean.Vasile---
Date: Jun 16, 2025 12:10PM

As a screen reader user, I would have to say probably not.
Because how would I be able to understand the content on the map?
Dean Vasile
IAAP, CPACC
<EMAIL REMOVED>
617-799-1162

> On Jun 16, 2025, at 1:25 PM, Hash, Colton via WebAIM-Forum < <EMAIL REMOVED> > wrote:
>
> Hi, I have been researching ways to develop more accessible web maps where users can select map features with keyboard controls.
>
> Most web map platforms only allow users to pan and zoom in on a map using keyboard controls. However, many web maps have points and polygon features that users can click on using a mouse to display additional information. From my understanding of WCAG Success Criteria 2.1.1 , users should also be able to select and activate map features using keyboard only controls?
>
> Example 1: ArcGIS Map Application
> https://experience.arcgis.com/experience/f49f4168ba6842e2aecb21db3adc969d
>
> This simple ArcGIS web app allows users to click polygon regions or point features with a mouse to display relevant contact information. None of the points or polygons on the map are keyboard accessible, but there is a connected information window where you can select different features with arrow buttons. Is this acceptable to meet keyboard accessibility requirements?
>
>
> Example 2: Custom Leaflet Map Application
> https://mhpdojmtdev.wpenginepowered.com/accessible-map-test/
>
> This is a test map application to demonstrate the ability to select points and polygon features with Tab, and show information with Enter. Google Maps API and Leaflet allow easy implementation of point markers that are directly keyboard navigable. Modifying the DOM of Leaflet output, I was able make it so polygon features are selectable with TAB and Enter. I assume that this is closer to what a Keyboard Navigable map should look like?
>
>
> Example 3: Custom Google Maps Application
> https://mvdstg.wpengine.com/driver-license-exam-stations/
>
> As a final example, this work-in-progress map application has a list of accordion sections for each city, which highlights the location on the map when expanded. The points on the map are also keyboard navigable with Tab, and arrow keys to select between currently visible points on screen. When a point is activated from the map, the associated accordion section is focused. This approach offers an html / text-based alternative to navigate map information, but still allows keyboard users to fully interact with the map.
>
>
> So for a web map to be WCAG 2.1 AA compliant, is it necessary to have these elements be directly navigable with keyboard controls as in Example 2 and Example 3? Or is it acceptable to have an interface where users can indirectly select points from an associated control, as in Example 1?
>
> Thank you for providing additional information and feedback, I am continually learning about web accessibility and have been working to improve our team's map applications.
> -Colton
>