Skip to main content

Trust

Accessibility

Articarry is used by children and by busy clinicians. The build targets WCAG 2.1 AA and the testing posture below holds it there.

Internal beta: synthetic and explicitly-consented test data only.

Articarry is in a private beta. The text below describes how the product is engineered and how it intends to handle data. Use with real patient audio requires BAA-covered infrastructure and a legal review of this text; both are gates between this beta and any wider use.

What we aim for

WCAG 2.1 Level AA on both surfaces: the child's practice screens and the clinician's dashboard. Some choices are designed to clear AA and a stricter floor of our own: per-word attention markers are color-blind-safe (encoded by shape as well as hue), and a grayscale print of any clinician surface carries the same diagnostic signal as a color render.

How the build holds the line

  • axe-core sweeps every signed-in surface. Each clinician and guardian page is walked by a Playwright + axe-core test on every CI run. A WCAG-AA violation fails the build.
  • Keyboard-only walks of the heaviest flows. The enrollment composer (six steps), the book reader (library → reader → reveal → completion), and the per-recording diagnostic have all been walked with the keyboard alone; findings are folded back into the templates.
  • Screen-reader walks of the same flows. The composer and the book reader have been walked with NVDA on Windows. Each finding is documented and either fixed or routed to the design-system v1.1 backlog.
  • A "comfort panel" on the child surface: larger text, higher contrast, easier-reading spacing, reduced motion. Remembered per device.
  • Reduced-motion is honored wherever an animation could be intrusive (book-reader scene reveal, completion confetti). The operating system's prefers-reduced-motion setting is the source of truth.
  • Skip-to-main link on every page, focus rings preserved on every interactive element, semantic headings throughout, ARIA only where the HTML primitive can't express it.

What we know we have not tested yet

  • Cross-screen-reader matrix. NVDA is the primary screen reader walked today. JAWS and VoiceOver (macOS / iOS) have not been systematically walked end-to-end. This is a gate, not a date, on real-patient deployment.
  • Voice-control (Voice Access, Dragon). Speech-driven UI navigation has not been validated.
  • Switch-control + scanner input. Some children use a single-switch or scanner interface. The recorder's tap-to-start interaction has not been validated against either.

Reporting a barrier

If something is hard to use, please tell us: accessibility@articarry.com. A clinician in the beta can also raise it directly with us; a family can send it through their clinician. We acknowledge in writing and prioritize inline.

If the barrier you've hit is "I want to leave", a guardian can delete a child or their whole account from the account page; the privacy page describes the 30-day undo window and what is removed when.

Last updated: 2026-05-25.