Accessibility
Last updated: July 2026
One path, no dead ends. That is the idea behind the name, and it applies to who can use this too.
Where this stands
Labyrinth is done solo. Accessibility is part of the build, not something bolted on later, but it is unfinished. This page says what has actually been checked and what has not. It gets updated as that changes.
Confirmed
- Plain text data. Notes are stored as standard .md files, so they can be opened in whichever editor works for you, including one built for your own setup.
Being tested
These are in the build and under audit now. None are claimed as supported until each has been walked end to end on a real device.
- VoiceOver on iPhone and Mac
- Voice Control on iPhone and Mac
- Reduce Motion
- Keyboard navigation on Mac
Known limitations
- Text does not yet scale fully with Dynamic Type. Some sizes are fixed and will not respond to your system text size setting.
- Some controls have tap targets smaller than the 44pt minimum.
- Some secondary text sits below the contrast ratio it should meet.
- Moving a task between board columns relies on drag, which is harder without a pointer or touch. Other ways in are being added.
- Tag chips carry colour, but the tag name is always shown alongside, so colour is never the only signal.
This website
Semantic HTML, visible keyboard focus, no motion-dependent content. Every page works without JavaScript except the contact form.
Feedback
Shake your device inside the app to send a report, open an issue on GitHub Discussions ↗, or get in touch directly.
If something in Labyrinth or on this site is difficult or impossible to use, please do tell.
Standards
Labyrinth works towards WCAG 2.1 Level AA and follows Apple's Human Interface Guidelines for accessibility. This is a self-assessment, not an independent audit.