CLZTRAccessibility
What CLZTR aims for, what works today, what does not yet, and how to tell us when something stops you.
The standard we hold ourselves to
WCAG 2.1 Level AA, on clztr.com, clztr.app and the mobile apps. That is the level referenced by the European Accessibility Act, the UK public-sector regulations and Section 508, so meeting it once covers the places that ask.
It is a target and not a certificate. We test with VoiceOver and TalkBack on the core journeys (signing up, the map, opening a cluster, reporting somebody, settings) and with axe and Lighthouse on every page of this site.
What works today
- Every interactive element has a name a screen reader can announce, including the map controls and the report and block actions.
- The map has a list alternative: everything the map shows near you is also a list you can read and act on without touching a map.
- Text scales to 200% without losing content or function, and the app honours the system text size.
- Reduce Motion is honoured: the feature tour, the map animations and the page reveals all stop moving.
- Colour is never the only carrier of meaning. Marker types carry a shape and a label as well as a colour.
- The whole of this site is reachable with a keyboard, with visible focus and a skip link.
What does not work yet
- The map itself is a rendered canvas. Screen readers cannot describe the map surface; the list alternative is the supported path, and it carries the same information.
- Some longer legal documents are served as continuous text without in-page navigation. They are readable and navigable by heading, but there is no table of contents yet.
- Video content on the marketing pages has no captions. It is decorative, and no information is conveyed only in the video, but captions are still the right thing and are not there yet.
If something is missing from this list because we have not found it, that is exactly what we would like to hear about.
Telling us about a problem
Write to the address below, or use the contact form. Say what you were trying to do, what happened, and what you were using. A screen reader and its version is enormously helpful, and so is "I could not tell what the button did".
We answer within five business days with what we found and when it will be fixed. If a fix will take a while, we will tell you the workaround in the meantime rather than leaving you waiting for a release.
Accessibility settings
CLZTR uses your system settings rather than a second set of its own: text size, bold text, reduce motion, reduce transparency and increased contrast all apply. Settings › Accessibility in the app links straight to the system screen.