Accessibility

Last reviewed: August 25, 2026

Holakare is a place people keep a medical record for someone they love, often while tired and in a hurry. It has to work for the person using it, whatever they use to get there. This page says where we actually stand — including the parts that are not there yet.

What we are aiming at

We build to WCAG 2.2, Level A and Level AA, across all three places Holakare exists: this website, the caregiver web portal, and the iPhone, iPad and Apple Watch apps.

Where we are

Most of the way, with the last step outstanding. On 24 August 2026 all three were audited against WCAG 2.2 A and AA — by reading the code and measuring colour values, which is a real audit but not the same thing as using them — and the problems it found have since been fixed — contrast, keyboard access, skip links, focus rings, form errors that announce themselves, and the undo prompt described below.

What has not happened yet is the part that matters most: sitting down with a screen reader and using the thing. Everything above was verified by reading the code and measuring colour values. That is necessary and it is not sufficient, and we would rather say so than round it up to “accessible”.

What is fixed, specifically

• Contrast. Every text and button pairing we measured now clears 4.5:1 in both Day and Night — the range is 5.9:1 to 14.3:1. The accent used for links and buttons was changed to a text-safe tone, because the brand fills themselves were never readable at small sizes.
• The undo prompt after a dose. It used to disappear after six seconds whatever you were doing. It now does not time out at all while VoiceOver is running, and it notices if you switch VoiceOver on part-way through.
• Getting around without a mouse. Every page has a skip link, the navigation opens from the keyboard, and focus is always visible.
• Motion. Turning on Reduce Motion removes animation and smooth scrolling across the site and the app.
• Colour is never the only signal. Status carries a label or a shape too.

What is still open

One thing, and it is honest work rather than a known defect:

• We have not recorded a live assistive-technology session. VoiceOver on a real iPhone, Switch Control, the largest Dynamic Type sizes, 400% browser zoom, and Windows High Contrast all still need a person to sit down and go through them. Until that happens we will not claim conformance, because code review can tell you something is wired up correctly — it cannot tell you it is usable.

If you use any of those and something gets in your way, you will find it before we do. Please tell us.

Telling us something is wrong

Write to [email protected] and put "Accessibility" in the subject. Tell us what you were trying to do, what got in the way, and what you use — a screen reader, a switch, voice control, a large text size, whichever it is. You do not need to know the name of the problem.

We aim to reply within five working days, and to tell you either how to work around it or when we expect it fixed. If something blocks you from care information you need right now, say so in the subject line and it goes to the front.

Holakare is made by one person, so there is no accessibility department to escalate to — but there is also nobody for the message to get lost behind.

How this page is kept honest

The claims above come from an audit of the code and the interface, plus measured colour values — not from a checklist someone filled in. It is not a certification and it is not a legal opinion. When we fix something on the list, it comes off the list; when a review finds something new, it goes on.