Connected care should include everyone.

Our commitment

CROW FINANCIAL HOLDINGS LLC DBA CURA COACH is committed to making its website and connected-care services usable by people with disabilities. Accessibility is treated as an ongoing product and operational responsibility, not a one-time checklist.

We aim to provide equitable access for patients, healthcare professionals, practice teams, billing partners, applicants, and members of the public across supported devices and assistive technologies.

Our technical target

CuraCoach targets the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA for public and authenticated web experiences wherever practical. WCAG is a technical reference point; a statement of alignment is not a claim that every page, integration, document, or third-party component is free of barriers.

Applicable legal obligations may vary by service, customer, jurisdiction, and context. We review requirements and prioritize effective communication and meaningful access.

Accessibility built into the experience

Our design and engineering practices include:

• Semantic headings, landmarks, labels, and page titles.
• Keyboard-operable navigation, forms, dialogs, and primary workflows.
• Visible focus indicators and logical focus order.
• Text alternatives for meaningful imagery and labels for icon controls.
• Color contrast designed for readability, with status communicated through words and icons—not color alone.
• Responsive layouts, scalable text, adequate target sizes, and reduced-motion support.
• Accessible form instructions, required-state text, validation feedback, and error recovery.
• Table structure and chart summaries intended to preserve meaning for assistive technology.

Clinical and operational workflows

Accessibility is especially important where users review readings, alerts, tasks, documentation, billing states, or provider requests. CuraCoach designs these workflows to preserve essential actions at different viewport sizes and to expose urgency, status, and required information without relying on visual presentation alone.

Time-sensitive clinical or operational processes must also have organizational fallback procedures. Accessibility features do not replace appropriate staffing, escalation, downtime, or emergency procedures.

How we evaluate accessibility

Our intended evaluation approach combines automated checks, keyboard review, screen-reader testing of priority workflows, contrast review, responsive testing, reduced-motion checks, and issue tracking. Material releases should include accessibility review proportionate to the risk of the affected workflow.

Automated tools identify only some barriers. Human testing, feedback from people with disabilities, and remediation verification remain necessary.

Third-party content and integrations

Some experiences may rely on identity, communication, payment, document, device, EHR, or other third-party services that CuraCoach does not fully control. We evaluate accessibility during selection and integration where practical and work to provide an accessible path or reasonable alternative when a barrier is identified.

Supported technology

CuraCoach is designed for current versions of major browsers and commonly used assistive technologies. Older, unsupported, heavily customized, or security-restricted environments may behave differently. Keeping browsers, operating systems, and assistive technology current generally provides the best experience.

Alternative access and assistance

If a feature, document, report, or communication is not accessible to you, contact us and describe the content, route, format, assistive technology, and barrier. We will review the request and work toward an accessible alternative or reasonable accommodation appropriate to the circumstances.

Do not include patient details in the public contact form. Authenticated users should use their approved support route for issues involving sensitive records.

Feedback and response

Accessibility feedback may be submitted through the CuraCoach contact page and labeled “Accessibility.” Include the page address and a concise description of the issue. We welcome feedback and use it to prioritize remediation.

This statement will be updated as our product, testing, or accessibility practices materially change.