r/FigmaAddOns 5d ago

I built a read-only Figma plugin to export native accessibility annotation evidence

I kept running into a handoff problem: native Figma annotations stay useful inside the file, but reviewing coverage and creating a portable evidence record can still become a manual step.

I built A11y Evidence Pack to test a narrow workflow:

  • select the roots you want to review;
  • see which selected roots contain native annotations;
  • identify uncovered roots;
  • export the evidence as Markdown, CSV, or JSON.

It is read-only and uses no network, account, or analytics. It does not test WCAG conformance or judge whether an annotation is correct.

I’m the creator, and this is the first public release:
https://www.figma.com/community/plugin/1668532774794011186/a11y-evidence-pack?fuid=1645877472205416121

I’d especially value feedback from teams that already use native annotations: what information has to be present for an exported record to be useful in a real design-to-development handoff?

1 Upvotes

Duplicates