Accessibility Statement

Version 1.3 · Effective 2026-09-29 · Last reviewed 2026-09-29

The short version. We aim to make the Service usable for everyone. Our target is WCAG 2.2 Level AA conformance and the EU's EN 301 549 standard. We are not yet fully there. If you encounter an accessibility barrier, email contact@eltria.de and we will work to fix it.

1. Our commitment

Eltria UG (haftungsbeschränkt) is committed to building a Service that works for people with a wide range of abilities. We treat accessibility as part of the product, not an afterthought. We aim to conform to:

WCAG 2.2 Level AA: the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.2, Level AA conformance.
EN 301 549: the European Harmonized Standard for ICT accessibility, which references WCAG and is referenced by the European Accessibility Act (EAA, Directive (EU) 2019/882) effective from 28 June 2025.
Section 508 of the US Rehabilitation Act, where it applies to consumer-facing services.

We aim to meet these standards across both the mobile app and the hosted web pages (privacy, terms, this statement, and the other policy surfaces).

2. Where we are today

Honest assessment: we are partially conformant with WCAG 2.2 Level AA. We have done the following:

Designed the mobile app to work with VoiceOver (iOS) and TalkBack (Android), interactive controls carry text labels and navigation order is logical.
Used semantic HTML on the policy pages (proper heading hierarchy, list structures, table headers) so screen readers can navigate them.
Honoured the OS Dynamic Type / font-size preference in the mobile app, text in the app follows your setting up to 150% of the default size (see Known limitations).
Honoured prefers-color-scheme: dark on the policy pages, with sufficient colour contrast in both modes (verified against WCAG 1.4.3 minimum contrast ratios).
Provided text alternatives for non-text content where it carries meaning.

3. Known limitations

We acknowledge the following gaps and are working on them:

Text size. The app follows the OS text-size setting up to 150% of the default and holds text at that size above it, so that fixed-size screens such as the story view do not clip. This falls short of the 200% that WCAG 1.4.4 asks for.
Animations. The app's ambient animations (the onboarding hero, the first-run guide, the story stage, the sign-in backdrop, progress and result indicators) stop when the OS-level Reduce Motion setting is on.
Analysis story. The story view of an analysis advances on a timer and is navigated by tapping and swiping. With a screen reader on, the story stops auto-advancing, each part is announced, and Previous and Next buttons move through it. There is not yet a visible pause control for sighted users who want more time on a part (WCAG 2.2.2); the same content is always available as plain text in the analysis itself.
Charts and data visualisations. Some chart-style outputs in the personality results may not yet have a fully equivalent text alternative. The text body of the analysis always contains the same insights in prose form.
Third-party content. Some content rendered from third-party services (for example, the Apple HealthKit permission sheet on iOS or the Health Connect permission sheet on Android) is controlled by the operating system and is not subject to our accessibility work.
Languages. The Service is currently English-only at launch. We do not yet offer German or French translations, which limits accessibility for non-English speakers in our target markets. German and French translations are on our roadmap.

4. Assistive technologies tested

What we test today, honestly stated:

Web (policy pages), automated: an axe-core scan runs in our build pipeline on every change to these pages, and a failing scan stops the change from being merged.
iOS: manual VoiceOver checks (iOS 17 and later) of the core flows during pre-release testing. We do not yet run a full assistive-technology test matrix at each release.
Android: the Service is built for Android as well as iOS; the Android app is not yet released on Google Play. Our TalkBack testing is less mature than our VoiceOver testing: we do not yet run a structured TalkBack pass at each release, and we will update this section when we do.

We will update this section as our testing practice grows.

5. How to report an accessibility issue

If you encounter an accessibility barrier in the Service or on the policy pages, please tell us. The most useful reports include:

The screen or page where the issue occurs (e.g. "the Settings → Disconnect Apple Health screen" or "the Privacy Policy §10.2 anchor link")
The assistive technology you are using (screen reader name + version + OS)
What you expected to happen and what happened instead

Send reports to contact@eltria.de. We aim to acknowledge accessibility reports within 5 business days and to address them in the next reasonable release. If a barrier prevents you from accessing your data or exercising your privacy rights, say so in the report and we will provide a manual workaround straight away.

6. Enforcement

If you are not satisfied with our response to an accessibility issue, you may file a complaint with the relevant authority depending on your location:

EU/EEA: the national accessibility-supervision authority designated under the European Accessibility Act in your country. A list is maintained by the European Commission.
Germany: the Bundesfachstelle Barrierefreiheit (BFIT-Bund) at bundesfachstelle-barrierefreiheit.de.
UK: the Equality Advisory and Support Service (EASS).
United States: the US Department of Justice (Civil Rights Division) under the Americans with Disabilities Act.
Canada: the Canadian Human Rights Commission.

7. Status of this statement

This statement was last reviewed on 2026-09-29. We review it at least once every 12 months and after any material change to the Service. The next scheduled review is 2027-09-29.