بيان إمكانية الوصول

Health records should be usable by everyone, including people who rely on assistive technology. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We are not fully there yet; this page says honestly where we are.

1. Measures in place today

• Semantic HTML structure (headings, lists, landmarks, labeled form fields); form labels are checked automatically on every code change, but we have not yet tested the wording with screen reader users (see below).
• A "Skip to content" link on the public site and in the signed-in portal, and a visible focus indicator on every control we have tested by keyboard.
• Keyboard navigation for core flows: signing in, viewing records, uploading documents, the emergency page, family, and settings.
• A consistent design-token color system chosen with text contrast in mind.
• Minimal use of animation, respecting the operating system's reduced-motion preference.
• Responsive layouts designed for small screens and browser zoom.
• Plain-language explanations of medical content as a product principle, which helps cognitive accessibility.

2. How we test

Our automated test suite checks pages with the axe-core accessibility engine against WCAG 2.0 and 2.1 Level A and AA rules, at desktop and phone width: our public, legal and sign-in pages and the main signed-in pages (Today, Records, Imaging, Care, Family, Settings, Emergency, Medicines, Labs, Documents, Upload, Timeline, Appointments, Messages, Sharing and Help). The check fails on any serious or critical issue on those pages. Our last internal review was on 21 October 2026, and it included a keyboard-only walk through the main flows.

Automated testing finds only part of the barriers people meet. It is not a substitute for testing with screen readers or for an independent audit, and we do not yet claim full conformance.

3. Known limitations

Being honest about the gaps:

• Form fields in the web app have a label in code, checked automatically on every code change. Some compact fields, such as search boxes and fields inside table rows, are labelled for screen readers only and show no visible caption. We have not yet reviewed the label wording with screen reader users.
• Interactive charts (labs, vitals, trends) are not yet fully usable by screen readers; the underlying values are included in your record exports.
• Embedded PDF and medical-image viewers depend on third-party rendering and may be difficult with assistive technology; original files can be downloaded.
• We have not yet completed a formal third-party WCAG audit, and we have not yet tested every flow with screen readers.
• The service is in English, with machine translation into other languages on request; translated text has not been reviewed for accessibility.
• Voice and audio features do not yet have full text-equivalent alternatives in every flow.

We are working through these and prioritize fixes that block access to your own records.

4. Accommodation requests (ADA / AODA)

If a barrier prevents you from accessing your records, contact us and we will provide the information in an accessible format that works for you, at no cost. This is our commitment under the Americans with Disabilities Act (ADA) for U.S. users and the Accessibility for Ontarians with Disabilities Act (AODA) for Ontario users, and our policy everywhere else.

5. Feedback

Accessibility feedback goes straight to the operator: [email protected]. Please describe the page, the assistive technology in use, and the problem; we aim to acknowledge within 5 business days.