Trust
Accessibility statement
We aim for WCAG 2.2 level AA. This statement is a self-assessment. Maplivo has not yet had an independent audit or published a VPAT, and the known gaps are listed below.
Last updated 28 September 2026
Keyboard
Every map action works without a mouse.
| Action | Keys |
|---|---|
| Add a subtopic / a sibling / a sibling above | Tab / Enter / Shift+Enter |
| Move between topics | Arrow keys |
| Rename a topic | F2 |
| Open the topic's notes | Ctrl/Cmd+Enter |
| Collapse or expand a branch | Space |
| Go to any topic or map | Ctrl/Cmd+P |
| All commands | Ctrl/Cmd+K |
| Resize a topic | Focus its edge grip, then the arrow keys |
| See every shortcut | ? |
Screen readers
- The Outline panel presents the whole map as a navigable tree, with the same structure as the canvas.
- Buttons and controls have text labels, for example “New subtopic from Budget”.
- Topic status, owner, due date and progress have text names (“Status: In progress”, “Due 3 Oct, overdue”).
- Save status and errors are announced.
Vision and motion
- Light and dark themes designed for readable contrast.
- Status is shown by icon and text, never by colour alone.
- Browser zoom and canvas zoom both work, and topics can be resized.
- Animations are switched off when your system asks for reduced motion.
- Touch targets on phones are at least 44 × 44 pixels.
Known limitations
- Drawing a free connection between two topics needs a pointer; use Links and mentions to connect topics by keyboard.
- Moving a topic to an exact spot on the canvas needs a pointer; automatic layouts and the Outline panel are keyboard alternatives.
- Map images (PNG, SVG, PDF) are pictures. Use the Markdown, OPML, Word or HTML exports for accessible documents.
- Maplivo has not yet been tested with every screen reader and browser combination. Please report anything that doesn't work.
Report a barrier
Use the Feedback button, choose Bug and describe what you were doing and which assistive technology you use. We treat accessibility barriers as bugs.