◆ JavaScript

Implement accessibility features

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 taskMy page needs to meet basic accessibility requirements before the sprint demo. Add keyboard…+
My page needs to meet basic accessibility requirements before the sprint demo. Add keyboard focus order to the form on the checkout page, ensure ARIA labels read the product name and price for the screen reader, and make the modal dismissible with Escape and by clicking outside. Test with VoiceOver on macOS and Tab navigation and report any remaining failures by Thursday.
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 I hand this to QA, make the accessibility fixes obvious to a reviewer: put the product…+
Before I hand this to QA, make the accessibility fixes obvious to a reviewer: put the product name and price into visible text and into aria-labels, surface the current focusable element in a high-contrast outline, add a short note at the top explaining the escape/overlay dismiss behavior, and list any interactive bits that still need semantics (e.g., custom sliders).
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just got a bug from Sam in QA: keyboard users can’t reach the promo code field in the…+
Keyboard users report they cannot reach the promo code field.
I just got a bug from Sam in QA: keyboard users can’t reach the promo code field in the checkout flow. The page has custom widgets and a floating sticky header. I’m worried we added tabindex="-1" somewhere or the sticky header is stealing focus. I cannot reproduce reliably on my machine and don’t know which widget intercepts Tab. What's the most likely cause and the fastest fix to restore keyboard order?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross three releases we keep getting accessibility regressions in checkout and product pages:…+
We repeatedly ship UI that keyboard and screen-reader users can't use.
Across three releases we keep getting accessibility regressions in checkout and product pages: invisible focus states, missing ARIA on dynamic widgets, and modals that trap focus. We spend hours late in the sprint fixing them. Which two habits should we adopt to stop this bleed — what checks to add to PRs and what small developer workflow change will catch regressions early?
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 JavaScript'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.