Maya from AccessOpsPilot feedback from week one
The keyboard model is landing well across the support team.
Accessibility first
Assistive tech
in the architecture.
Blind users are the primary audience—not a persona deck. Blind Sight, keyboard maps, live regions, and audio layers ship in the desktop shell and shared settings—not patched in after launch.
Dual modes
Visual layout or Blind Sight—same capabilities on desktop.
Blind Sight hides chrome for non-visual workflows while shortcuts and AT APIs keep working. Mobile mirrors the toggle where the Expo shell exposes it.
Visual mode
Keyboard-firstAudio cuesProvider-ready
BlindBox keeps orientation obvious.
Read the thread, hear state changes, jump between folders, and move into compose without losing your place.
Blind Sight mode
Keyboard-firstAudio cuesProvider-ready
BlindBox keeps orientation obvious.
Read the thread, hear state changes, jump between folders, and move into compose without losing your place.
Core pillars
Behaviors implemented in the desktop and mobile clients.
Screen-reader-first structure
For blind and visually impaired users, orientation is everything: skip links, landmark regions, aria-live announcements, and deliberate focus order ship alongside mailbox views and shared accessibility composables—not a marketing checklist.
Blind Sight mode
Desktop-only toggle (Alt+Shift+V) hides the visual surface while keeping the same command surface for keyboard and assistive tech users.
Shortcut-led movement
Documented global shortcuts for refresh, compose, folder shortcuts, help, and list navigation match the README table so training materials stay accurate.
Adaptive visuals & reading
Per-theme palettes, high contrast, reduced motion, larger controls, readable fonts, spacing, font size, reading width, and plain-text preference—all persisted like other accessibility prefs.
Audio confirmation
Optional success/error/navigation sounds plus transition cues support people who rely on audio feedback alongside or instead of visual highlights.
Insight-friendly workflows
When your plan includes Insight, AI summaries and transcripts extend PDF/image workflows without removing the underlying accessible mail experience.
Shared-device clarity
Blind Sight, themes, and audio settings are per user profile on a machine—mixed visual needs in one household or office stay independent.
Shortcut map
Keep your hands
on the keys.
The shortcuts below match the table in the repository README. They are global in the desktop shell so refresh, compose, and folder jumps stay one chord away—not buried in nested menus.
Toggle Blind Sight mode from anywhere in the desktop app (hides visual chrome, keeps keyboard + AT access).
Refresh the current mailbox view.
Open compose instantly.
Jump between Inbox, Sent, Drafts, and Starred.
Open keyboard shortcut help.
Move through message lists and open the selected conversation.
Inclusion at scale
One workflow, many ways of seeing.
Mixed-ability households and support desks get one codebase: Blind Sight for non-visual work, rich themes for low vision, and the same mailbox APIs underneath—plus honest docs when a feature is desktop-only.
OrientationLandmarks & Focus Order
AdaptationContrast & Audio Control
TrustBuilt-for-Blind mode