◆ HTML

Document web-accessible software designs

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 taskTake this Figma design for the new customer portal and generate the web page structure and…+
Take this Figma design for the new customer portal and generate the web page structure and styling. Make sure it's responsive for mobile and desktop, and uses our standard component library for navigation and form elements.
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 acceptI need to turn this design into web-accessible content for our new customer portal. Focus on…+
I need to turn this design into web-accessible content for our new customer portal. Focus on making sure all interactive elements have proper ARIA labels and keyboard navigation, and that color contrast meets WCAG AA standards. We can't afford another accessibility audit failure.
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 legal team just sent back the new portal design, saying it fails accessibility standards…+
Our last web design was rejected for accessibility issues by the legal team.
The legal team just sent back the new portal design, saying it fails accessibility standards again, specifically for screen reader navigation and color contrast. I thought I followed all the guidelines, but clearly I missed something critical. What are the most common, subtle accessibility pitfalls in modern web designs that I might be overlooking, and what's the fastest way to diagnose and fix them before Friday's re-submission?
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 scrambling to fix accessibility issues late in the development cycle for new web…+
I keep getting caught off guard by accessibility requirements after development is 'done'.
I'm constantly scrambling to fix accessibility issues late in the development cycle for new web features, leading to missed deadlines and re-work. What's one habit I can change to integrate accessibility thinking earlier into the design and web page authoring process, so it's not an afterthought?
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 HTML'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.