◆ Salesforce

Solve LWC accessibility warnings

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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to make sure the custom 'Deal Status' component on the Opportunity page meets…+
I need to make sure the custom 'Deal Status' component on the Opportunity page meets accessibility standards. Check for sufficient color contrast, keyboard navigation, and proper ARIA labels so all users can interact with it.
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 this new 'Deal Status' component to production, make sure it’s truly usable by…+
Before we push this new 'Deal Status' component to production, make sure it’s truly usable by everyone. Beyond the basic checks, how can we ensure the visual indicators for status changes are clear for colorblind users, and that screen readers announce updates intuitively without overwhelming the user? I want our sales team to rely on this without friction.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe accessibility team just hit me with a critical finding on the 'Pipeline Health' component.…+
Our internal accessibility audit just flagged the 'Pipeline Health' component for having multiple low-contrast elements and unannounced state changes.
The accessibility team just hit me with a critical finding on the 'Pipeline Health' component. They found several text elements with insufficient contrast against their backgrounds and said screen readers aren't announcing when the health status changes from 'Good' to 'At Risk.' I'm worried we'll miss our compliance deadline. I thought I followed the style guide, but clearly I missed something fundamental. What’s the most common reason for these contrast and state-change issues, and what’s the quickest, most reliable way to fix them without breaking the component's existing functionality?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly battling accessibility warnings when building new custom components, which…+
I keep getting accessibility warnings on almost every new custom component I build, slowing down deployments.
I'm constantly battling accessibility warnings when building new custom components, which delays deployments and frustrates the team. I try to address them during development, but I often miss things until testing. This adds significant rework. What habit should I change in my development process to consistently build accessible components from the start, especially regarding keyboard navigation and screen reader compatibility, so I'm not always playing catch-up?
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 Salesforce'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.