Accessibility Statement

People who use TruHealth most are often the people who most need it to be usable: someone managing a long-term condition, an older parent, a caregiver working through a list at the end of a long day. Poor eyesight, a tremor, a screen reader, or simply a small phone in bad light should not stand between a person and their own health record.

We are working towards WCAG 2.2 level AA — the Web Content Accessibility Guidelines published by the W3C, which is the standard most accessibility laws point at, including the Accessible Canada Act and Ontario's AODA. It is our target, and this page says how far along we are.

These are choices already built into the product, verified by us during development:

• Real HTML structure. Headings, lists, landmarks, buttons and links are marked up as what they are, so navigation aids have something to work with.
• Keyboard operation. Interactive parts are built from keyboard-accessible components, and focus is visible rather than styled away.
• Light and dark themes that follow your system setting, so people who need a dark or a bright screen get one without hunting for a switch.
• Messages you can actually see. Success, warning, error and information notices are tinted across the whole surface with a matching border, chosen to hold AA contrast in both light and dark mode — no white-on-white notices, and never colour alone carrying the meaning.
• Text that scales. Sizes are relative, so browser and system text-size settings work.
• Icon-only buttons carry names. Compact toolbar buttons have tooltips and accessible labels so they are announced properly.
• Layouts that reflow. Pages work on a small screen and at high zoom rather than forcing sideways scrolling.

These are the areas we already know need work. Listing them is not an excuse — it is how you know what to expect before you rely on the product.

• Charts and trend graphs convey information visually and do not yet have a full non-visual equivalent such as a data table or text summary.
• The body map, used to point at where a symptom or allergy is, remains a visual interface. The product now provides searchable text and keyboard paths to the same body locations, but their parity still needs formal screen-reader verification.
• Screen reader testing is incomplete. We have not finished testing with VoiceOver, NVDA or JAWS, so announcements in complex screens — grids, drawers and dialogs — may be wrong or missing.
• Dense data grids are compact by design. Keyboard navigation within them, and how they behave at high zoom, need review.
• Motion. Some parts of the marketing site animate. Respect for the “reduce motion” system setting is not yet applied everywhere.
• Uploaded documents. Files you upload to your vault — scanned lab reports, photographs of prescriptions — are as accessible as the original. We cannot fix a scanned page for you.
• Contrast has not been measured across every screen. The shared colours were chosen to meet AA, but we have not audited every combination in the product.

This statement is based on a self-assessment by the team that builds TruHealth. It reflects checks made during development: keyboard walkthroughs, contrast choices made against the WCAG AA ratios, and review at mobile widths in both light and dark mode.

It is not based on an independent evaluation, an automated accessibility scan report, or testing with users of assistive technology. An external review is planned for <PLANNED ACCESSIBILITY REVIEW DATE>; when it happens, this page will be rewritten around what it finds.

If something here stops you using TruHealth, we want to hear about it — this is the fastest way for us to fix the right thing.

• Email <ACCESSIBILITY CONTACT EMAIL>, or use the contact form on our home page.
• Tell us what you were trying to do, which page you were on, and what you use to browse (for example, a screen reader and its version) if you know it. Any detail helps; none of it is required.

We aim to reply within <RESPONSE TIME> and to tell you either how to work around the problem now or when we expect to fix it. Please do not include health details in a message to us — see the Privacy Policy.

If you are not happy with our response, you can escalate to <ESCALATION CONTACT>. In Canada, you may also be able to complain to the accessibility regulator that applies where you live.

Where a barrier stops you doing something important, ask us and we will find another way — for example, providing your records in a different format, or helping you complete a task directly. Contact <SUPPORT EMAIL>.

We will not charge you for that, and asking for it will not affect your account.

Scope

This statement covers the TruHealth marketing website and the TruHealth web app. Native mobile applications, when we publish them, will be added here.

Standard

Web Content Accessibility Guidelines (WCAG) 2.2, level AA — target, with partial conformance today as described above.

Prepared

Prepared on 1 August 2026 by the TruHealth team, on the basis of a self-assessment. It is reviewed whenever we ship a significant change to the interface, and at least every <REVIEW INTERVAL>.