Updated 2 November 2026
Accessibility
A map is the hardest kind of page to make accessible, and this one does not claim to be finished. This page states the target, what is done, and what is still missing.
Draft. Written from what this deployment actually does — the tables it writes, the cookies it sets, the retention it enforces. It has not been reviewed by a lawyer. Treat it as the brief for that review, not as legal advice.
Target
WCAG 2.1 level AA for the interface. The map canvas is treated as an enhancement: the same information is available as lists, records and API responses, because there is no honest way to promise a screen-reader experience for a canvas.
What is implemented
- Four themes, including High contrast (pure black and white with an amber accent). Body text is at least ~12:1 on every theme.
- Keyboard shortcuts (press
?) for the panel, search, nearby mode and projection, and Escape to dismiss. - Every icon-only control has an accessible name; panels expose
aria-expanded; results announce viaaria-live. - Semantic headings and landmarks, and a skip link to the main content.
- No autoplaying audio or video; no motion that runs without being asked for.
Known gaps
- The map canvas cannot be navigated by keyboard alone, and its content is not described to screen readers. Records remain reachable through search, the nearby panel and the API.
- Pointer targets on clusters are small at low zoom; the click tolerance helps but does not replace a larger hit area.
- Some dense data pages are tables without full row/column associations.
- Focus styling follows the browser default; it is visible but not customised.
Feedback
If something blocks you, say which page and which assistive technology — that is enough to act on, and a real report beats an audit score.
Contact details are published with the other legal pages on this deployment.