Accessibility statement
Last updated 2026-09-10
Exalink wants Story Builder to be usable by everyone who writes, and by everyone who reads. This page says where we stand, honestly.
What we aim for
WCAG 2.1 level AA.
Where we stand
Not yet formally audited. No external evaluation has been carried out, so we cannot claim conformance. What we can tell you is what has been deliberately built:
- Every interactive control is reachable and operable from the keyboard, including the writing surface, the search palette and the dialogs.
- Focus is always visible, and dialogs return focus where it came from.
- Colour is never the only carrier of meaning; status is also a shape or a word.
- Text colours are chosen against their backgrounds in both light and dark themes.
- Animation is reduced or removed when your system asks for reduced motion.
- The reader offers text size and reading-speed controls, and text-to-speech.
- Interface text is available in English and Ukrainian.
Known gaps
- The map editor places markers on a canvas and, for the marker layer specifically, still expects a mouse. The same actions are reachable from the keyboard through the control panel's location list.
- Canvas-based views — the relationship graph and the diagram editor — present visual information that has no full text equivalent yet.
- No audit has been done, so this list is what we know about, not necessarily all there is.
Telling us about a problem
Write to the contact form with the page and what went wrong. We treat accessibility defects as defects — they go in the same queue as everything else that is broken, not a separate one that never gets read.
If you are not satisfied with our answer, you may contact the accessibility enforcement body in your country.
Next
A formal audit against WCAG 2.1 AA, and this page rewritten to say what it found.