Kainen accessibility statement
Last updated: November 14, 2026 · Version française
Our commitment
We want Kainen to be usable by everyone, including people who use a keyboard, a screen reader or screen magnification. Our target is WCAG 2.1, level AA. Kainen does not fully meet it yet: the known gaps are listed below, with what we are doing about them.
What is in place
- Interface in French and English; the page language is declared for screen readers.
- Text contrast of at least 4.5:1 on the screens checked.
- Every button and field has an accessible name; icons have a tooltip.
- No information is given by colour alone.
- Status messages (saving, connection lost) are announced to screen readers.
- Escape closes windows and menus, and focus returns where it was.
- Password rules are announced as text, not only by an icon.
- Durations and costs can be exported as a table (CSV) to read with other tools.
Known gaps
| Gap | Workaround | Planned fix |
|---|---|---|
| Cards on the canvas cannot yet be reached with the Tab key; creating and moving cards needs a mouse or touch screen | Import steps from a table (CSV); read steps in the details panel and the reports | Keyboard navigation on the canvas (W-34) |
| Moving a floating panel has no keyboard equivalent | Dock or float the panel from its "⋮" menu | Under review |
| Three card type icons (note, decision, system) have contrast below 3:1 | Write to us (below) | Colour review (W-13) |
| About a dozen browser dialogs (confirm, alert) cannot be styled or described | They remain keyboard-operable | A Kainen confirmation dialog |
| Kainen has not yet been tested with real screen readers (NVDA, VoiceOver), at 200% zoom or on phones | Write to us (below) | Tests planned after going online |
How we assessed
Self-assessment on 2026-11-13: automated contrast and accessible-name checks on 9 screens, and scripted keyboard runs. No external audit yet.
Contact
Something stops you from using Kainen, or you need content in another format? Write to support@kainen.io with the subject "Accessibility". We answer within 5 business days.