Vertix.

Accessibility

Accessibility Statement

Last updated: May 1, 2026 · Currently available to licensed clinicians in the United States.

Vertix is committed to ensuring that the platform is accessible to people with disabilities, including clinicians and the patients they serve.

1. Standards we follow

  • WCAG 2.1 Level AA: target conformance level for all marketing pages and the Clinic app.
  • Section 508: required for federal customers and any clinician working with VA, DoD, or government-affiliated clinics.
  • ADA Title III: covered entity obligations for places of public accommodation operating online.

2. What we have done

  • Color contrast meeting WCAG AA on all text-on-background combinations (normal text 4.5:1, large text 3:1).
  • Keyboard navigation for all interactive elements. No mouse trap. Visible focus indicators (3px ring).
  • Semantic HTML throughout — proper headings, landmarks, lists, and form labels.
  • ARIA labels on all interactive components without visible text labels.
  • Form fields with explicit label elements, aria-required, and aria-invalid states.
  • Image alt text for all meaningful images. Decorative images marked aria-hidden.
  • Respect for prefers-reduced-motion — animations disabled when the user has the OS-level setting on.
  • Tap targets minimum 44×44 pixels on touch interfaces.
  • Error messages announced to screen readers via role="alert".

3. Where we are still working

We do not claim full conformance. Known areas in progress:

  • Some legacy charts in clinical dashboards lack screen-reader-friendly text alternatives. Targeted fix Q3 2026.
  • Complex tables in the comparison matrix require a more granular row-header association. Targeted fix Q2 2026.
  • Live Co-Pilot streaming output is being instrumented with aria-live regions for screen readers. In progress.

If you encounter a barrier, please report it. We treat accessibility issues as priority bugs.

4. Assistive technology compatibility

We test with:

  • NVDA + Firefox (Windows)
  • JAWS + Chrome (Windows)
  • VoiceOver + Safari (macOS / iOS)
  • TalkBack + Chrome (Android)

If your assistive technology is not on this list and you encounter issues, contact us.

5. How to report a barrier

Email [email protected] with:

  • The page or feature affected.
  • The assistive technology you are using.
  • A description of the barrier and what you were trying to accomplish.

We acknowledge accessibility reports within 2 business days and aim to resolve or provide a workaround within 30 days for AA conformance issues.

6. Alternative formats

If you need any document on this site (BAA, terms, security questionnaire) in an alternative format (large print, plain text, screen-reader-friendly PDF), email [email protected].

Questions about this document? Reach our compliance team.