Trust
Accessibility
Accessibility is something we build into the product, not a statement we publish instead of it. This page describes what we do today and where we still have work to do — honestly, not aspirationally.
What we do today
- Semantic HTML and ARIA labeling on interactive controls (buttons, menus, dialogs) throughout the product.
- Visible keyboard focus states, and modals that trap and restore focus correctly when opened and closed.
- Descriptive alt text on meaningful images; decorative elements are hidden from screen readers.
- Form fields paired with real
<label>elements, not placeholder text alone. - Respect for
prefers-reduced-motion— animations are minimized for users who’ve requested it at the OS level. - A color system built for sufficient contrast between text and its background.
Where we still have work to do
EnlightIn is under active development, and accessibility is an ongoing practice, not a box we check once. If you hit a genuine barrier — a control that doesn’t work with a screen reader, a contrast issue, a keyboard trap — we want to know about it and fix it.
Tell us about a problem
If you encounter an accessibility barrier anywhere on EnlightIn, please contact us with the page and what happened. We treat these reports as real product bugs, not feedback to file away.