Accessibility Statement

Effective date: August 22, 2026 · Version 3.1

In short: We want everyone to be able to use Diagramium, and we design toward WCAG 2.1 Level AA as our target. We are not fully there yet. Presentations narrate aloud by default, with the spoken text shown at the same time in the notes panel and highlighted word by word as it is read; most menus and dialogs work by keyboard, and reduced-motion settings are respected — but drag-and-drop diagram editing on the canvas is not yet fully usable by keyboard or screen reader. This page says honestly what works, what does not, and how to reach us if you hit a barrier: admin@dhureelabs.com.

Scope

This statement covers the Diagramium service: the diagram editors, the Explore template gallery, Present mode, and our public website pages. Diagramium is operated by DhuRee Labs Inc. ("we", "us", "our"), a company based in Ontario, Canada.

Our commitment

We are committed to making Diagramium usable by as many people as possible, including people who use assistive technology, keyboard-only navigation, captions, or reduced motion. Accessibility is part of how we design and build, not an afterthought. When we learn about a barrier, we treat it as a defect to be fixed.

Nothing in this statement limits any rights you have under the Accessibility for Ontarians with Disabilities Act, 2005 (AODA), the Ontario Human Rights Code, or any other accessibility or human-rights law that applies to you.

The framework we follow

We operate from Ontario, Canada. We comply with the accessibility obligations applicable to our organization, and we voluntarily use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our design target. This is a target we are working toward, not a claim of current conformance. The sections below describe our real, current position.

Current status

Diagramium does not yet fully conform to WCAG 2.1 Level AA. Some parts of the product meet many of its requirements; the diagram canvas in particular does not. We prefer to state this plainly rather than publish a conformance claim we cannot support.

What works today

Keyboard access to the app's controls. Menus, dialogs, toolbars, settings panels, the command palette (Ctrl/Cmd+K), and the Explore template gallery can be operated by keyboard. Template cards can be focused and opened with Enter. When a popover closes, focus returns to the control that opened it.
Visible focus indicators on interactive controls throughout the interface.
Present mode is fully keyboard-operable once started. Arrow keys and Page Up/Page Down move between steps, Space plays and pauses, Home and End jump to the first or last step, and Escape exits. An in-app overlay lists the presentation shortcuts.
Captions for narration, on by default. Spoken narration in Present mode is accompanied by on-screen subtitles, with an optional word-by-word highlight. Subtitles can also be burned into video exports.
Narration audio as an alternative modality. Step notes are read aloud in Present mode. Where a tour ships pre-produced studio narration (synthesized speech) we play that; otherwise your browser's built-in speech synthesis reads the note. Narration is on by default and every part of it is one click from off: mute, the narration toggle, and the bottom-subtitle and word-highlight switches all persist your choice. Whether narration is on or off, the same text is always visible in the notes panel. Background music and sound effects are off by default.
Reduced motion is respected. When your system asks for reduced motion, the app disables its presentation transitions, landing-page effects, and other scripted and CSS animations.
Light and dark themes with a persistent toggle. (Present mode's chrome intentionally stays dark in both themes.)
Zoom is not blocked. Browser zoom and pinch-zoom work normally; the app does not disable user scaling.
Semantic structure and ARIA. Pages declare their language; dialogs carry dialog roles and accessible names; toggles expose their pressed or checked state; segmented controls use radio-group semantics; decorative images are hidden from assistive technology; content images on the website carry descriptive alt text. Website pages use header, navigation, and footer landmarks with a heading hierarchy.
Text-based authoring for some diagram types. For sequence, org chart, mind map, and sitemap diagrams, the Text editor tab lets you author the entire diagram as plain text, entirely by keyboard, in sync with the canvas. A plain-text export exists for those diagram types and several others.
Editing shortcuts. Undo/redo, Delete to remove a selection, and Escape to close dialogs work across the editors. In six graph-style editors (process map, decision tree, architecture, data flow, network, fishbone), a selected shape can be nudged with the arrow keys and copied, pasted, duplicated, or grouped from the keyboard.
No time limits and no flashing content. Presentation playback is user-started and can be paused at any time.

Known limitations

We list these honestly so you can decide what will work for you:

Canvas editing needs a pointer. Creating and selecting shapes on the drawing canvas is drag-and-drop and click based. Diagram elements on the canvas are not in the keyboard tab order, so a diagram cannot currently be built or edited by keyboard alone on the canvas itself.
The keyboard-only authoring path does not cover every diagram type. The Text editor alternative currently exists for four diagram types (sequence, org chart, mind map, sitemap). An earlier version of this statement described a "complete keyboard-only authoring path"; that was an overclaim, and this statement corrects it.
Plain-text export is not available for every diagram type (currently missing for flowchart, state machine, swimlane, timeline, and journey map diagrams).
Screen reader support is limited. The app does not yet announce step changes, notifications, or captions to assistive technology; Present-mode subtitles are visual-only and are currently hidden from screen readers; and the rendered diagram graphic does not yet expose an accessible name or image role.
No skip-to-content link, and the main app page does not yet use a main landmark.
No dedicated high-contrast or forced-colors mode. We have not yet completed a measured colour-contrast audit of our themes, so we do not claim conformance with WCAG's contrast criteria.
A correction: earlier versions of this statement said the app had "no audio." That is out of date. The app now offers optional narration audio and optional background music — always with on-screen captions available and always under your control.

What we suggest in the meantime

For keyboard-only authoring, use the Text editor tab with the sequence, org chart, mind map, or sitemap diagram types.
Ready-made templates and narrated tours can be enjoyed without any canvas editing: open one from Explore and use Present mode, which is fully keyboard-operable, narrates aloud by default, and always shows the narrated text in the notes panel.
Where a plain-text export exists for your diagram type, it provides a text alternative to the rendered graphic.
If none of these work for your situation, contact us and we will help, including providing content in an alternate format where we reasonably can: admin@dhureelabs.com.

Ongoing work

We are actively working to close the gaps listed above, prioritizing the barriers that block the most users. As improvements ship, we update this statement to match the product's real state.

Feedback and alternate formats

We welcome feedback on the accessibility of Diagramium, and we treat reported barriers as priorities. Email us at admin@dhureelabs.com; if email itself presents a barrier, tell us in whatever way works for you and we will accommodate. We aim to acknowledge accessibility feedback within 5 business days.

On request, we will provide or arrange accessible formats and communication supports — both for this statement and for the feedback process itself — in consultation with you, at no extra cost.

Compatibility

Diagramium is a web application and runs in modern desktop and mobile browsers. Some conveniences (such as saving directly back to a file on disk) depend on browser support and fall back to a standard download where unavailable.
Spoken narration uses your browser's built-in speech synthesis, so available voices and languages depend on your browser and operating system.

About this statement

Prepared August 5, 2026; last revised August 22, 2026. We review this statement at least annually and after significant feature releases that affect accessibility.