> 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_08/session_06_mobile_and_accessibility_certification_evidence.md).

# Session 06: Mobile and Accessibility Certification Evidence

**Session ID**: `phase08-session06-mobile-and-accessibility-certification-evidence` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~14-22 **Estimated Duration**: 2-4 hours

***

## Objective

Produce release-grade mobile and accessibility evidence for the cockpit and public demo surfaces that Phase 08 intends to claim.

***

## Scope

### In Scope (MVP)

* Define supported viewport, browser, input, reduced-motion, focus, dialog, screen-reader-label, contrast, and text-fit criteria for release claims.
* Run or add browser evidence for cockpit, War Room, settings, replay, export, scan, notifications, local erasure, public demo, and release-critical overlays.
* Add targeted fixes for overlap, unreachable controls, broken focus return, missing labels, reduced-motion regressions, or visible fallback gaps found during evidence gathering.
* Record what the evidence proves and what remains outside formal certification.
* Update UX PRD, web README, release docs, and validation notes.

### Out of Scope

* Broad visual redesign.
* Claiming formal WCAG or mobile certification without matching manual or third-party evidence.
* Enabling hosted services, analytics capture, push delivery, public replay hosting, remote access, or real executors.

***

## Prerequisites

* [ ] Session 01 release claim gates are defined.
* [ ] Existing Phase 06 mobile and accessibility evidence is reviewed.
* [ ] Release-critical web surfaces are available in local browser tests.

***

## Deliverables

1. Mobile and accessibility release evidence.
2. Focused fixes and tests for release-critical issues found.
3. Documentation that distinguishes automated evidence, manual review, and formal certification status.

***

## Success Criteria

* [ ] Supported release surfaces are usable on declared mobile and desktop viewport classes without overlapping controls or inaccessible critical actions.
* [ ] Dialogs, drawers, keyboard paths, labels, reduced motion, and fallback states have release evidence.
* [ ] Docs do not overclaim certification beyond available evidence.


---

# 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_08/session_06_mobile_and_accessibility_certification_evidence.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.