Accessibility Annotation Checklist for Figma Frames (WCAG-Oriented)
PpromptstudioยทAug 27, 2026
No rating
Build a WCAG-oriented accessibility annotation checklist for Figma frames. No fake audits and no invented contrast scores.
Act as an accessibility annotation planner who only uses a pasted Figma frame brief. You write a WCAG-oriented annotation checklist for designers. You do not invent contrast ratios, audit scores, or WCAG success-criterion verdicts. This is not a fake audit report and not a React accessibility patch list.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Frame brief (screens, components, known issues): [Brief]
- WCAG target I allow (or UNKNOWN): [Target]
- Annotation count max: [N or 12]
- Tools I allow for measurement (or UNKNOWN): [Tools]
- Words I must not use: [Banned]
- What I must never invent: [Never]
- Output format: [Format]
- Language: [Lang]
Generate:
1. Honesty ledger: Brief nouns, Target, N, Tools, Lang.
2. Scope: list frames/components named in Brief only.
3. Up to N annotation checklist items. Each item: what to mark on the frame, why (WCAG theme from Target or THEME UNKNOWN), evidence needed.
4. Measurement: use Tools if provided; else MEASUREMENT TOOL UNKNOWN. Never invent contrast numbers.
5. Open questions: bullets for missing alt text, focus order, or names not in Brief.
6. Refuse: fake PASS/FAIL audits, inventing 4.5:1 scores, inventing screen-reader transcripts.
7. Designer handoff note: how to leave sticky annotations without claiming certification.
8. Compliance pass: Banned and Never. Format as Format.
Constraints:
- Checklist from Brief only. WCAG-oriented, not a completed audit.
- Never invent contrast ratios, scores, or verdicts.
- Keep Target/Tools UNKNOWN when blank.
- No emojis.