Accessibility Statement | Mediara Vault

Mediara is committed to making Mediara Vault accessible. This statement applies to the Mediara Vault Android app and, in the final section, to this website.

It is structured on the EU model accessibility statement and the European Accessibility Act (Directive (EU) 2019/882), whose technical baseline is EN 301 549 — which, for apps, points to WCAG 2.1 level AA.

Conformance status

Partially conformant with WCAG 2.1 AA. “Partially conformant” means most of the standard is met, but some content and interactions have not yet been fully verified against every success criterion on assistive technology.

We state this deliberately rather than claiming full conformance, because a full audited pass on real devices with live assistive technology has not been completed. We would rather under-claim and tell you where the gaps are.

What is in place, and verified in the build

Screen-reader support (TalkBack). Interactive elements and status tiles carry semantic labels, and progress tiles announce meaningful sentences with units rather than bare numbers — for example “Doses today: 3 of 7 taken, 4 left” instead of “3 / 7”. This is covered by automated tests in the codebase.
Large text and dynamic type. Layouts are tested at large text scale, up to about 200%, without clipping key content. This is enforced by automated overflow guards on key screens.
Colour contrast. Status and severity colours use a theme-aware, contrast-checked palette in both light and dark themes, and colour is never the sole carrier of meaning — direction arrows accompany up/down status, and record types are named as well as coloured.
No reliance on sensory-only cues for critical information.
Voice dictation provides a hands-free path into every long free-text field, with the microphone inside the field so the destination is unambiguous.
Privacy and security options do not impede accessibility. Discreet notifications and screen-capture blocking change what is displayed, not whether it can be read by assistive technology.
No time limits and no auto-advance in the consent flow, and each of its eleven acknowledgements is individually focusable with a full-sentence label. The disabled continue button announces why it is disabled.
Reduced-stress copy. Deletion is described honestly (“moved to Recycle Bin — restorable for 30 days”), destructive confirmations use haptics, and the pregnancy-loss path avoids celebratory framing.

Known gaps and limitations

A full audited pass on real devices with live assistive technology is pending. A device-driven TalkBack walkthrough and a 200% visual sweep are on the manual test checklist but have not been signed off. Until they are, conformance is stated as partial.
Some complex custom widgets — charts, multi-step editors — may not yet expose complete semantics for every gesture path.
Voice input depends on the platform speech recognizer and on your device’s own accessibility configuration. Because the app requires on-device recognition, dictation is unavailable on devices without a local speech model.
English only. This release ships in English only, which is itself an accessibility limitation for people who do not read English comfortably.

These are the reasons this statement does not claim full conformance. They are tracked for remediation.

Assessment method

Self-assessment, based on automated widget and semantics tests in the codebase and a code-level review of the UI layer, together with the accessibility findings tracked in the project’s own UI audit. A third-party or full manual assistive-technology audit has not yet been performed.

This website

These pages are built to the same intent: semantic HTML with a correct heading order, a skip-to-content link, visible keyboard focus indicators, text that reflows without horizontal scrolling down to narrow viewports, descriptive alternative text on every meaningful image, wide tables that scroll within their own container rather than forcing the page sideways, support for the reduced-motion preference, and a light and dark theme that both meet contrast requirements. Every page works with JavaScript disabled.

Like the app, the website has not had a third-party audit. If something here is hard to use, please tell us — the same address works for both.

Feedback and contact

If you encounter an accessibility barrier in the app or on this website, contact support@mediara.care. Please describe the screen and the problem, and tell us which assistive technology you were using. We aim to respond within a reasonable period.

Enforcement (EU users)

If you are not satisfied with our response, you may contact the accessibility enforcement body in your EU member state.