◆ HTML

Use obscure HTML elements effectively

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 taskI need to display a short, important quote from the CEO, 'Our future is built on trust,' on the…+
I need to display a short, important quote from the CEO, 'Our future is built on trust,' on the company homepage. Make sure it stands out but isn't just a bold paragraph. It should be semantically correct for a quote.
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 push this new product page live, I want to ensure the product features list is…+
Before I push this new product page live, I want to ensure the product features list is accessible and easy for screen readers to navigate. It's a long list, so make sure the structure helps users understand the hierarchy and relationships between features without getting lost.
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 audit just came back, and our main navigation links are flagged as ambiguous…+
The new accessibility audit flagged our main navigation as having ambiguous link purposes for screen reader users.
The accessibility audit just came back, and our main navigation links are flagged as ambiguous for screen reader users. The marketing team insists on concise link text like 'Products' and 'Services,' but the audit says that's not enough context. Our launch is next week, and I'm afraid of delaying it or getting a further penalty. What's the best way to add context for accessibility without making the visible navigation clunky or upsetting marketing?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent fixes for overlooked semantic structural issues after pages…+
I keep getting pulled into urgent fixes for overlooked semantic HTML issues after pages go live.
I keep getting pulled into urgent fixes for overlooked semantic structural issues after pages go live, costing us time and credibility with the QA team. Often, it's about using a div when a more specific element would have been better for accessibility or SEO. What habit should I change in my initial build process to catch these structural oversights before they become post-launch problems?
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.