Write Accessibility Annotation Notes

Write accessibility annotation notes from the following inputs:

Screen or component: [SCREEN OR COMPONENT NAME]
Platform: [WEB / iOS / ANDROID / MULTI]
Design file context: [FIGMA LINK OR DESCRIPTION]
Primary user tasks: [TASK LIST]
Known issues or concerns: [LIST OR NONE]
Standards target: [WCAG 2.2 AA OR OTHER]
Audience for notes: [DESIGNERS, ENGINEERS, QA]

Requirements:
1. Annotate focus order, labels, roles, error messaging, contrast risks, and keyboard or screen reader needs.
2. Use clear, actionable language engineers can implement. Avoid vague "make accessible" comments.
3. Separate must-fix issues from nice-to-have improvements.
4. Do not invent product behavior. Flag unknowns as questions for the team.
5. Keep notes scannable with short bullets and IDs (A1, A2, ...).

Deliverables:
1. Annotation note list grouped by area (structure, interaction, content, visuals).
2. Priority table (must-fix vs improve) with rationale.
3. A short QA checklist for verifying the annotations after build.