> 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_34/session_02_accessibility_and_compact_input.md). # Session 02: Accessibility And Compact Input **Session ID**: `phase34-session02-accessibility-and-compact-input` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Fix AI Rogue Play accessibility and compact-input gaps so the runtime state and all core verbs are reachable without relying on keyboard-only canvas behavior. *** ## Migrated Audit Source * Former audit session: 2026-06-25 Session 10 Accessibility And Input, with related coverage synthesis from Sessions 12 and 14. * Primary findings: AR-D6-001, AR-D6-002, AR-D6-003, AR-D8-001, and AR-D8-003. * AR-D6-001 evidence: the mounted Pixi canvas has a static `role="img"` / `aria-label` while `render-model.ts` already computes a richer dynamic summary that is not applied to the canvas, an `aria-describedby` target, or an `aria-live` surface. * AR-D6-002 evidence: keyboard can dispatch `inspect` and `target-next`, but compact controls expose movement, Strike, Surge, and Protocol only. * AR-D6-003 evidence: `largeHudLabels` is exposed and persisted, but no runtime bridge, render preference, or effects branch changes HUD behavior. * Preserve the audit distinction: keyboard users can currently play, but default enablement needs screen-reader-visible runtime state and touch parity for advertised verbs. * Source details are preserved in `PRD_phase_34.md` Appendix A. *** ## Scope ### In Scope (MVP) * Expose the dynamic `renderModel.summary` through a stable accessible surface such as `aria-describedby`, an off-canvas region, or an equivalent bridge. * Ensure the summary updates on meaningful turn changes and includes relevant input, motion, and run-state details. * Add compact/touch controls for Inspect and Next target or replace them with an equally reachable touch interaction. * Implement real Large HUD behavior with bounded layout coverage, or remove or disable the unsupported preference. * Update focused unit/e2e coverage for the changed controls and accessible summary behavior. ### Out of Scope * Visual redesign of the AI Rogue Play surface. * New gameplay verbs or balance changes. * Default enablement. *** ## Prerequisites * [ ] Session 01 coverage exists or equivalent test coverage is added in this session before behavior changes. * [ ] Current input-mode resolver behavior remains the source of truth for `auto`, `keyboard`, and `compact` modes. *** ## Deliverables 1. Runtime accessibility implementation for dynamic board/run summaries. 2. Compact/touch access to Inspect and Next target behavior or an explicit removal of unreachable commands from compact mode. 3. Large HUD implementation or removal with matching Settings/Loadout copy. 4. Focused tests and mobile/public-demo coverage updates where applicable. *** ## Success Criteria * [ ] Screen-reader-visible runtime summary changes after movement. * [ ] Touch-only users can reach the same intended inspect/target behavior as keyboard users, or the UI no longer advertises unreachable behavior. * [ ] Large HUD preference has a visible tested effect or no longer appears as an active preference. * [ ] AI Rogue remains browser-local in public-demo mode. --- # 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_34/session_02_accessibility_and_compact_input.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.