Accessibility
Last updated 9 October 2026
In plain words
Glimby is built for brains that work differently, so we want it to work for every body and setup too. We aim to meet WCAG 2.2 at level AA. If something gets in your way, tell us and we’ll treat it as a bug.
What you can expect
- Everything works with a keyboard, with a visible focus outline and a “skip to content” link.
- Pages use real headings, landmarks and labels, so screen readers can find their way around.
- Text and controls meet AA contrast in both light and dark themes.
- Text can be zoomed to 200% and the layout reflows on narrow screens, down to 320 pixels.
- Buttons and links are large enough to tap (at least 24 by 24 pixels, most 40 or more).
- Animations stop when your device asks for reduced motion, and sounds and vibration can be turned off.
- Anything you can do by dragging, like reordering Today, also has a button.
- Time limits are never forced: focus timers can be paused or stopped at any point.
Known limitations
- The companion’s glow is decorative; its meaning is always written out too, but the animation can’t be described in detail.
- Some charts in Patterns are summarised in text rather than exposed point by point.
How we check
Automated checks (axe) run on every change in our test suite, alongside manual checks with a keyboard and browser zoom. This statement was last reviewed on 9 October 2026.
Tell us
If you hit a barrier, write to hello@glimby.app or use Settings → Feedback. Tell us the page and what happened if you can. We aim to reply within five working days and to fix barriers as a priority.