Accessibility
Last updated: 2026-11-01
Our commitment
Pannable is a map, and maps are hard to make accessible. We want
everyone who prospects to be able to plan a trip and read a legal
verdict with the app, whatever tools they use to browse. Our goal is
to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level
AA for everything that is not the map canvas itself, and to give the
map canvas a usable alternative wherever we can. This page says
plainly where we are today, including where we fall short. It is a
statement of current status, not a certification; no outside audit
has been done yet.
What works today
-
Keyboard. Buttons, links, form fields, panels and
dialogs in the web app are built to be reached and operated with the
keyboard.
Focus is always visible (a contrasting ring on the focused element).
The drawing tools (measure, claim outline, trend line), whose
natural input is a mouse click on the map, each have an
Add point at map center button so a shape can be drawn by
panning the map with the arrow keys and pressing the button.
-
Screen readers. Panels, dialogs and status messages
carry names and roles; results such as a land-status verdict are
announced when they appear. Icon-only buttons have text labels.
Decorative images are hidden from assistive technology; meaningful
images on this site have alternative text.
-
Contrast and themes. Text and controls in both the
light and the dark theme meet the WCAG AA contrast ratio (4.5:1 for
text, 3:1 for large text and interface parts). We check a set of
screens automatically on every change with an accessibility test
tool and fix what it reports before release. The site and the app
follow your system’s light or dark preference.
-
Motion and zoom. Animations are reduced when your
system asks for reduced motion. Pages reflow and remain usable at
200% browser zoom and on phone screens; nothing requires a
particular orientation.
-
Plain language. Legal verdicts, warnings and
freshness notes are written in short sentences and never rely on
colour alone: each colour-coded state also has a word or an icon.
Known limitations
-
The map canvas. The map itself is drawn on a WebGL
canvas. A screen reader cannot read the mines, claims, model
colours or land boundaries painted on it, and the cursor position on
the canvas cannot be operated by keyboard alone. We offer text
alternatives for the decisions the map supports: the
Can I pan here? verdict, the ranked spots list, the mine
and claim detail cards and the land-manager readout are all plain
text and keyboard-reachable. The model layers (relative terrain
scores shown as colour) have no text equivalent yet beyond the
legend and the ranked spots.
-
Colour scales. The depositional model layers are
colour ramps over terrain. Users with colour-vision deficiency may
find some ramps hard to tell apart; the ranked spots list and the
per-spot scores are the intended alternative. A high-contrast or
colour-blind-safe ramp option is on our list.
-
Mobile app. The iOS and Android app is in
development. It uses the platforms’ accessibility services
for its controls, but its map canvas has the same limits as the
web map, and we have not yet tested it with VoiceOver and TalkBack
end to end.
-
Third-party content. Basemap tiles, aerial imagery
and the public records we display come from outside providers and
are shown as they are published.
-
File exports. Field packs and the
data exports (CSV, GeoJSON, KML) are data files, not documents
designed for screen readers.
Ask for help or an accommodation
If any part of Pannable is hard or impossible for you to use, or if
you need information from the map in another form (for example a
plain-text summary of the land status and nearby mines for a place
you name), email
support@pannable.app
with the word Accessibility in the subject. Tell us
what you were trying to do, the page or screen, and the browser or
device and assistive technology you use. A person reads every
message; we aim to reply within five business days and to fix
blocking problems ahead of other work. You do not need an account to
write to us.
How we test
Automated accessibility checks run on a set of app screens in our
test suite on every change, and the public pages on this site are
checked for structure, labels and contrast in both colour schemes.
We have not yet commissioned an independent audit; when we do, we
will link the report here.