Accessibility
Accessibility
Last reviewed Sep 25, 2026.
This page says what this product can and cannot do for someone who does not use a mouse, or does not use a screen, or neither. It is written to be checked rather than believed: what is claimed below is what is tested on each release, and everything still missing is listed beside it.
The standard this is measured against
WCAG 2.1, levels A and AA — the standard our automated checks are configured for. We do not claim full conformance. We claim the things listed below, because those are the things we test.
How it is checked
- Every page is scanned by an automated accessibility checker on every release, in Arabic and in English, on all three browser engines we support, and most of the pages around the board on a phone-sized one as well. A failure stops the release rather than filing a ticket. Not in it yet: the screens shown when something crashes, and a handful of surfaces that open on top of the board.
- The Editor, which opens in its own tab, is not yet covered by these automated checks.
- The board has automated keyboard journeys of its own: drawing a link, breaking one, moving a card and running one, each done with the keyboard alone and each run in both reading directions.
- No person who depends on a screen reader has used this product yet. An automated checker finds broken markup; it cannot tell you whether what it reads out makes sense. Until that pass has happened, read the screen-reader claims below as ours rather than as somebody else's verdict.
What works today
- Every screen is in Arabic and in English, and Arabic is the original rather than a translation. The board itself mirrors: work flows right to left, the ports swap sides, and the arrowheads, the auto-layout and the minimap follow.
- Everything on the board is reachable with Tab alone — every card, every control on a card, every port, the rail, the side panels and the dialogs. On a very large board only the cards in view are drawn, and the outline reaches the rest. Where focus is, is always visible.
- A link is drawn from the keyboard: Enter on a port picks one up, Enter on another port or on a card finishes it, Escape puts it back. Delete on a port removes the links at that port.
- A selected card moves with the arrow keys, by the same step a drag snaps to, and further with Shift held. Several nudges in a row are one undo step.
- Every card is announced with a name, what it is doing, and what feeds it and what it feeds. Every port says what it carries and what it is linked to. While a run walks the board, each card is announced as it starts and as it finishes.
- The board is also a list, in the order it runs, with every link on it and a way to jump to any card. Open it from the rail or with the O key.
- Shortcuts are bound to where a key sits rather than to the letter printed on it, so they are the same keys on an Arabic keyboard — and the keyboard help shows both.
- Animation stops for anyone whose system asks for reduced motion.
What does not work yet
- Nobody who relies on a screen reader has driven this product. The labels and the announcements were written, and tested, by people looking at a screen.
- The board is not supported on a phone or on any touch screen, and wiring has no touch equivalent yet. The pages around it open on a phone, but some of them are not yet laid out for a small screen.
- A card is resized by dragging its corner, and there is no keyboard equivalent yet.
- Letting a link go on an empty part of the board offers a list of cards that could take it. That gesture has no keyboard equivalent: from the keyboard, add the card first and then draw the link to it.
- The minimap is for pointers only. The outline, the fit control and moving between cards do the same work from the keyboard.
- A generated image or video carries no description beyond the prompt that made it, generated video has no captions, and generated speech has no transcript.
- Nothing has been checked against Windows High Contrast or any other forced-colours mode.
- Studio's editor has faults the automated check finds that are recorded, not yet fixed: icon controls in its Media tab and its preview toolbar have no name, its project-name field has no label, and its playhead is a control nested inside the timeline ruler, which is a control too.
Tell us about a problem
If something here is wrong, or something you need is missing, tell us. A report about accessibility is treated as a defect and not as a request.
It helps to say: the address of the page, what you were trying to do, which browser you were in, which assistive technology you were using, and which language the interface was in.