01 · Commitment
Accessibility is part of the interface contract.
Public pages are designed with semantic headings, visible focus, keyboard-operable links and controls, responsive reflow and respect for the browser’s reduced-motion preference.
The working target is WCAG 2.2 Level AA for the public platform. This statement is a commitment and status report, not a claim that every route has already completed a formal external audit.
- +Keyboard navigation
- +Visible focus indicators
- +Responsive text and layout
- +Reduced-motion support
02 · Known limitations
Dense diagrams and the game need deeper testing.
Some decorative world scenes are intentionally complex and may not communicate their atmosphere to non-visual users. Their essential information should remain available in nearby text.
Interactive diagrams, generated game content and the separately deployed game require route-by-route keyboard and assistive-technology testing as they evolve.
- +Complex interactive diagrams
- +Canvas or game-specific interfaces
- +Very dense directory views at high zoom
- +Translation consistency across new content
03 · Feedback
Describe the barrier, not only the page.
An accessibility report should include the URL, task you were trying to complete, input or assistive technology used and the point where progress stopped. A screenshot is helpful but not required.
Reports are prioritized by whether they block access to content, navigation, support or a playable action.
- +Exact route
- +Expected task
- +Browser and assistive technology
- +Observed barrier