Accessibility

Last updated September 1, 2026

We want SK Maps to be usable by every rider. This page describes where the app and this site stand today and how to tell us when something falls short.

In the app

The app's controls carry VoiceOver labels — including the icon-only map controls — and composed cards read as single, sensible elements. Text follows your Dynamic Type setting up through the first accessibility size; above that the app holds the largest size it can lay out reliably rather than letting content clip. Text and control contrast is checked against WCAG AA (4.5:1) by automated tests that run on every build, so a color change that would break legibility fails the build before it ships.

On this site

The site is server-rendered semantic HTML: real headings, landmarks, lists, and links, with alt text on images, visible focus, and no cookie walls or motion traps. It works with a keyboard and reads cleanly in a screen reader.

Known limits

A map is an intensely visual surface, and parts of the experience — following a line across terrain, judging a hillshade — do not yet have a good non-visual equivalent. Where the map can't speak, we try to make sure the data behind it can: search, saved items, and detail sheets are fully labeled.

Tell us

If you hit something that is hard to see, hear, reach, or operate, email maps@secondkickmoto.com and describe what you were doing. Accessibility reports go to the top of the queue.