# Editable project scope and accessibility review

This is an illustrative scope for the published local SDK lobby. No reviewer has approved it; no UI accessibility test has been conducted. Download scope.json and validate.mjs together; use Node.js 22 or later and run `node validate.mjs`. Expected: checks passed, ready false, six unresolved requirements. This intentionally refuses to call the example approved.

The source sample establishes local state transitions only. Before building a UI, name its owner, intended users, devices, input methods, acceptance criteria, exclusions and dependencies. Tie every observation to the exact artifact/version/hash. The JSON is editable and contains no real account, payment or project credentials.

## Proposed UI and error cases

- Two labeled player slots have explicit not-ready/ready state; changing a state must be possible by keyboard and announced when needed.
- Start is unavailable until the actual minimum and readiness conditions hold. Explain the missing condition. Attempting a premature start in the SDK sample is tested.
- A full lobby rejects an extra slot. Keep the two existing slots intact and explain how to free one. This SDK error is tested; a UI implementation is not.
- End/reset returns to an understandable lobby state. Test repeat actions, focus restoration and an accessible error/success announcement on the implemented UI.
- At narrow widths and zoom, retain labels and action order. Review contrast, keyboard traps, timing and reduced-motion behavior with intended users and assistive technology.

## Human review record

Record reviewer name, relevant expertise, scope and conflicts; device/browser/assistive-technology versions; task sequence; expected and observed results; pass/fail/not-tested; severity; correction; re-test and exact approved artifact hash. A general accessibility statement is not a conformance certification. A failed or not-tested criterion must be resolved or explicitly accepted as a documented limitation by the decision owner before calling a scope ready.

The validator only checks structural completeness and unresolved requirements. It does not authenticate a person, judge accessibility, verify a date/hash against an artifact or authorize release. Keep release controls separate. No actual project activation or deployment is created by downloading this scope.