Public accessibility report · reviewed August 1, 2026
Access is a product requirement.
hippocampOS targets WCAG 2.2 Level AA across its public website and authenticated workspace. Because WCAG 2.2 extends WCAG 2.1, that target also carries the WCAG 2.1 A and AA requirements forward.
2.2 AA
current target
2.1 AA
included baseline
2
themes tested
320 px
reflow viewport
01 · What the target means
One current standard, with the previous standard inside it.
The W3C recommends WCAG 2.2 for new and updated accessibility work. WCAG 2.2 extends WCAG 2.1, so meeting the applicable A and AA requirements in 2.2 also covers the applicable WCAG 2.1 requirements.
Honest boundary
This report documents engineering controls and repeatable tests. It is not an independent audit, legal opinion, or blanket claim that every third-party screen is certified accessible.
W3C guidance expects a combination of automated testing and human evaluation. Manual assistive-technology review remains part of the release process and is tracked separately from automated results.
02 · WCAG principles
Perceivable. Operable. Understandable. Robust.
01WCAG 1.x
Perceivable
Semantic headings, text alternatives, responsive reflow, readable contrast, light and dark themes, and content that does not rely on color alone.
02WCAG 2.x
Operable
Keyboard access, visible focus, bypass navigation, reduced motion, minimum target sizing, logical focus order, and no keyboard traps in shared dialogs.
03WCAG 3.x
Understandable
Descriptive page titles, explicit labels, predictable navigation, announced status updates, clear errors, and confirmation for destructive actions.
04WCAG 4.x
Robust
Native controls, semantic landmarks, accessible names, correct roles and states, and regression checks for assistive-technology compatibility.
03 · WCAG 2.2 additions
The newer criteria are implemented deliberately.
These are the WCAG 2.2 A and AA additions most directly reflected in the current product interface.
| Criterion | Requirement | hippocampOS implementation |
|---|---|---|
| 2.4.11 | Focus Not Obscured (Minimum) | A global, high-contrast focus indicator and visible skip link keep keyboard location apparent above sticky interface regions. |
| 2.5.7 | Dragging Movements | Core platform actions use buttons, links, selects, and file inputs; important workflows do not require drag-only operation. |
| 2.5.8 | Target Size (Minimum) | Standalone controls receive a 24 by 24 CSS-pixel minimum, while primary actions generally use larger touch targets. |
| 3.2.6 | Consistent Help | Support and feedback entry points use stable labels and locations, with public Contact, Privacy, Security, and Terms routes. |
| 3.3.7 | Redundant Entry | Account and connector flows reuse known session context instead of repeatedly asking for information already provided where the workflow permits. |
| 3.3.8 | Accessible Authentication (Minimum) | Authentication uses familiar provider-based sign-in without a memory puzzle or cognitive-function test imposed by hippocampOS. |
04 · Verification evidence
Accessibility is tested with every change.
Automated rules
axe-core WCAG 2 A, 2 AA, 2.1 A/AA, and 2.2 AA tags
Public routes
10 route checks, including this report, in light and dark themes
Responsive reflow
Public pages checked at a 320 CSS-pixel viewport
Keyboard
Skip navigation and composite tab arrow-key behavior covered
Motion
Platform-wide prefers-reduced-motion behavior covered
Code quality
jsx-a11y linting, TypeScript, unit tests, and production build
Public-route automation currently reports no detectable WCAG A or AA violations in the tested light and dark states. Credentialed smoke tests extend the same axe rules across authenticated and administrative routes.
05 · Continuous review
Passing automation is the floor, not the finish line.
Manual review covers keyboard-only operation, focus order, zoom and reflow, meaningful labels, destructive confirmations, and screen-reader announcements. New connectors and third-party authorization screens are reviewed at their product boundaries, while provider-owned interfaces remain subject to the provider's accessibility implementation.
If an accessibility barrier prevents you from using hippocampOS, tell us the route, control, assistive technology, browser, and expected result. Accessibility issues are treated as product defects.