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.
- Screen reader compatibility of exported tagged PDF files is still under testing. Formal test evidence with NVDA and JAWS against exported PDF output is pending.
- Exported tagged PDF files carry proper structure tags, alternative text, and outlines 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.
- 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.
- Product documentation is expanding, and older articles may not yet follow the same heading discipline as newer ones.
- No prerecorded or live synchronised media is present on any surface. Any future media will ship with captions and audio description alongside the media itself.
5 WCAG 2.2 success criteria are held at Partially Supports rather than Supports. In each case automated testing showed no failures and manual verification is still to follow, or a specific export path is still being verified.
| Criterion | Level | Reason held |
|---|---|---|
| 1.3.1 Info and Relationships | A | Held pending end-to-end screen reader verification of exported PDF output. |
| 1.3.2 Meaningful Sequence | A | Held pending manual verification after automated testing showed no failures. |
| 2.4.1 Bypass Blocks | A | Held pending manual verification after automated testing showed no failures. |
| 1.4.10 Reflow | AA | Held pending manual verification after automated testing showed no failures. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Held pending manual verification after automated testing showed no failures. |
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, supplemented by manual testing by the Aletheia team covering keyboard navigation, colour contrast, high-contrast mode compatibility, and browser text-size scaling. A formal audit by an independent third party is planned and has not yet been carried out.
Automated testing produced two separate evidence records, one per surface. They are named individually here because their route counts are similar and they have previously been read as one record.
- Aletheia marketing website (this site): axe-core 4.12.1, October 16, 2026, covering all 31 public routes of the site revision named beside it. Zero violations at every severity across the full WCAG 2.0, 2.1, and 2.2 Level A and AA rule sets plus axe best-practice rules. The results axe records as incomplete rather than pass or fail are colour-contrast checks that axe cannot compute against the site's background gradient; they are resolved separately by measuring the rendered pixels, and that resolution is committed alongside the sweep. Evidence:
test-results/axe/m17-2026-10-16/One JSON record per route plus _aggregate.json, committed to this repository. Each record carries the page title the origin served at scan time, so a reader can confirm the sweep ran against Aletheia and not against another site sharing the preview port. None. The route set is derived from src/pages by scripts/lib/routes.mjs and the build fails if committed evidence does not cover every route. Site revisionc2b6329aa097. - Aletheia web application and admin dashboards: axe-core, September 20, 2026, covering 73 runs across desktop and mobile viewports, including the Settings route that carries the data-export control. Zero violations. Evidence: test-results/axe/a11-2026-09-20/ in the Aletheia application repository. Held in the application repository and not committed here, which is why it is named separately from the marketing-site record. The batches before it were a13-2026-09-20 and a12-2026-09-19; five tracked batches exist since the July 14, 2026 sweep, and this record cites the latest.
The statement was last reviewed on October 4, 2026. It is reviewed at least once a year and on every major product release.
Change history
| Date | Version | Change |
|---|---|---|
| October 4, 2026 | 1.4 | The automated-evidence sentence now names the site revision the sweep covered instead of calling it the current build, and cites the sweep re-run on October 4, 2026. A sentence that says "current" re-asserts itself on every build without anyone deciding to, which is how the previous one came to describe a build ten commits newer than the audit behind it. |
| September 17, 2026 | 1.3 | Contact address consolidated to support@lonia.ai. |
| August 26, 2026 | 1.2 | Compatibility list corrected to tested platforms only. Added an explicit list of the platforms Aletheia has not been tested on, distinguished the combinations actually tested from those that are targets of support, and stated who carries out the manual testing, on what, how, and since when. |
| August 23, 2026 | 1.1 | Separated the two automated evidence records, which were previously cited as one with confusingly similar route counts, and named the artifact backing each. Re-ran the marketing-site sweep against every route in the current build, including the one route the previous run never covered. Non-accessible content is now rendered from a shared record so this statement, the EAA statement, the VPAT, and the consumer accessibility statement cannot diverge. |
| July 14, 2026 | 1.0 | Initial publication in the Commission Implementing Decision (EU) 2018/1523 template. |
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 support@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).
- Chrome with TalkBack (Android).
- Firefox with Orca (Linux).
Of these, the combinations that have actually been tested are Chrome with NVDA on Windows 11 and Chrome with TalkBack on Android. The rest are targets of support, built to the same standard accessibility interfaces, and not yet exercised in a testing session. The platforms named in the next section have not been tested at all.
Platforms not tested
Aletheia has not been tested on Apple platforms. No iOS, iPadOS, or macOS device, no version of Safari, and no VoiceOver session has been part of any testing pass to date. Aletheia is a standards-based web application and is expected to work there, but an expectation is not evidence, and nothing published here should be read as a claim that it has been verified on those platforms.
- iOS and iPadOS, on any device.
- macOS, on any device.
- Safari, on any platform.
- VoiceOver, on any platform.
- JAWS. JAWS is named as a support target because the product is built to the interfaces JAWS uses, and no JAWS session has been run.
Tested platforms are listed above and are limited to Windows 11 with NVDA and Android with TalkBack.
If you use one of these platforms and hit a barrier, tell us at support@lonia.ai. A report from an untested platform is more useful to us than one from a tested platform, and it is treated as a defect.
Manual testing
Manual testing is carried out by the Lonia AI product team on Windows 11 with NVDA and on Android with TalkBack, iteratively during development rather than as a single scheduled audit, continuously since May 2026. It covers targeted keyboard navigation, WCAG 2.2 Level AA colour contrast, responsive layout, high-contrast mode, and confirming that each accessibility setting changes real behaviour. The fix commits in the Aletheia application repository are the audit trail; there is no separate manual-testing report and none is claimed.
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.