Aletheiaby Lonia AI

Accessibility

Accessibility is the product, not a feature.

Aletheia exists to remove accessibility barriers from other people's content, so the tool itself has to meet the standards it helps people enforce. This statement describes what we commit to, what we have built, what is still imperfect, and how to tell us when something is wrong.

Last updated: June 18, 2026

Conformance commitment

Aletheia targets WCAG 2.2 Level AA as the floor, not the ceiling, and aligns with Section 508 for users in U.S. federal contexts. We aim higher where it does not break essential functionality. Both this marketing site and the Aletheia product are built to this standard from the first release.

Specific measures

  • Every page has a skip-to-content link as the first focusable element.
  • All interactive elements have visible focus indicators of at least 3 pixels with offset.
  • Color contrast meets at least 4.5:1 for normal text and 3:1 for large text.
  • Color is never the sole indicator of meaning. State is also conveyed with text, icons, or position.
  • Semantic HTML is used throughout, with ARIA added only where semantic HTML is insufficient.
  • Headings follow a logical hierarchy, with one H1 per page.
  • Every form field has an associated label, visible or available to screen readers.
  • Errors are announced and described next to the field they belong to.
  • The full site can be operated with a keyboard alone. 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 with NVDA, JAWS, and VoiceOver.

Known limitations

Accessibility is an ongoing effort, not a finished checkbox. We acknowledge areas we are still improving:

  • Documentation for advanced features is expanding, and older articles may not yet have the same heading discipline as newer ones.
  • Any future media will ship with captions and audio description alongside the media itself.

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 [email protected] with "Accessibility" in the subject line, or write to [email protected]. Please include:

  • The page or feature where you encountered the issue.
  • The assistive technology you were using, such as a screen reader, voice control, switch device, magnifier, or 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

Aletheia holds itself to a standard much of the industry treats as optional. The standard does not lower because shipping was hard. If a feature cannot be built accessibly, it does not ship.

Have a question?