Accessibility
Accessibility at Lumeo
Lumeo aims to make document tools usable across different devices, input methods, and assistive technologies.
Last updated: July 11, 2026
Lumeo does not currently claim formal WCAG certification. Accessibility is treated as an ongoing product responsibility.
Current design approach
- Keyboard-accessible controls where tool interactions require them.
- Visible focus states for key navigation and action controls.
- Semantic headings and page landmarks on public pages.
- Accessible labels for icon-only navigation.
- Touch-friendly targets and responsive mobile layouts.
- Reduced-motion support where implemented.
- Contrast-conscious Midnight Notary palette.
- Error messages that do not rely only on colour.
Known limitations
- Complex PDF previews may not yet communicate all page content to assistive technology.
- Third-party PDF rendering libraries may have accessibility limitations.
- Some advanced document interactions may require further keyboard and screen-reader refinement.
- Large document workflows can be constrained by browser and device capabilities.
Feedback
Accessibility feedback is welcome, especially when a workflow is difficult to complete with a keyboard, screen reader, magnification, touch input, or reduced-motion preference.
Improvement model
New tools should be reviewed for keyboard access, mobile usability, focus management, error recovery, semantic structure, reduced motion, and colour-independent state communication.