Conformance commitment
Aletheia targets WCAG 2.2 Level AA as the floor, not the ceiling. We aim for AAA where it does not break essential functionality, and we align with Section 508 for users in U.S. federal contexts. The marketing site you are reading meets WCAG 2.2 AA. The product, when it launches, will meet the same standard from its first release.
Specific measures
- Every page has a skip-to-content link as the first focusable element.
- All interactive elements have visible 3 pixel focus indicators with 3 pixel offset.
- Color contrast meets 4.5:1 for normal text and 3:1 for large text. Critical UI uses 7:1.
- Color is never the sole indicator of meaning. State changes also use icons, text, or position.
- Semantic HTML is used throughout. ARIA is added only where semantic HTML is insufficient.
- Headings follow a logical hierarchy. One H1 per page. H2s nested under it. H3s under H2s.
- Every form field has an associated label, either visible or visually hidden but available to screen readers.
- Errors are announced through role="alert" and described next to the field they belong to.
- The full site can be operated using only a keyboard. Tab, Shift+Tab, Enter, Space, and Escape behave as expected.
- Mobile touch targets are at least 44 by 44 pixels.
- Animation and transitions respect prefers-reduced-motion.
- The site has been tested in NVDA, JAWS, and VoiceOver.
Known limitations
Accessibility is an ongoing effort, not a checkbox. We acknowledge there are areas where we are still improving:
- Some third-party content embedded on future product pages may not yet meet our standards while we evaluate alternatives.
- Documentation for advanced features will be added as the product grows. Older articles may not yet have the same heading discipline as new ones.
- Live captioning and audio descriptions for any future video content will roll out alongside the videos themselves.
If you find a barrier we have not listed, please tell us. We treat accessibility issues as bugs, not feature requests.
Report an accessibility issue
Email admin@lonia.ai with "Accessibility" in the subject line. Please include:
- The page or feature where you encountered the issue.
- The assistive technology you were using (screen reader, voice control, switch device, magnifier, keyboard only).
- What you expected to happen and what actually happened.
We respond to accessibility reports within five business days and prioritize fixes ahead of feature work.
Closing
Accessibility is an ongoing effort, not a checkbox. The standard does not lower because shipping was hard. If a feature cannot be built accessibly, the feature does not ship. That is the rule we hold ourselves to, and the rule we expect to be held to.