> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_06/session_06_mobile_cockpit_and_accessibility_hardening.md).

# Session 06: Mobile Cockpit and Accessibility Hardening

**Session ID**: `phase06-session06-mobile-cockpit-and-accessibility-hardening` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~16-24 **Estimated Duration**: 2-4 hours

***

## Objective

Harden the mobile cockpit and accessibility behavior for collaboration, core cockpit workflows, local orchestration, War Room states, and reduced-motion use.

***

## Scope

### In Scope (MVP)

* Verify and improve mobile reachability for battlefield, mission list, roster, hero detail, mission detail, settings, replay, local orchestration, and War Room collaboration controls.
* Fix text overlap, clipped labels, unstable board dimensions, inaccessible icon-only controls, focus loss, broken scroll regions, and pointer-only interactions found in supported mobile browser widths.
* Ensure collaboration controls expose accessible names, role/status semantics, visible focus states, duplicate-action guards, clear unavailable states, and bounded feedback.
* Preserve reduced-motion meaning for battlefield states, overlays, replay, achievements, collaboration context, and any new motion.
* Add or update Playwright checks and retained screenshots for desktop and mobile states that Phase 06 changes.
* Keep public-demo changes limited to parity or documentation needs if core app changes affect shared product vocabulary or approved assets.

### Out of Scope

* Building a native mobile app.
* Claiming full WCAG certification, app-store readiness, production-hosted mobile validation, or hosted collaboration certification.
* Adding push notifications, background sync, hosted accounts, public replay hosting, analytics, or real command execution.

***

## Prerequisites

* [ ] Sessions 02-04 collaboration states are available or explicitly unavailable in the UI.
* [ ] Existing desktop and mobile browser validation projects run locally.
* [ ] UX PRD responsive, accessibility, and reduced-motion acceptance criteria are reviewed.

***

## Deliverables

1. Mobile cockpit layout fixes and collaboration-control accessibility improvements.
2. Focused unit and browser tests for mobile, focus, labels, reduced motion, and no-overlap behavior.
3. Retained desktop and mobile browser evidence for changed Phase 06 surfaces.
4. Updated UX docs or package README notes for validated mobile behavior and remaining non-certification caveats.

***

## Success Criteria

* [ ] Critical cockpit and collaboration workflows remain reachable on supported mobile browser widths.
* [ ] Text, labels, buttons, panels, overlays, and battlefield elements do not overlap incoherently.
* [ ] Keyboard, pointer, screen-reader, focus, and reduced-motion behavior remains usable and documented for changed surfaces.


---

# 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://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_06/session_06_mobile_cockpit_and_accessibility_hardening.md?ask=<question>&goal=<endgoal>
```

`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.