Home/Blog/How to Build an Accessibility Annotation Checklist for Figma
Blog

How to Build an Accessibility Annotation Checklist for Figma

P
promptstudio
How to Build an Accessibility Annotation Checklist for Figma

Annotation checklists invent 4.5:1 scores. Ask for evidence. Never stamp a fake AA PASS.

The matching generator is the Accessibility Annotation Checklist for Figma Frames (WCAG-Oriented) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Scope only frames named in the brief

Build a WCAG-oriented accessibility annotation checklist for Figma frames. No fake audits and no invented contrast scores. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

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]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Write checklist items as annotation asks

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  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.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Leave measurement tool UNKNOWN when blank

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • 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.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Refuse fake audits and invented contrast ratios

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (figma accessibility annotation checklist, wcag oriented figma frames, accessibility checklist no fake audits) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.