◆ Figma

Develop web-accessible software

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCan you review the current design system components and make sure they meet WCAG 2.1 AA…+
Can you review the current design system components and make sure they meet WCAG 2.1 AA accessibility standards? Focus on color contrast and keyboard navigation for the primary CTA buttons and form fields.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we push these new components to production, can you help me audit them for web…+
Before we push these new components to production, can you help me audit them for web accessibility? I need to ensure they're usable for everyone, especially those relying on screen readers, so we avoid any compliance issues down the line.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new legal requirement for web accessibility just dropped, and our current product build is…+
A new legal requirement for accessibility just dropped, and our current build is almost complete.
A new legal requirement for web accessibility just dropped, and our current product build is nearly finished. The engineering lead is pushing to launch as planned, but I'm afraid we'll be non-compliant and face fines. I can't tell them to halt the launch without a clear path forward. What's the immediate risk, and what's the best next step to address this without causing a huge delay?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find that web accessibility considerations are pushed to the very end of our…+
Accessibility always feels like an afterthought, leading to rushed fixes at the end of projects.
I consistently find that web accessibility considerations are pushed to the very end of our development cycles, leading to rushed, expensive fixes and a lot of stress. It impacts our team's morale and the quality of our product. What habit should I change to integrate accessibility earlier and more consistently into our design and development process?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Figma's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.