Accessibility statement

We want everyone on a team to read the map, follow a flow and work the board, with a mouse, a keyboard, a screen reader, speech input or zoomed to 400%. This page says how far we are, what doesn't work yet, and how to tell us.

Last reviewed 12 November 2026 · applies to rabbinatix.com and the Rabbinatix app

Our standard

We follow the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which is also the level of EN 301 549 and most accessibility laws.

Status: partially conformant. Most of the product meets WCAG 2.2 AA, including the visual editors: the system map has a table view, the flow and logic canvases and whiteboards have an outline and work with the keyboard, and almost every drag has a menu, field or key instead. A few gaps remain; they are listed under known exceptions below, with what to use instead today.

What works

  • Every page has a “Skip to main content” link, landmarks, one h1 and headings in order.
  • Everything works with the keyboard: menus, dialogs, drawers, tabs, selects, the board, chat and reports. Dialogs keep focus inside and give it back when they close.
  • The canvases too: Tab into a flow or logic canvas and use the arrow keys to go from step to step in the order they run; Enter opens a step, C connects it to another step from a list, Delete removes it (and Undo brings it back).
  • Whiteboards too: Alt and the arrow keys go from shape to shape, Space selects several, the arrow keys move them, C draws an arrow to a shape picked from a list, and each shape’s menu sets its size and position with fields.
  • Inspect, for a screen’s design, has a Layers list: pick a widget with the arrow keys and Enter, and “Measure to…” another to hear the distances in words.
  • Every canvas has a text alternative: an outline of the flow or logic (and its text steps), an outline of every whiteboard, and a table of the systems and connections for the map.
  • Nothing needs dragging (except bending a whiteboard arrow, below): board columns and cards have Move menus, timeline dates have fields and arrow keys, map systems and whiteboard shapes move with the arrow keys, and panels resize with the arrow keys.
  • One visible focus ring on every control, never hidden behind sticky headers or messages.
  • Text and controls meet WCAG contrast in both light and dark themes.
  • Status never relies on colour alone: contract and flow statuses have an icon and a word, every report chart has a table view, and each type of connection point on a logic canvas has its own shape (the key is in the canvas controls and under the node palette).
  • Connection points, handles and labels on the canvases keep a target of at least 24 by 24 pixels at every zoom level.
  • Saves, run results, validation errors and counts are announced to screen readers.
  • Pages reflow to 320px wide and to 400% zoom; only the canvases and wide tables scroll sideways.
  • Sign-in works with password managers and paste, with no puzzles or memory tests.
  • Single-letter shortcuts can be turned off in Settings → Appearance, and animations stop when your system asks for reduced motion.

Known exceptions

These work, with a gap we know about ("partial" in our checklist). Each has a way round it today and a planned fix.

Known accessibility exceptions, their WCAG criteria and workarounds
WhereWCAGWhat doesn't work yetUse instead
Flow and logic canvases1.4.12 Text spacingWith extra letter, word and line spacing, long step names on the canvas are cut short.The full name is the step’s accessible name, and it is in the Outline view.
System map, flow and logic canvases2.1.1 KeyboardKeyboard use differs from canvas to canvas: the logic canvas has the most keys, the flow canvas moves between its rows, the map moves systems and pans with the arrow keys. It hasn’t had the manual screen reader pass yet.The Outline view (flows, logic) and the Table view (map), and each step’s menu (Shift+F10).
System map, logic canvas, timeline2.5.7 Dragging movementsEvery drag has another way, but placing a system or step at an exact spot takes several key presses or a form instead of one drag.Arrange automatically on the map; Ctrl or ⌘ and the arrows (with Shift for bigger steps) on the logic canvas; date fields in the timeline’s List view.
Whiteboards2.1.1 Keyboard, 2.5.7 Dragging movementsShapes work fully from the keyboard, but an arrow can only be chosen by its label (Find), and bending an arrow or moving its end to another shape still needs dragging. The keyboard support is new and hasn’t had the manual screen reader pass yet.Find (Ctrl+F) selects a labelled arrow, and Enter (after Esc closes Find) edits its label; to move an arrow’s end, Disconnect it in Connect to… and connect the right shape instead. The Outline tab lists where every arrow goes.

How we check

  • Every page is scanned with axe-core in light and dark, at desktop and phone width, on every change. Serious issues block the release.
  • Colour tokens are checked by an automated test: 4.5:1 for text and 3:1 for controls, focus rings and chart colours, in both themes.
  • The main keyboard journeys (sign-in, navigation, the board, dialogs, the command palette, chat, settings) run as automated keyboard-only tests on every change. Before each release they are also done by hand with NVDA and Firefox on Windows, and with VoiceOver and Safari on macOS.
  • We test in current Chrome, Edge, Firefox and Safari. The app needs JavaScript.

Report a problem

If something stops you, or takes much longer than it should, please tell us. Say which page, what you tried, and the browser and assistive technology you use. We reply within two working days and tell you when it's fixed. If you need information from the app in another format, ask, and we'll send it.

If you're not happy with our answer, you can complain to the body that oversees digital accessibility in your country.