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
Interactive markers (e.g. markers that bind to popups) should have a default accessible name, e.g. aria-label="Marker" if not specified.
Related WCAG 2.1 Success Criterion: 4.1.2 Name, Role, Value (this issue is to address the Name part of the Success Criterion for interactive markers).
Furthermore, ideally developers should ensure that each marker has a unique and descriptive name, such that the user can know what the marker is visually highlighting (in the case of markers binding to popups it'd also allow AT users to know what it's for before opening the popup). For example, the marker in https://maplibre.org/maplibre-gl-js-docs/example/set-popup/ would ideally be named "Washington Monument" or similar. Perhaps developers can be warned if markers are not uniquely named?
Interactive markers (e.g. markers that bind to popups) should have a default accessible name, e.g.
aria-label="Marker"
if not specified.Related WCAG 2.1 Success Criterion: 4.1.2 Name, Role, Value (this issue is to address the part of the Success Criterion for interactive markers).
Furthermore, ideally developers should ensure that each marker has a unique and descriptive name, such that the user can know what the marker is visually highlighting (in the case of markers binding to popups it'd also allow AT users to know what it's for before opening the popup). For example, the marker in https://maplibre.org/maplibre-gl-js-docs/example/set-popup/ would ideally be named "Washington Monument" or similar. Perhaps developers can be warned if markers are not uniquely named?
(The same issue was also reported with MapBox: mapbox/mapbox-gl-js#11030.)
The text was updated successfully, but these errors were encountered: