> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_35/session_03_runtime_accessibility_controls.md). # Session 03: Runtime Accessibility Controls **Session ID**: `phase35-session03-runtime-accessibility-controls` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Finish and verify AI Rogue touch, screen-reader, and Large HUD user paths. *** ## Scope ### In Scope (MVP) * Confirm the mounted canvas or associated DOM exposes the dynamic runtime summary through a stable accessible surface. * Confirm compact or touch controls can reach Inspect and target-next behavior. * Confirm the Large HUD Labels preference changes runtime presentation without label overlap, or remove/disable the preference if it is intentionally unsupported. * Extend runtime-canvas tests and mobile e2e coverage for compact Inspect, target cycling, Large HUD behavior, and no-overflow mobile layouts. ### Out of Scope * Adding new gameplay commands beyond the existing runtime command union. * Redesigning the full AI Rogue Play surface. *** ## Prerequisites * [ ] Session 01 has confirmed which accessibility items remain live. * [ ] Session 02 coverage protects existing assistive-summary behavior. *** ## Deliverables 1. Runtime bridge, renderer, settings, or controls changes for remaining AR-D6-002 and AR-D6-003 gaps. 2. Positive accessibility and mobile coverage for compact/touch operation. 3. Evidence that existing keyboard behavior remains intact. *** ## Success Criteria * [ ] Touch-only users can open inspect details and cycle targets. * [ ] Screen-reader users receive current runtime state from the Play surface. * [ ] Large HUD either visibly affects bounded runtime layout or is absent from settings and persistence-facing UI. * [ ] Mobile Play, Ledger, Loadout, and Settings route checks still pass. ## Folded Audit Detail Routed To This Session ### Finding IDs Owned * AR-D6-001: canvas accessibility moved from static `aria-label` to dynamic runtime summary or associated DOM surface. * AR-D6-002: compact/touch mode needs controls for `inspect` and `target-next`; keyboard already maps `KeyE` and `Tab`. * AR-D6-003: Large HUD Labels preference must have visible bounded runtime effect or be removed/disabled until supported. * AR-D8-003: compact input and Large HUD preferences need positive UI coverage. ### Source Locations From Audit * `src/extensions/ai-rogue/runtime/renderer.ts:1106`: historical static canvas accessible name. * `src/extensions/ai-rogue/views/runtime-canvas.tsx:134`: runtime command union includes inspect and target-next. * `src/extensions/ai-rogue/views/settings-view.tsx:59`: Large HUD Labels preference is persisted. * `src/extensions/ai-rogue/__tests__/runtime-canvas.test.tsx:1`: compact controls test anchor. ### User-Visible Contracts * Keyboard users and compact/touch users must have equivalent access to inspect details and target cycling. * Screen-reader users must receive current board/run state from the Play surface, not only a static canvas name. * Large HUD must either improve readability without overlap or not be exposed as a current setting. * Mobile route checks must cover Play, Ledger, Loadout, and Settings with no layout overflow or bridge requests. ### Acceptance Evidence Required * [ ] Runtime canvas or associated region exposes a changing summary. * [ ] Compact controls dispatch Inspect and Next target behavior. * [ ] Large HUD has positive layout assertions or the setting is absent. * [ ] Runtime-canvas unit tests and mobile e2e prove the accessible paths. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_35/session_03_runtime_accessibility_controls.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.