Accessibility

Content last checked: 4 September 2026. No live assistive-technology session has been recorded yet; one is planned before the App Store release. See known limitations.

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, everywhere Holakare exists: this website, the iPhone, iPad and Apple Watch apps, and the signed-in pages that run in a browser.

Where we are

Partially conformant, with a plan to close the gap. On 24 August 2026 all of them were audited against WCAG 2.2 A and AA, by reading the code and measuring color values, which is a real audit but not the same thing as using them. Most of what it found has been fixed. What remains is listed below, each with what happens next, and the live session that would prove the rest either way is planned before the App Store release.

What is fixed

• 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.
• Touch targets on the app’s filter chips and segmented controls, and color is never the only signal; status carries a label or a shape too.

Known limitations, and what we are doing about them

These are the limitations we know about, each with what happens next. When one is closed it comes off this list.

• No live assistive-technology session is on record yet. VoiceOver on a real iPhone, Switch Control, 400% browser zoom and Windows High Contrast all still need a person. That session is planned before the App Store release, and what it finds will be added here. Until it is on record we will not claim full conformance, because reading code tells you something is wired up correctly, not that it is usable.
• Text can be cut off at the largest text sizes. Some status chips and titles in the app are limited to one line and will truncate rather than wrap. A fix is planned before the App Store release.
• Tab bar icons. The contrast between the selected and unselected tab icons has not been measured on a real screen. It is part of the live session above.
• Layout at very high zoom. At 400% zoom on a desktop-width window, the signed-in pages that run in a browser are not proven to reflow without loss. It is part of the live session above.
• The sign-in security check is a third-party widget with its own accessibility behavior, which we do not control. The forms stay usable if it fails to load, but the widget itself is not ours to fix. If it blocks you, tell us and we will get you signed in another way.
• Automated checks do not run yet in our build. Structural tests do; a full in-browser accessibility scan is not wired up. Adding one is planned.

If something is in your way right now, you do not have to wait for any of that. Write to us as described below. Where the interface itself is what blocks you, we will find another way through, including sending you a copy of your household’s data, which you are entitled to anyway.

If you use any of these 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.

This one gets a reply. Not a form letter, an actual answer telling you either how to work around it or when we expect it fixed. If something is blocking you from care information you need right now, say so in the first line of the message and it goes to the front of the queue. Keep the subject as it is; a subject line travels through mail servers, notifications and forwards, and what is blocking you is nobody else’s business.

We are not going to put a number of days on that. Holakare is made by one person, and a published deadline that gets missed while they are asleep or on a train is worth less than a promise we can actually keep. There is no accessibility department to escalate to, and also nobody for your 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 color values, not from a checklist someone filled in. It is not a certification and it is not a legal opinion. When we fix something it comes off the list, and when a review finds something new it goes on.

The date at the top counts one thing only: when someone last went through this page and checked it still matches the product. It is deliberately not a claim that anyone sat down with a screen reader; when that happens it will be said here in plain words, and this line will be the first thing to change.