Compliance status
This website is partially compliant with the accessibility requirements, due to the non-compliances listed below.
Aletheia targets full conformance with WCAG 2.2 Level AA and with EN 301 549 V3.2.1, the harmonised European standard in force as of the publication date. Partially compliant means that most requirements of the standard are met and that the known exceptions, where content does not yet fully conform, are described in the next section. The complete criterion-level position, against every WCAG 2.2 Level A and Level AA success criterion and against the Revised Section 508 standards, is documented in the VPAT accessibility report.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility requirements
The following limitations are known and are being worked on. They are drawn from the criteria recorded as Partially Supports in the VPAT accessibility report, so that users and buyers can make an informed decision.
- Exported tagged PDF output carries structure tags, alternative text, and reading order, but comprehensive end-to-end verification of the exported PDF with the NVDA, JAWS, and VoiceOver screen readers is planned and has not yet been conducted (affects 1.3.1 Info and Relationships).
- Five WCAG 2.2 criteria are held at Partially Supports pending manual verification that follows automated testing in which they showed no failures. At Level A: 1.3.2 Meaningful Sequence and 2.4.1 Bypass Blocks, together with 1.3.1 Info and Relationships as noted above. At Level AA: 1.4.10 Reflow and 2.4.11 Focus Not Obscured (Minimum).
- 3.3.7 Redundant Entry is met in the marketing flows; a full review of every multi-step flow in the web application and administration dashboards is still pending.
- Exported tagged PDF files carry correct structure for Latin-script content. Non-Latin scripts may show fallback characters in the current build. Plain text export preserves all Unicode content without loss and can be used where non-Latin scripts must be retained exactly.
- Product documentation is expanding, and older articles may not yet follow the same heading discipline as newer ones.
Disproportionate burden
Aletheia does not currently invoke disproportionate burden exemptions for any conformance area.
Content not within scope of the applicable legislation
- Content served to authenticated users under an institutional deployment agreement may be scoped differently per that institution's configuration.
- Content produced by a third-party AI provider under bring-your-own-key credentials is generated by that provider, not by Aletheia. On the Professional tier the provider is called directly from the user's browser; on the Enterprise tier the call is relayed by Lonia's Enterprise Worker using the institution's own enrolled key. In both cases the description text is produced by the third-party provider under the customer's own provider account, and its content is outside Aletheia's control.
Preparation of this accessibility statement
This statement was prepared on July 14, 2026.
The method used to prepare the statement was a self-evaluation of Aletheia against WCAG 2.2 Level AA and EN 301 549 V3.2.1, using automated testing with axe-core across 21 of the product's 26 routes conducted on July 14, 2026, which returned zero critical, serious, or moderate violations, supplemented by manual testing by the Aletheia team covering keyboard navigation, colour contrast, high-contrast mode compatibility, and browser text-size scaling. A formal third-party audit is planned and has not yet been carried out.
The statement was last reviewed on July 14, 2026. It is reviewed at least once a year and on every major product release.
Feedback and contact information
If you find an accessibility barrier in Aletheia, or need information from Aletheia in an accessible format that is not currently provided, please tell us. Aletheia treats accessibility issues as defects, not feature requests.
Email accessibility@lonia.ai.Please include the page or feature where the issue occurred, the assistive technology you were using, and what you expected to happen. We aim to acknowledge accessibility feedback within five business days.
Enforcement procedure
If you contact us about an accessibility barrier and you are not satisfied with our response, you can contact the accessibility enforcement or market surveillance authority designated in your European Union Member State. Examples include:
- France: the Direction générale de la concurrence, de la consommation et de la répression des fraudes (DGCCRF).
- Germany: the market surveillance authority designated under the Barrierefreiheitsstärkungsgesetz (BFSG).
- Netherlands: the Netherlands Authority for Consumers and Markets (Autoriteit Consument en Markt, ACM).
- Sweden: the Swedish Post and Telecom Authority (Post- och telestyrelsen, PTS).
The European Commission publishes the list of national authorities responsible for monitoring and enforcing accessibility requirements in each Member State. Users may also contact the equality body or ombudsman in their European Union Member State.
Compatibility with browsers and assistive technology
Aletheia targets support for the following user agent and assistive technology combinations:
- Chrome with NVDA (Windows).
- Firefox with NVDA (Windows).
- Chrome with JAWS (Windows).
- Safari with VoiceOver (macOS and iOS).
- Chrome with TalkBack (Android).
- Firefox with Orca (Linux).
Technical specifications
Accessibility of Aletheia relies on the following technologies to work with the combination of a web browser and any assistive technologies or plugins installed on your computer:
- HTML5.
- CSS3.
- JavaScript (ES2022).
- WebGPU, with a CPU fallback.
Assistive technology compatibility relies on standard accessibility interfaces: ARIA, WAI-ARIA 1.2, and HTML5 semantics.