Accessibility statement
DiagramDock targets WCAG 2.2 AA. A diagram editor is a genuinely hard case for accessibility — the primary interface is a spatial canvas — so this statement includes what is not yet done as well as what is.
What is implemented
Keyboard alternatives for canvas actions, including creating, connecting, styling and deleting elements without a mouse. Visible focus indicators throughout. Semantic controls with accessible names. Dialogs that trap and restore focus. Reduced motion honoured via prefers-reduced-motion. A contrast checker that warns when node text falls below AA against its fill, without preventing the choice.
Diagram descriptions
Diagrams and individual elements can carry text descriptions. These are written into exported SVG as title and desc elements, so an exported diagram carries its own alternative text rather than relying on whoever embeds it.
Colour
Colour is never the only carrier of meaning in the interface. Diagram content is under your control, and the contrast checker will tell you when a combination is likely to be hard to read.
Known gaps
Being specific rather than reassuring: a full audit with assistive technology across every route has not yet been completed. Canvas interaction with a screen reader is functional but has not been tested with real users of screen readers, which is a different and higher bar. Complex diagram types — sequence diagrams in particular — have keyboard support that is less complete than the flowchart editor. On phones, the editor is usable for viewing and simple edits, but the style panel is hidden and there is no dedicated touch layout yet. These are gaps, not features, and they will be listed here until they are closed.
Feedback
If something is inaccessible, please tell us — accessibility reports are prioritised. The contact page has a category for exactly this.