Write Acceptance Criteria for a User Story

Write clear, testable acceptance criteria for this user story:

User story: As a [USER TYPE], I want to [ACTION], so that [OUTCOME].
Product / surface: [PRODUCT OR FEATURE AREA]
Platforms: [WEB, iOS, ANDROID, API, ETC.]
Priority: [MUST / SHOULD / COULD]
Known edge cases: [LIST ANY KNOWN EDGE CASES]
Out of scope: [WHAT THIS STORY DOES NOT INCLUDE]

Requirements:
1. Restate the user story in one clean sentence.
2. Write acceptance criteria in Given / When / Then format (or bullet criteria if Gherkin is overkill — pick the clearer option).
3. Cover happy path, validation rules, permissions, empty states, and failure states.
4. Include accessibility and analytics criteria if relevant to the story.
5. Define done: what must be true for QA to mark the story complete.
6. Flag open questions that block implementation or testing.

Deliverables:
1. 6–12 acceptance criteria that are specific and testable (no vague language like “works well”).
2. A short QA checklist (5–8 items) derived from the criteria.
3. Suggested test data examples for the main scenarios.