Accessibility

1. The standard we work to

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and the corresponding requirements of EN 301 549, across both karego.ai and the KareGO iOS app.

We have not yet completed an independent accessibility audit, so we do not claim conformance. Stating an aim honestly is worth more than asserting a standard we have not verified.

We also aim to meet the requirements of the European Accessibility Act. As a very small company we may currently fall within its exemption for microenterprises. We are not relying on that exemption, because our reason for doing this is not that the law requires it.

2. What KareGO supports today

On iOS, KareGO is built with the system's standard accessibility frameworks, which means the following work with the app:

• VoiceOver — the screen reader built into iOS. Interface elements are labelled so they can be read aloud.
• Dynamic Type — text scales with the size you have chosen in iOS settings, including the accessibility sizes.
• Bold Text, Increase Contrast and Reduce Transparency — the app respects these system settings.
• Reduce Motion — animations are reduced when you have asked iOS to reduce them.
• Voice Control and Switch Control — standard controls are reachable by these input methods.
• Zoom and Magnifier — supported at the system level.
• Dark Mode — supported.

Design choices that help

• Text is used for meaning rather than colour alone, so information is not lost if you cannot distinguish particular colours.
• Touch targets are sized for imprecise or unsteady input.
• Every feature that requires a device permission works without it — KareGO does not become unusable if you decline the camera, microphone or location.
• Plain language is a product principle, not only an accessibility one. Our medical explanations target roughly a 14-year-old reading level.

On karego.ai: semantic HTML structure, keyboard navigation, text alternatives for meaningful images, and a cookie banner that can be dismissed without accepting analytics — the page remains fully usable either way.

3. Where we currently fall short

This section exists because you deserve to know before you rely on us, not after.

• We have not completed a full independent audit. Our knowledge of our own gaps is therefore incomplete, and there will be problems we have not found.
• Uploaded documents inherit their source. A scanned PDF from a hospital is an image. Our AI extracts and structures the text, which often makes a document *more* accessible than the original — but the original file itself cannot be made accessible by us.
• Charts and biomarker trends are visual. We are working to ensure every chart has an equivalent text or table view. Until that is complete, some trend information is easier to reach visually.
• The PPG heart measurement requires the camera and steady placement of a finger. There is no non-visual equivalent, and for some users this feature will not be usable. Nothing else in KareGO depends on it.
• Voice transcription accuracy varies. Speech recognition performs less well with atypical speech, strong accents and some languages. Transcripts can be edited, and audio is retained so you can check them.
• The Medical ID card is information-dense by design, since it must be readable at a glance in an emergency. Balancing that against text scaling is an ongoing piece of work.

4. What we are working on

• Commissioning an independent accessibility audit of the app and website, and publishing the results including the failures.
• Text and table equivalents for every chart in the app.
• Testing with assistive technology users, not only with automated tools. Automated checks find a minority of real problems.
• Reviewing VoiceOver labelling across every screen, prioritising the Medical ID card and medication management, where an error has clinical consequences.

We will report progress on this page rather than announce it once and stop.

5. Telling us about a problem

Email [accessibility@karego.ai](mailto:accessibility@karego.ai).

Useful if you can include it, but never required: what you were trying to do, which screen, which assistive technology and iOS version. "The medication list does not work with VoiceOver" is a perfectly good report.

Our commitments

• We acknowledge within 2 business days.
• We give you an assessment and a plan within 10 business days.
• We prioritise anything that blocks access to your own medical records above new feature work.
• We tell you when it is fixed.

We do not treat accessibility reports as feature requests, and we do not close them because a workaround exists.

6. If you cannot access something now

If you cannot reach part of KareGO, contact accessibility@karego.ai and we will help you directly — including exporting your data, retrieving specific records, or explaining what a document contains. We will verify your identity carefully first, since we are handling medical information, but we will not leave you locked out of your own health history while we work on a fix.

This is a standing offer, not a courtesy extended case by case.

7. Assistance from others

If someone helps you use KareGO — a family member, a carer, a support worker — be aware that they will see your complete medical history, and that our sharing features are described in our Terms of Service. Share deliberately, including with people you trust.

8. Contact

Accessibility: accessibility@karego.ai

General support: support@karego.ai