Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Accessibility: basemap contrast

Closed
#80 1 comment 0 reactions 1 assignee View on GitHub

@jimsafley is already working on this.

Since Sep 3, 2026.

Assessment

This issue has not been assessed yet.

Description

a11y

Some of the basemaps we offer do not meet contrast guidelines for non-text content (at least 3:1, exceptions apply for map types such as heatmaps where color gradients are essential for map representation). The default basemap, CartoDB.Voyager, has about a 1.2:1 contrast with no map boundaries to provide sufficient distinction (as modeled in WCAG Technique G209: Example 3: Map with border boundaries
).

We should also set a contrast approved basemap as the default and assess all offered basemaps to determine which are above contrast minimums to suggest for use in a visible manner. If basemaps offered fail contrast minimums, we could consider replacing those if they cannot or will not be modified.

Dominant language
JavaScript
Stars
12
Forks
22
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from omeka/plugin-Geolocation

All issues in omeka/plugin-Geolocation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.