Skip to main content
Skip to accessibility statement

Accessibility statement

Hands that hurt deserve software that works. We design HandTherapy.app for one-handed use, low-vision use, voice-first use, and reduced-motion users.

Our standard

We aim for WCAG 2.2 AA conformance across the marketing site and the in-app experience. Color contrast, focus indicators, semantic landmarks, and keyboard navigation are part of every component review.

Floating hand-assist and voice corner

On phones and tablets, look for the accessibility (person-in-circle) and microphone buttons above the bottom navigation. Both stay available on the full-screen guided session unless you dismiss them. The mic panel includes tappable phrase chips to copy examples.

  • Scroll up / down — large targets move the page in comfortable steps. Double-tap Down quickly to cycle smaller, medium, or larger steps. When the column is visible (not hidden), Arrow Up and Arrow Down on the keyboard use the same step size (skipped while typing in a field or navigating a listbox or dialog).
  • Nudge while video plays — optional gentle scroll while a video in the main content is playing (read-along style; turn off if distracting).
  • Mute session sounds — saves your previous guided / beeps choice in this tab so you can restore it with one tap. Full sound controls stay on the guided session screen.
  • Reel Mode — when enabled, the hand-assist panel includes a link to a vertical, swipeable exercise feed (/reels). Same patient-education rules apply: stop if pain worsens.

Voice commands during sessions

On the guided session screen, tap Voice cmd to opt in. The browser listens for short phrases (English) so you can keep the phone propped up and reduce tapping.

  • Examples: next, back, pause, resume, stop, repeat, first and last step, start. Ask how long for the clock; how many reps for rep count. The floating mic tips panel can copy these phrases to your clipboard. Custom words: Settings → Accessibility → Guided session voice.
  • Recognition uses the device's Web Speech API when available; it never leaves your session without analytics consent elsewhere in the app.

Reel Mode — keyboard, screen readers, and focus

Reel Mode (/reels) is a full-viewport vertical feed when the feature is enabled. It is built for touch first, with parallel support for keyboard and assistive technology.

  • Skip link — At the top of the reel page, Skip to reel feed (visible when focused) moves focus to the main feed landmark (#reel-mode-main). The landmark uses role="region" and an explicit label so screen readers announce where you landed.
  • Escape — Closes the queue sheet, tailor sheet, or shortcuts help if one is open; otherwise leaves reel mode (same destination as the on-screen Exit control).
  • Keyboard shortcuts — Documented in-feed via the Info (?) control: move between exercises with arrow keys (on desktop with a fine pointer, arrow direction matches vertical swipe), Page Up/Down, Home/End; Space or P pause/resume; M mute; R or V restart clip; Q queue; ? full list; G guided session. Shortcuts are suppressed while typing in fields or when certain overlays are open.
  • Screen reader announcements — Slide changes update a debounced polite live region (e.g. “Exercise 3 of 12: …”) so rapid swipes do not spam announcements. Optional spoken titles use the same text when the user enables speech and reduced motion allows it (Settings → Accessibility).
  • Toolbar and progress — Playback controls are in a labeled role="toolbar". Clip position uses role="progressbar" with a short human summary (approximate; not a seekable scrubber).
  • Reduced motion — When the OS prefers reduced motion, programmatic scroll between clips uses instant snapping instead of smooth scrolling.
  • YouTube embeds — Inline video is often a cross-origin iframe. Focus and arrow keys may be captured by the player when the iframe is focused; reel shortcuts are registered on the document so they still work from the surrounding controls, and overlay controls stay available for pause, mute, and navigation.
  • Voice commands — Same global preference as the guided session when supported (HTTPS, compatible browser). Tap the mic control in the reel header to opt in; phrases mirror the guided session (next, back, pause, repeat, etc.).

Guided session: tailored controls (no extra clutter)

The full-screen Session screen is built so you can tune audio, visuals, and which hand the on-screen demo favors — without burying the Start button.

  • Sound rowGuided (voice lines + beeps), Beeps only, or Silent (visual + mirror). Many browsers require a tap on Start before the first spoken line.
  • Voice commands — optional mic toggle; phrases like “next” and “pause” reduce taps when one hand is busy or sore.
  • Hand preview — pick left, right, both, or unsure so animations match your situation. This preference is stored on the device and also feeds flows like Personalize.
  • Larger session text — bumps instruction size for low vision or arm's-length phone use.
  • Low-touch mode — bigger primary controls and more spacing for shaky or splinted hands.
  • Phones & narrow layouts — sound, display, hand, and related toggles tuck into a single collapsible “Sound, display & hand” panel so the timer and Start stay in view first.
  • Wide screens — the same controls stay open in one card with full keyboard shortcuts spelled out next to the sound row.

What we support today

  • Full keyboard navigation across the site.
  • Visible focus rings on every interactive element.
  • Semantic headings and landmarks for screen readers.
  • Reduced-motion respect via prefers-reduced-motion.
  • Large tap targets sized for sore or splinted hands.
  • Voice cues and captions on exercise sessions (opt-in).
  • High-contrast text on hero gradients and media overlays.
  • Reel Mode — skip link to the feed landmark, labeled region, keyboard shortcuts, debounced slide announcements, and toolbar/progress semantics when the vertical feed is enabled (/reels).

Where we can do better

  • Native mobile apps (iOS / Android) with VoiceOver and TalkBack support are in progress.
  • Additional language support beyond English is planned.
  • Color-blind-safe palettes for chart visualizations are an open task.

Tell us when something is broken

Accessibility is a moving target. If something is unusable for you, please reach out via the contact channels published in the app. Reports about hand-friendly UX get priority — that's the whole point of the product.