Legal · Accessibility Statement
A medical product should be usable by anyone who needs it.
We treat accessibility as a clinical-grade requirement, not a marketing bullet. The product is tested with real assistive technology before every release, the conformance target is published, and the things we haven't fixed yet are listed below by name. If something on this site or inside the product blocks you, write accessibility@conceptualhealth.com — that inbox is monitored, and we'll respond within two business days.
Last updated: April 2026.
1 · Conformance target
WCAG 2.2 Level AA, with the exceptions named.
Public marketing pages and the authenticated patient app target WCAG 2.2 Level AA. Clinical surfaces — the EHR, the provider command center, the ops dashboards used by licensed staff — also target Level AA except where the screen is intentionally clinically dense (e.g., a multi-pane vitals grid during a code) and where a Level AA pattern would slow time-to-decision. Every such exception is published with its rationale in the in-app accessibility center.
2 · What we do every release
Automated, then manual, then on real hardware.
Automated. Every pull request runs axe-core against the touched pages; a regression blocks merge.
Manual. A human runs a screen reader on every new or modified surface before release.
Contrast. Body text holds 4.5:1, large text 3:1, UI components 3:1 — measured per surface, not assumed from the theme.
Keyboard. Every interactive element is reachable by Tab and operable by Enter or Space. Visible focus indicators are present on every focusable element.
Forms. Every input has a programmatically associated label; errors are announced; required fields are marked in text, not just by color.
Media. Images have alt text or are flagged decorative. ARIA labels appear where semantics require them. A skip-to-main link is the first focusable item on every page.
3 · Known gaps
The honest list of things that aren't fully there yet.
DICOM viewer. The medical imaging viewer used by clinicians requires a sighted operator. Patients who receive an imaging study can request an alt-format export (PDF report + structured findings) in the in-app accessibility center.
HMAC chain explorer. The visual chain explorer at /proof/chain.html is graphic-heavy by design; a screen-reader-friendly tabular alternative is served by pressing Tab on the page.
HC.exchange charts. Order-book depth charts and candlestick charts on the exchange surface have a screen-reader tabular alternate that opens on focus.
Motion. Animations on the orb and the proof pages respect prefers-reduced-motion and resolve to static states when that preference is set.
4 · Tested assistive technology
Real hardware. Real combinations.
Screen readers: NVDA on Windows, JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android.
Voice control: Dragon NaturallySpeaking on Windows, Voice Control on macOS, Voice Access on Android.
Browsers: latest two major versions of Chrome, Safari, Firefox, Edge.
Magnification: ZoomText and the OS-level zoom on each platform.
5 · Report a barrier
Two business days to acknowledge. Thirty to resolve or scope.
From inside the product, tap "Report a barrier" in the footer of any screen. From the marketing site, write to accessibility@conceptualhealth.com. We acknowledge within two business days and aim to resolve within thirty; if a fix needs longer (because it requires a vendor change, for example), we publish a timeline and a workaround.
6 · Formal complaints
U.S. residents have escalation paths beyond us.
If a Conceptual Health® response doesn't resolve a barrier you've experienced, U.S. residents may file a complaint with the U.S. Department of Health and Human Services Office for Civil Rights (Section 1557, ACA non-discrimination) or, under ADA Title III, with the U.S. Department of Justice. We will cooperate with both. Filing a complaint does not affect your account, your care, or your tokens.