Accessibility is a right, not a feature.

Standards 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 hold ourselves to a higher bar where it does not break essential functionality. Both this marketing site and the Aletheia product are built to this standard from the first release.

Conformance status

Self-evaluation. No third-party accessibility audit has been conducted, and no SOC 2 or comparable certification is claimed. A formal audit by an independent third party is planned and has not yet been carried out.

Automated testing of this marketing site with axe-core 4.12.1 on October 16, 2026 covered 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. The evidence is at test-results/axe/m17-2026-10-16/ in the site repository. 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. Site revision c2b6329aa097.

The Aletheia web application and the admin dashboards are a separate surface with a separate evidence record: axe-core on September 20, 2026, across 73 runs across desktop and mobile viewports, including the Settings route that carries the data-export control, which found no critical, serious, or moderate violations. It lives in the test-results/axe/a11-2026-09-20/ in the Aletheia application repository. The two records are named apart because their route counts are close enough to be mistaken for each other.

European Accessibility Act (EAA)

For users and buyers in the European Union, Aletheia publishes a separate conformance statement under the European Accessibility Act (Directive 2019/882). It sets out the conformance basis, known exceptions, assistive technology compatibility, feedback contacts, and the enforcement procedure for EU Member States. Read the European Accessibility Act (EAA) Conformance Statement.

For a clause-by-clause technical view, Aletheia also publishes an EN 301 549 Conformance Mapping. It maps the product against the harmonised European standard V3.2.1 and each WCAG 2.2 Level AA success criterion, and records preparation for EN 301 549 V4.1.1.

For EU public sector procurement, Aletheia publishes an EU Accessibility Statement following the mandated template of Commission Implementing Decision (EU) 2018/1523, with the compliance status, non-accessible content, feedback contacts, and enforcement procedure in the order that template requires.

Voluntary Product Accessibility Template (VPAT)

For procurement teams in U.S. federal, state, and higher-education contexts, Aletheia publishes an Accessibility Conformance Report in the ITI VPAT 2.5 format. It records Aletheia's honest conformance status against every WCAG 2.2 Level A and Level AA success criterion and against the Revised Section 508 standards, with per-surface remarks and known limitations disclosed. Read the VPAT accessibility report in your browser, or download the tagged PDF for your procurement records.

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.
• Interactive targets meet the WCAG 2.2 Level AA minimum of 24 by 24 pixels. Inline targets that would fall below that size qualify under the spacing exception, with an 18 pixel gap between adjacent links. The mobile navigation menu meets 44 by 44 pixels, which is the Level AAA target size.
• Animation and transitions respect prefers-reduced-motion.
• The site is built for the NVDA and JAWS screen readers on Windows and TalkBack on Android. NVDA and TalkBack are the two that have been tested. The platforms that have not been tested are listed below.

Known limitations

Accessibility is an ongoing effort, not a finished checkbox. These are the places Aletheia does not yet fully meet the standard, in plain language. The same list, in criterion-level form, is in the VPAT, the EAA Conformance Statement, and the EU Accessibility Statement; all four pages are generated from one record, so none of them can quietly say less than the others.

• Screen reader testing of the tagged PDF files Aletheia exports is not finished. The tags, alternative text, and reading order are written into the file; formal testing with NVDA and JAWS against that output is still pending. Plain text export is available in the meantime and loses nothing.
• Exported tagged PDF files handle Latin-script content correctly. Non-Latin scripts may show fallback characters in the current build. Plain text export keeps every character exactly as it was.
• Nothing on this site asks you to type the same information twice. A full pass over every multi-step flow inside the web application and the admin dashboards has not been completed.
• Product documentation is still growing, and older articles may not use headings as consistently as newer ones.
• There is no audio or video anywhere in Aletheia today. If any is ever added, it ships with captions and audio description at the same time, not afterwards.

Criteria held short of full conformance

5 WCAG 2.2 success criteria are recorded as Partially Supports rather than Supports. In each case automated testing found no failures and a person still has to confirm the result by hand, or a specific export path is still being verified. Nothing here is a criterion we believe we are failing; each is a criterion we have not finished proving.

For the full criterion-level record, including every criterion that is met, read the VPAT accessibility report or download the tagged PDF.

If you find a barrier we have not listed, please tell us. We treat accessibility issues as bugs, not feature requests.

How this was tested

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.

Report an accessibility issue

Email support@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, such as a screen reader, voice control, switch device, magnifier, or keyboard only.
• What you expected to happen and what actually happened.

We acknowledge accessibility reports within five business days. Acknowledgement is a reply from a person, not a resolution time.

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.

Change history