Jumbly legal
Accessibility
Jumbly's current accessibility direction, including keyboard support, mobile usability, reduced motion, contrast, and beta limitations.
Last updated: May 11, 2026
These pages describe the current Jumbly closed beta and planned platform features in plain language. We will keep them updated as accounts, analytics, subscriptions, and wider launch systems mature.
Accessibility Commitment
Jumbly should feel polished, playful, and usable. The goal is to keep improving keyboard support, readable contrast, reduced motion behavior, labels, touch targets, and screen-reader support without losing the calm premium feel.
Keyboard Support
- Core navigation, footer links, legal pages, modals, buttons, and form controls should remain keyboard reachable.
- Word and grid games should provide practical keyboard controls where the interaction model supports it.
- Focus states should be visible enough to navigate confidently in dark mode.
Mobile Accessibility
- Jumbly is designed mobile-first with large touch targets, safe-area-aware layouts, and thumb-friendly controls.
- Game boards should avoid tiny controls, hidden essential actions, and layouts that depend on hover.
- Mobile Safari and installed PWA behavior should be tested regularly because many players will use iPhones.
Reduced Motion
- Animations should be subtle, purposeful, and respectful of reduced-motion preferences.
- Tile flips, mascot moments, modals, route transitions, and celebration effects should avoid becoming disorienting.
- Reduced-motion handling exists in the codebase and should be preserved as new games are added.
Contrast and Color
- Dark mode should maintain readable text, clear focus states, and enough contrast for important controls.
- Puzzle feedback should not rely on color alone where practical; labels, symbols, aria text, or visible state changes should reinforce meaning.
- Green, yellow, and dark feedback states should stay legible across mobile screens and brightness settings.
Known Beta Limitations
- Some highly visual game boards may need stronger screen-reader semantics and non-color feedback.
- Complex drag, swipe, path, and spatial puzzle interactions may need alternate input paths before broad accessibility claims.
- Automated accessibility testing and manual assistive technology checks should be added before public scale.
Feedback
If something is hard to read, navigate, hear, understand, or operate, contact support@jumbly.games with the game, route, device, browser, and what blocked you.