Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[accessibility] Interactive markers should have a default accessible name #355

Closed
Malvoz opened this issue Sep 18, 2021 · 2 comments
Closed
Labels

Comments

@Malvoz
Copy link
Contributor

Malvoz commented Sep 18, 2021

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?


(The same issue was also reported with MapBox: mapbox/mapbox-gl-js#11030.)

@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Mar 18, 2022
@github-actions
Copy link
Contributor

This issue was closed because it has been stalled for 30 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant