Accessibility & AAC

Accessibility & AAC

Accessibility that is architecturally enforced — not a bolt-on. Plus ARIA AAC CVI for non-verbal users.

Accessibility & AAC

CVI Mode: LIVE

ARIA AAC CVI: COMING SOON

The sensory profile

Every ARIA component respects it — this is a design rule, not a setting. Persists to SQLite on every state change so it survives a crash.

CVI Mode

Pure-black backgrounds, bright yellow borders around interactive elements, larger touch targets, slower or disabled animations. Toggle from Settings. Also available inside the Meal Planner and Marketplace modals.

Touch targets and palm rejection

Minimum size selectable: 80, 120, or 160 pixels. Palm rejection at screen edges for ataxia accommodation.

Animations

Gated on the sensory profile flag and on OS prefers-reduced-motion. No rapid flash anywhere — photosensitive-seizure safe.

ARIA AAC CVI

First-party AAC board for non-verbal children with visual impairment. Large, high-contrast tap targets. Tap-to-speech within 100 ms via local Web Speech API. Queue interrupts and replaces on new taps — stim-tapping never floods the output.

Status: COMING SOON. The tap-to-speech engine and sensory-profile wiring are in place. The symbol library and user-configurable board layouts are still being curated.

Why it exists

Accessibility was designed in from the start for families caring for children with sensory, visual, motor, and communication differences — not layered on later. The architecture requires every component to respect the user's sensory profile, so accessibility is a design rule rather than a setting.

Updated on: 
Apr 14, 2026