Accessibility
Access is the product, not a setting.
If a communicator cannot reliably reach a word, the vocabulary does not exist. These are the commitments we build against.
- Targets
- Every interactive cell is at least 44px and larger by default on the AAC surfaces.
- Text labels
- Labels are first-class, not decoration. Symbol and text always appear together, and label size is scalable.
- Colour
- Colour never carries meaning alone. Category cells differ by shape, border style and an explicit hint as well as tone.
- Keyboard and AT
- All controls are reachable by keyboard with visible focus states and descriptive ARIA labels.
- Scanning
- A predictable scanning prototype steps through the grid in stable order. The Context Halo is its own scan group and never re-ranks mid-selection.
- Motion
- Reduced motion removes non-essential transitions. There are no autoplaying animations on the AAC surfaces.
- Contrast
- A high contrast mode strengthens borders and text separation, and dark and light themes are both supported.
- Selection safety
- Activation can be set to fire on release rather than on touch, so a resting or dragging finger does not speak.
Known limitations in this build
- Spoken output uses the browser's own speech voices. Voice quality, language coverage and whether voices work without a connection depend on the device and browser, not on EyeSay.
- Eye gaze and switch access are provided as a scanning prototype in this interim web build; a native iPad build is planned for full input support.
- Speech recognition for the listening demo is only available where the browser provides it, and is never started automatically.
Found a barrier? Tell us through the early access form and we will treat it as a defect.