Accessibility
What the interface is built to, what is checked automatically, and what still falls short.
This page describes what the product actually does. Where something falls short it is named here rather than left for you to run into, because a statement of intent is not an accessibility policy.
The standard
We build to WCAG 2.2 at level AA. Quebec, the rest of Canada, the European Accessibility Act and the ADA converge on it, so meeting it once means meeting it everywhere the platform is used. We have not commissioned an independent audit; when we do, the report will be published at this address.
What is checked on every change
Most of these are enforced by the build rather than reviewed at release, which is the difference between a rule that holds and a rule that was true once. Contrast and focus order need a rendered page, so those two are checked by hand.
- Every control can be reached and operated by keyboard, and shows a visible focus ring when it is.
- Reduced motion is honoured as a removal, not a shortening: with the system setting on, animations do not play.
- Text and controls meet the contrast ratio in the dark theme and in the light one, which are designed as two palettes rather than one inverted.
- Each page has a single main landmark and a skip link that reaches it before the navigation.
- Images carry alternative text, and decorative ones are hidden from a screen reader instead of being described to it.
- The interface reflows to a phone and holds at 200% zoom without a horizontal scrollbar.
- Colour is never the only carrier of meaning: a state that is coloured is also labelled or shaped.
What we know is imperfect
- Content you upload is yours. A photo posted without alternative text has none, and we prompt for it rather than inventing a description of a picture we cannot see.
- The card and identity steps are rendered by our payment provider, so their accessibility is theirs. We test the path into and out of them.
Reporting a barrier
Write to [email protected] with the page and what stopped you. An accessibility report is handled as a defect rather than as feedback, and the answer you get is either a fix or a date.
