Documents · Operations

Accessibility Statement

What works, what does not yet, and how to tell us.

Version: v1.0
In force since: 24 July 2026
Last updated: 24 July 2026
Contents: 5 · 3 min read

In short

Target: WCAG 2.2 level AA for this website and the cabinet.

We state the known gaps instead of claiming full conformance we have not audited.

Write to us and an access problem is treated as a bug, not a feature request.

1.The commitment
Schools and public bodies buy FND, and an accessibility barrier in a purchase decision is our problem, not the buyer's. We aim for WCAG 2.2 level AA on findndo.app and the web cabinet, and for the iOS app to work with VoiceOver and Dynamic Type.
2.Current status
Partially conformant, self-assessed. There has been no third-party audit, and we say so rather than print a badge.
1. 2.1The site is built from semantic HTML with text alternatives, keyboard-reachable controls and visible focus.
2. 2.2Colour contrast targets AA; the palette is deliberately high-contrast ink on white.
3. 2.3Every animation respects prefers-reduced-motion.
4. 2.4Documents are readable as web pages rather than trapped in PDFs behind a form.
3.Known gaps
1. 3.1The live map in the iOS app is inherently visual; the activity list is the accessible equivalent, and it is not yet at full parity.
2. 3.2Some decorative motion on the marketing pages is reduced, not removed, under prefers-reduced-motion.
3. 3.3No formal audit has been carried out, so this list is what we have found ourselves, not what an auditor would find.
4.Telling us
Write to hello@findndo.app with the page and what happened. We answer within two business days, and an accessibility defect goes into the same queue as a payment bug, not into a backlog.
5.Legal context
This statement is made in the spirit of the European Accessibility Act and the Belgian rules implementing it. Where a partner organization has its own statutory accessibility obligations, we will supply what it needs to document ours.