Let Claude check your accessibility
Accessibility reviews usually happen too late, after the dev files a ticket. With figma-cli they take one sentence, so you can run them before every handoff.
The one-sentence audit
Open your screen in Figma Desktop and say:
You get a report that points at the exact layers that fail, not a vague "improve contrast" note. From there you can fix things by hand or just keep talking: "fix the failing ones" works too.
What gets checked
- Color contrast. Text against its background, measured against the WCAG thresholds. 4.5 to 1 for body text, 3 to 1 for large text.
- Touch targets. Anything tappable should be big enough for a thumb. Small icon buttons are the usual offenders.
- Text sizes. Flags type that is too small to read comfortably on the target device.
- Color-blindness simulation. Shows your screen the way someone with deuteranopia or protanopia sees it. Red and green status colors look identical to about 8 percent of men, this is how you find out before launch.
Check just one thing
You do not have to run the whole audit every time. Each check works on its own:
Make it a habit
The audit is fast enough to run on every screen before it leaves your hands. A practical routine:
- Finish the screen.
- Say "run a full accessibility audit on this page".
- Fix what fails, or ask Claude to.
- Hand off.
Questions
Can an AI check WCAG contrast in Figma?
Yes. Ask Claude to run a full accessibility audit on the open page and Figma-CLI measures every text layer against the WCAG thresholds, then names the layers that fail instead of giving a general warning.
What contrast ratio does text need?
WCAG AA asks for 4.5 to 1 for body text and 3 to 1 for large text, measured between the text colour and the colour directly behind it.
Can it simulate colour blindness?
Yes. It renders a simulated copy of your screen next to the original for deuteranopia and protanopia, which is how you catch red and green status colours that look identical to about eight percent of men.