> 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/sessions/phase08-session06-mobile-and-accessibility-certification-evidence/tasks.md).

# Task Checklist

**Session ID**: `phase08-session06-mobile-and-accessibility-certification-evidence` **Total Tasks**: 21 **Estimated Duration**: 3-4 hours **Created**: 2026-05-31

***

## Legend

* `[x]` = Completed
* `[ ]` = Pending
* `[P]` = Parallelizable (can run with other \[P] tasks)
* `[SNNMM]` = Session reference (NN=phase number, MM=session number)
* `TNNN` = Task ID

***

## Progress Summary

| Category       | Total  | Done   | Remaining |
| -------------- | ------ | ------ | --------- |
| Setup          | 3      | 3      | 0         |
| Foundation     | 5      | 5      | 0         |
| Implementation | 9      | 9      | 0         |
| Testing        | 4      | 4      | 0         |
| **Total**      | **21** | **21** | **0**     |

***

## Setup (3 tasks)

Initial configuration and environment preparation.

### apps/web

* [x] T001 \[S0806] Verify analyzer state, completed Sessions 01-05 prerequisites, `apps/web` package context, and Phase 08 S0806 routing before implementation (`.spec_system/PRD/phase_08/session_06_mobile_and_accessibility_certification_evidence.md`)
* [x] T002 \[S0806] Review Phase 06 mobile/accessibility checklist, current Playwright projects, browser guards, web README, public-demo validation docs, and release no-overclaim boundaries (`.spec_system/archive/phases/phase_06/mobile_accessibility_acceptance_checklist.md`)
* [x] T003 \[S0806] Create implementation notes with the evidence scope, supported surfaces, and explicit no formal WCAG/mobile certification claim (`.spec_system/specs/phase08-session06-mobile-and-accessibility-certification-evidence/implementation-notes.md`)

***

## Foundation (5 tasks)

Core structures and base implementations.

### Cross-surface Evidence

* [x] T004 \[S0806] Create the Phase 08 mobile/accessibility evidence artifact with supported surfaces, viewport classes, evidence types, manual-review slots, screenshots, and certification no-claim wording (`.spec_system/PRD/phase_08/mobile_accessibility_certification_evidence.md`)
* [x] T005 \[S0806] Extend browser guard helpers for text clipping, visible text fit, contrast-critical checks where feasible, accessible names, and sanitized diagnostics (`tests/e2e/support/browserGuards.ts`)

### apps/web

* [x] T006 \[S0806] Extend app browser evidence setup for settings, replay, export, scan, notifications, local erasure, War Room, and release-critical overlays with explicit loading, empty, error, offline, and privacy-safe states (`tests/e2e/app.e2e.ts`)
* [x] T007 \[S0806] \[P] Extend focused web mobile/accessibility component fixtures for labels, focus return, reduced motion, duplicate-action guards, local-only copy, and no-overclaim wording (`apps/web/tests/MobileAccessibility.test.tsx`)

### public-demo

* [x] T008 \[S0806] \[P] Extend public-demo browser evidence setup for splash, cockpit, audio visible equivalents, offline shell, synthetic limitations, and mobile layout assertions (`tests/e2e/public-demo.e2e.ts`)

***

## Implementation (9 tasks)

Main feature implementation.

### apps/web

* [x] T009 \[S0806] Add app desktop/mobile cockpit shell evidence for battlefield, rails, title bar, command controls, focus visibility, no horizontal overflow, no region overlap, and privacy-safe visible text (`tests/e2e/app.e2e.ts`)
* [x] T010 \[S0806] Add app desktop/mobile settings, notifications, scan, replay, export, and local erasure evidence with state reset or revalidation on re-entry, duplicate-trigger prevention while in-flight, and no trusted-erasure overclaim wording (`tests/e2e/app.e2e.ts`)
* [x] T011 \[S0806] Add app desktop/mobile War Room and overlay evidence for diagnostics, room lifecycle, remote context, command palette, keyboard shortcuts, heatmap, standings, focus return, and no hosted-identity or production-validation overclaim wording (`tests/e2e/app.e2e.ts`)
* [x] T012 \[S0806] Add or extend component tests for dialog semantics, accessible labels, reduced-motion static indicators, long-text fit, focus return, local-only copy, and no-overclaim assertions (`apps/web/tests/MobileAccessibility.test.tsx`)
* [x] T013 \[S0806] Apply targeted cockpit layout and region fixes discovered by evidence with stable dimensions, mobile reachability, text fit, and platform-appropriate accessibility labels (`apps/web/src/components/Layout.tsx`)
* [x] T014 \[S0806] Apply targeted title bar shell-control fixes discovered by evidence with focus management, platform-appropriate accessible names, stable touch targets, and explicit unavailable-state handling (`apps/web/src/components/TitleBar.tsx`)

### public-demo

* [x] T015 \[S0806] Add public-demo desktop/mobile evidence for splash, battlefield, roster, mission log, music/voice visible equivalents, reduced motion, offline shell, keyboard reachability, and synthetic/no-server limitation copy (`tests/e2e/public-demo.e2e.ts`)
* [x] T016 \[S0806] Apply targeted public-demo mobile, accessible-name, reduced-motion, visible-equivalent, or no-overclaim fixes discovered by evidence (`public-demo/index.html`)

### Documentation

* [x] T017 \[S0806] Update UX PRD, release guide, web README, and public-demo validation docs with evidence commands, supported coverage, residual risks, and no formal certification claim (`.spec_system/PRD/PRD_UX.md`)

***

## Testing (4 tasks)

Verification and quality assurance.

### apps/web

* [x] T018 \[S0806] Run focused web component tests and focused Biome checks for changed web test/component files (`apps/web/tests/MobileAccessibility.test.tsx`)
* [x] T019 \[S0806] Run Playwright app desktop/mobile and public-demo desktop/mobile evidence projects, retaining screenshots and recording exact commands or blockers (`tests/e2e/app.e2e.ts`)

### Cross-surface Evidence

* [x] T020 \[S0806] Run docs no-overclaim review plus ASCII, LF, whitespace, and `git diff --check` validation over changed evidence, docs, tests, and components (`.spec_system/PRD/phase_08/mobile_accessibility_certification_evidence.md`)
* [x] T021 \[S0806] Record command outcomes, screenshot/manual-review status, residual risks, and Session 07/08 handoff in implementation notes and the evidence artifact (`.spec_system/specs/phase08-session06-mobile-and-accessibility-certification-evidence/implementation-notes.md`)

***

## Completion Checklist

Before marking session complete:

* [x] All tasks marked `[x]`
* [x] All tests passing or blockers recorded with exact commands
* [x] All files ASCII-encoded
* [x] implementation-notes.md updated
* [x] Ready for the validate workflow step

***

## Next Steps

Run the implement workflow step to begin AI-led implementation.


---

# 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/sessions/phase08-session06-mobile-and-accessibility-certification-evidence/tasks.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.
