Accessibility
SPEC_ACCESSIBILITY.md
Accessibility — OBI OS for Everyone
Status: SPECIFIED
Version: v1.0
Author: VELA (Thread #13)
Conceived by: NOUS (α.13)
Date: 2026-04-21
Depends on: SPEC_OBI_OS_VISION.md, SPEC_BRIDGE_LAYOUT.md, SPEC_BRIDGE_VIEWSCREEN.md, SPEC_BAND_MODE.md, SPEC_TEACHING_PROTOCOL.md, SPEC_INTERACTION_PROTOCOL.md
PURPOSE
The Captain built the ship alone with a GED. No formal education. No institutional support. The ship is FOR people who are underestimated, self-taught, working with limited resources. If OBI OS is inaccessible to people with disabilities, it betrays its own origin story.
This spec ensures OBI OS works for EVERYONE — people who can't see the screen, people who can't hear the audio, people who can't use a mouse, people with cognitive differences, people on old hardware, people with slow internet.
Accessibility is not a feature. It's a REQUIREMENT.
THE STANDARDS
WCAG 2.1 Level AA is the minimum target. This covers four principles:
- Perceivable — content can be presented in ways any user can perceive
- Operable — interface components are operable by any user
- Understandable — content and interface are understandable
- Robust — content works with assistive technologies
SPECIFIC REQUIREMENTS
Visual Accessibility
- All images have alt text
- All charts have text descriptions
- Color is NEVER the only indicator — green/red status also uses ✓/✗ symbols
- Text meets minimum contrast ratios: 4.5:1 for normal text, 3:1 for large text
- Bridge UI works with screen readers (ARIA labels on all interactive elements)
- Font size adjustable
- High-contrast mode available
- The Viewscreen's ambient audio (green hum → red alarm) is the audio equivalent of color: it works FOR blind users, not against them
Auditory Accessibility
- Band Mode compositions have visual notation display alongside audio
- Alert sounds have visual indicators
- VR spatial audio has visual direction indicators for deaf users
- All video content has captions
Motor Accessibility
- All functionality available via keyboard — no mouse-only interactions
- No time-limited interactions (users who type slowly aren't penalized)
- Voice control compatibility (THE RING already accepts text — voice-to-text feeds the same input)
- Bridge VR supports seated mode and controller-free interaction where possible
Cognitive Accessibility
- Plain language in all user-facing text per SPEC_TEACHING_PROTOCOL.md
- Consistent navigation — buttons in the same place on every screen
- No autoplay of media
- Clear error messages that say WHAT went wrong and HOW to fix it
- Session Zero (SPEC_INTERACTION_PROTOCOL.md) can detect and adapt to cognitive accessibility needs
THE CAPTAIN'S PERSPECTIVE
The Captain has an Asperger's profile. The ship's interface already reflects neurodiverse design instincts:
- Consistent patterns — everything follows the same format
- Honest communication — HOW ABOUT NO doesn't hedge or use ambiguous social cues
- Customizable environment — Classic Desktop / Bridge 2D / Bridge 3D / Bridge VR — the user CHOOSES their interface complexity
- One task at a time — SPEC_INTERACTION_PROTOCOL.md standing order #2
These aren't accessibility features. They're good design that happens to be accessible because the designer experiences the world differently and built what works for him.
PRICING ACCESSIBILITY
$42/month must not be a barrier to people with disabilities who could genuinely benefit.
Future consideration: accessibility discount or scholarship program for users with documented disabilities and limited income.
LATTICE L1 is free forever. The language is accessible to anyone.
INTEGRATION
| System | Relationship |
|---|---|
| SPEC_OBI_OS_VISION.md | Four view modes (Classic Desktop / Bridge 2D / Bridge 3D / Bridge VR) provide a built-in accessibility gradient. Classic Desktop = most accessible. Bridge VR = least (requires hardware and physical capability). Users choose their level. |
| SPEC_BRIDGE_LAYOUT.md | Station accent colors must pass contrast checks. Visual indicators must not rely on color alone. |
| SPEC_BAND_MODE.md | Compositions must have visual notation alongside audio playback. |
| SPEC_BRIDGE_VIEWSCREEN.md | All seven panels must be screen-reader accessible with ARIA labels. |
| SPEC_TEACHING_PROTOCOL.md | Principle 4 (match the learner's level) includes matching accessibility needs. |
INVARIANTS
INV-01: WCAG 2.1 Level AA minimum. Not aspirational. Required. Test before launch.
INV-02: Color is never the only indicator. Every color has a corresponding symbol, text label, or pattern. A blind user and a sighted user receive equivalent information.
INV-03: All functionality available via keyboard. Mouse is a convenience, not a requirement.
INV-04: Plain language in all user-facing text. If a customer needs a technical degree to understand the interface: the interface is broken.
INV-05: The four view modes are a built-in accessibility gradient. Classic Desktop for maximum compatibility. Bridge VR for maximum immersion. The user chooses. No user is forced to a mode they cannot use.
INV-06: Accessibility is tested WITH people who use assistive technologies, not just checked against a spec. Automated tests catch syntax. Human testers catch usability. Both are needed before launch.
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042