2.2 AA
production target
Otto targets WCAG 2.2 Level AA across production web surfaces, including school-themed experiences.
Accessibility
WCAG 2.2 AA is the target, with proof status kept honest.
Otto treats accessibility as a product requirement across the web app, documents, auth, media, mobile actions, and AI-visible workflows. VPAT/ACR publication and third-party audit are later milestones.
Keys
keyboard and focus
Core workflows need keyboard operation, visible focus, and focus that is not obscured.
Docs
generated records
Forms, transcripts, certificates, captions, transcripts, and alternate formats remain part of the accessibility scope.
Later
VPAT and audit
VPAT/ACR publication and third-party accessibility audit remain later milestones, not current claims.
Controls
Accessibility controls across the school experience.
The public statement is organized around the product areas a school will actually inspect.
Semantic structure
Pages should expose headings, landmarks, labels, and names that assistive technology can navigate.
Public pages and app shells use semantic HTML patterns, but final screen-reader review remains a production gate.
Review accessibility hardeningKeyboard and focus
Users should be able to move, act, and recover without a mouse.
Keyboard operation, visible focus, focus-not-obscured behavior, and touch target sizing are P0 accessibility requirements.
Review responsive shellContrast and status
School colors cannot make text unreadable or make status depend on color alone.
Theme colors need automated contrast checks, AA-safe tokens, and non-color-only status cues.
Review branding contrastTarget sizes and mobile
Primary actions need practical touch targets on phone and tablet screens.
PRD 39 requires at least 24 by 24 px targets, with 44 px for primary touch actions where practical.
Review mobile actionsReduced motion
Motion should never be required to understand or use the product.
Any animated or interactive visual should respect reduced-motion preferences and retain a static usable state.
Media alternatives
Lessons, recorded video, and visual proof need text alternatives that support varied learners.
Alt text, captions, transcripts, and authoring checks are product commitments; production workflows remain later.
Accessible authentication
Sign-in and recovery should work with assistive technology and password managers.
Accessible auth includes no cognitive CAPTCHAs, password-manager/passkey support, and usable recovery paths.
Review auth readinessGenerated documents
Official records need accessible output, not only accessible web forms.
Generated forms, transcripts, certificates, and PDFs need accessible output before final production claims.
Review sealed PDF proofTimed assessments and accommodations
Approved accommodations should apply automatically where timing affects access.
Formal accommodations are a P0 requirement for timed assessments, while production accommodation workflows remain gated.
Preview quiz flowScreen-reader testing
Core flows need real assistive-technology validation, not only automated checks.
VoiceOver and NVDA testing is required for login, dashboard, lessons, quizzes, attendance, signing, payments, and Study with Otto.
Accessibility feedback channel
Production routing is later. The intended public channel will let users report barriers, request alternate formats, and receive a response target. This page does not yet send email or create a support case.
Barrier reports
The public channel should let users report an accessibility barrier without signing in.
Alternate formats
Users should be able to request alternate formats for public materials and generated records.
Response target
A response target is required before public launch; production routing is not connected yet.
Severity routing
High-impact barriers should be triaged separately from content clarifications and alternate-format requests.
Human routing
Accessibility feedback should route to people who can triage product, content, document, or support issues.
What is not claimed yet
- VPAT / Accessibility Conformance Report is a later milestone.
- Third-party accessibility audit is a later milestone.
- Accessibility feedback channel needs production routing before public launch.
Scope
The statement covers more than the marketing page.
Accessibility work has to reach the things schools actually produce and students actually use.
WCAG 2.2 AA target for production web surfaces.
Semantic HTML and landmark structure.
Keyboard operation and visible focus.
AA-safe contrast and non-color-only status cues.
Practical 44 px touch targets.
Reduced-motion support.
Alt text, captions, and transcripts where media is used.
Accessible authentication and account recovery paths.
Accessible generated documents such as forms, transcripts, and certificates.