Our commitment
Flagstone exists so people can find out whether a place will work for them before they travel to it. The people who most need that answer are disabled people, so the app itself is built to be used with a screen reader, at large text sizes, with reduced motion, and without relying on colour to carry meaning. We target WCAG 2.2 Level AA and Apple’s iOS accessibility guidelines (opens in new tab).
What the app supports
| Feature | Status | What that means here |
|---|---|---|
| VoiceOver | Supported | Every control has a spoken label, role, and where useful a hint. Status changes, filter results, and errors are announced. Photos carry descriptions written by the person who uploaded them. |
| Larger Text | Supported | Text scales with your Dynamic Type setting, including the accessibility sizes. Layouts reflow rather than clip. |
| Dark Interface | Supported | A full dark theme that follows your system setting, plus a manual toggle in Settings. |
| Sufficient Contrast | Supported | Text and controls meet WCAG AA contrast ratios in both light and dark themes. Automated tests block changes that would regress this. |
| Differentiate Without Colour Alone | Supported | Severity is shown as a number and a word, not just a colour. Status uses labelled badges. Links carry underlines. |
| Reduced Motion | Supported | When Reduce Motion is on, map and sheet animations are shortened or replaced with cross-fades. |
| Captions & Audio Descriptions | Not applicable | Flagstone contains no video or audio content, so there is nothing to caption or describe. |
| Voice Control | Under evaluation | Controls are labelled in ways that should work with Voice Control, but we haven’t finished testing it end to end, so we don’t yet claim it. |
Designed for the way people actually use it
- You can browse without an account. Reading the map, the part most people need, never requires signing up.
- Touch targets are at least 44 × 44 points, the size Apple recommends for reliable tapping.
- Reports say what they mean. Severity carries a plain-language consequence, not just a number.
- We never claim a place has no barriers. We only say that nobody has reported one. An empty map means missing data, and the app says so.
- Photos are optional and described. A photo is never the only way information is conveyed.
Known gaps
We would rather list these than pretend they don’t exist:
- Voice Control has not been fully tested (see above).
- Photo descriptions are optional, so older reports and reports from people who skipped the field may have no description beyond the barrier’s own text.
- The map itself is inherently visual. We pair it with a text list of nearby barriers, including distances, so the map is never the only route to the information. A spatial view is still easier for sighted users.
- Flagstone is available in English only at present.
Assistive technologies we test with
VoiceOver on iOS, Dynamic Type at accessibility sizes, Reduce Motion, Dark Mode, and colour-vision simulation for the common forms of colour blindness. Testing is done on physical hardware, not only the simulator.
Tell us where we got it wrong
If something in Flagstone is difficult or impossible for you to use, that’s a bug and we want to hear about it. Please include the device and which assistive technology you were using if you can, but a plain description is completely fine too, and no report is too small.
Email us about accessibilityWe aim to respond within 3–5 business days. You can also report issues on GitHub (opens in new tab), or use the Feedback option inside the app.
Last reviewed: 19 August 2026. We review this statement with each significant release.