Accessibility Statement
Our approach
The public form renderer is built accessible by default: visible focus states, logical reading and tab order, landmark navigation, live-region announcements for validation and progress, accessible names on every control, and support forprefers-reduced-motion. Dashboard surfaces follow the same conventions, including target sizes, contrast-checked palettes, and full keyboard operability of the builder and submissions views.
Forms you publish are rendered by this accessible renderer, but the accessibility of a form’s content — its labels, options, language, and required media — is controlled by its creator. Our Terms allocate that responsibility to the form owner, and the builder surfaces guidance (required markers, error association, alternative text on branding) to help owners publish accessible forms.
Current status and known limitations
Lumina is in public beta. Accessibility work is ongoing: we run targeted checks on each release (keyboard traversal, contrast ratios, landmark and live-region behavior, mobile viewports down to 360 px), but no independent third-party audit has been completed yet, so we state a target rather than a certification. Known limitations, where they exist, are tracked and fixed as part of normal development.
Report a barrier
If you encounter an accessibility barrier, email legal@luminaforms.app with the page URL, what you were trying to do, and the assistive technology or browser you used. We will respond within a reasonable time and work to remove the barrier.
Supported assistive technology
We test against current versions of major screen readers (VoiceOver on macOS/iOS, TalkBack on Android, NVDA and JAWS on Windows) in combination with Chrome, Safari, Edge, and Firefox, and against keyboard-only and switch-access navigation.