◆ HTML

Play audio on a webpage

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 taskAdd the 'welcome_message.mp3' file to the homepage, playing automatically when a user lands on…+
Add the 'welcome_message.mp3' file to the homepage, playing automatically when a user lands on the page, so it's ready for the marketing campaign launch on Monday.
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'm adding background music to the new product landing page. Make sure it plays automatically…+
I'm adding background music to the new product landing page. Make sure it plays automatically but quietly, with a clear pause button, and doesn't restart if someone navigates to another page and comes back. The goal is a subtle, professional feel, not an annoyance, for the buyer.
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 latest podcast episode is embedded on the blog, but I'm getting emails from users saying…+
The new podcast episode isn't playing for some users, and I don't know why.
The latest podcast episode is embedded on the blog, but I'm getting emails from users saying it's not playing for them, especially on their iPhones. I'm worried we're losing listeners right after launch. I've checked the file path, but I can't tell if it's a browser issue or something with how it's embedded. What's the most likely cause, and what's the quickest way to diagnose and fix it before more people complain?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I add an audio file, I face unexpected issues with playback on different devices or…+
Audio files always seem to have playback issues or accessibility problems.
Every time I add an audio file, I face unexpected issues with playback on different devices or forget about accessibility for screen readers. I waste time fixing these after the fact. What's the key habit I should adopt when embedding audio to ensure it's robust and accessible from the start, avoiding these recurring post-launch fixes?
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.