Accessibility
This is a statement of what was done, not a certificate. Nobody has audited this site, and we are not going to imply otherwise.
This is a draft, and it has not been reviewed by a lawyer. It describes the offer Margo intends to sell, not every detail of what the product does today — parts of it name commitments that are still being built. It has no legal approval behind it, and Margo is not on sale. It will be finished, checked and versioned before anyone can buy anything. Until then, please read it as a statement of intent.
The standard we aimed at
WCAG 2.2 level AA, as an engineering target. That means we built to it; it does not mean a third party has confirmed we met it.
What is in place
- Semantic landmarks and a heading order that makes sense read aloud.
- A skip link to the main content, first in the tab order.
- Everything operable by keyboard, including the walkthrough (arrow keys, Home and End), the platform selector, the FAQ, and the privacy panel — which traps focus while open, closes on Escape, and returns focus where it came from.
- A visible focus ring that is never covered by a sticky header or a banner.
- Form fields with real labels, errors described at the field and summarised above it.
- Forms that keep what you typed when they reject it, and that prevent a second submission while the first is in flight.
- Status messages announced politely rather than as interruptions.
- Text that reflows to 320px and survives 200% zoom without horizontal scrolling — checked in German as well as English, because German runs longer and is what breaks a narrow layout first.
- A language switcher that is two ordinary links and works with JavaScript switched off, with each language named in its own language and marked up with its own `lang`, so a screen reader pronounces it correctly.
- Every page carrying the right `lang` on the document, in both languages.
- Reduced motion honoured — every animation on the site becomes instant. Nothing is hidden until it animates in, so a page with all motion and all JavaScript switched off still shows everything.
- Reduced transparency honoured: the frosted surfaces become opaque, exactly as the app does.
- Forced-colours mode honoured: decorative washes and glass are dropped.
- Touch targets of at least 44px, and nothing that requires hovering.
- Contrast checked against the actual surfaces the text sits on, including over the translucent navigation.
What we have not done
- No audit by anyone independent.
- No testing with real screen-reader users, in either language.
- No automated accessibility tests in the build.
- No formal accessibility statement of the kind some markets require, because which markets we sell into has not been decided and the obligations follow from that.
We build for this regardless of whether a law requires it of us. The list above is honest about the difference between building carefully and having proof.
If something does not work for you
Tell us. Say what you were using and what happened. A specific report about one broken control is worth more than any statement on this page, and it gets fixed.
Questions about this page: contact us. To exercise a right over your data: data requests.