Accessibility Statement
Last updated: 7 October 2026
Glauve should be usable by everyone, including people who use a screen reader, a keyboard instead of a mouse, or need larger text and higher contrast. This statement says where we stand and how to reach us.
1. What we aim for
We build to WCAG 2.1 level AA, the standard behind the European Accessibility Act, which has applied to consumer services sold in the EU since 28 June 2025. That means real text instead of images of text, labels on every form field, keyboard access to menus and dialogs, visible focus, and colour combinations that stay readable.
2. What works today
The public site — the homepage, guides, blog, club listings, press kit and all policy pages — is readable by a screen reader, works with the keyboard alone, and follows your browser's text-size settings.
The dark and light themes are both checked for contrast. Our photo privacy labels and status messages are text, not colour alone. Videos on the homepage do not start by themselves and respect your system's reduced-motion setting.
3. What still falls short
Some older parts of the signed-in app have interactive elements that a screen reader announces poorly, and a few dialogs do not move focus inside themselves when they open.
Some user-uploaded photos have no description, so a screen reader cannot tell you what is in them. We are adding prompts that ask members to caption their photos.
The chat timeline is dense on small screens and can be hard to scan with a keyboard.
We are fixing these in order of how many people they block, and we will update this page as each one ships.
4. Tell us about a barrier
Email support@glauve.com with the subject "Accessibility" and tell us what you were trying to do, what went wrong, and which device and browser you used. We reply within 5 working days with what we plan to do and roughly when.
5. If you are not satisfied
If our answer does not resolve the problem, you can complain to the accessibility enforcement body in the EU country where you live. In France that is the DGCCRF; each member state lists its own authority on the European Commission's site.
6. How we test
We check every release with a keyboard only, with a screen reader, and at 200% zoom, plus automated checks in our build. It is not a substitute for real users, so we also read every accessibility email we get.