HTML Media
Image maps made regions of one picture clickable. Media on the web is broader: still images, sound, moving pictures, and sometimes nested pages or hosted players. HTML gives purpose-built tags so browsers can display or play those resources with controls and accessibility hooks. This session is your map before Video, Audio, YouTube, and Plug-ins go deep.
What “media” means here
In everyday course language, media means content that is not only paragraphs and headings — photos, icons, voice clips, demos, and embeds. Using the right element helps browsers expose native play UI, download the right resource type, and give assistive tech a clearer role than a mystery <div> full of scripts.
Direct answer
- Images →
img(and sometimespicturefor multiple files) - Sound →
audio - Movies and clips →
video - Nested browsing (maps, other sites’ players) → often
iframe
Prefer the matching element for the job. Give userscontrolson audio and video unless you have a strong, accessible custom player. When media carries important information, plan a text alternative, caption, or transcript.
Building blocks at a glance
📊 Media building blocks
| Element | Typical use |
|---|---|
| img / picture | Photos, diagrams, icons |
| audio | Music, voice, sound effects |
| video | Clips and recorded demos |
| iframe | Embed another HTML page or hosted player |
A tiny sampler
You already know img. Here is how audio and video sit beside it in a first practice page — paths are examples; use files you actually have when you try this at home.
Tiny media sampler
html<img src="images/note.png" alt="Music note icon">
<audio controls src="media/hello.mp3"></audio>
<video controls width="320" src="media/demo.mp4"></video>
Reading the sampler
imgstill needssrcand meaningfulaltaudioandvideousesrc(or nestedsourcechildren in later lessons) and benefit fromcontrolswidthonvideocan reserve layout space while the file loads- Empty files or wrong paths fail the same way other assets do — check folders early
Controls are a beginner habit
The controls attribute asks the browser to show play, pause, and related UI. Autoplaying sound without a clear user action is often blocked and usually annoying. Start with visible controls. Custom players come later if a project truly needs them.
Audio and video with controls
html<audio controls src="media/lesson-intro.mp3"></audio>
<video controls width="480" src="media/walkthrough.mp4"></video>
Choosing the right tool
- Podcast or voice note →
audio - Screen recording or clip →
video - Photo or diagram →
img/picture - Map widget or third-party player page → often
iframe(with performance and security awareness)
Do not force a video into an image tag, or a whole external app into a mysterious script blob, when a native element exists.
Accessibility and meaning
If the media teaches something, plan how a person who cannot hear or see it still gets the idea: alt for informative images, captions for spoken video, transcripts for long audio. Decorative motion without information should not trap focus or autoplay loudly. Later specialized lessons will go deeper; lock the habit now.
iframe costs (preview)
iframe embeds another browsing context. That is powerful for maps and hosted players, and it also brings another page’s scripts, cookies, and layout weight into yours. Use it when nesting is the real goal — not as a default for every media file you host yourself. Native audio / video / img stay simpler for your own files.
How the next lessons fit
After this map: Video and Audio teach attributes, multiple sources, and practical file habits. Plug-ins and YouTube cover older or hosted patterns. Iframe goes deeper on embedding. Treat this page as the directory; treat those pages as the workshops.
Practice in your editor
- From the table, name which element you would pick for a podcast file (
audio). - Add one
imgto a practice page with clearalt(you already know this). - If you have a small mp3 or mp4, add
audioorvideowithcontrols. - Write one line in your notes: “captions/transcripts for spoken content.”
- Skim the titles of the next media sessions so the roadmap feels familiar.
Easy mistakes
- Autoplaying sound without controls or a clear user gesture
- Embedding huge videos with no sizing thought and no alternative text plan
- Using
iframefor every file when nativeaudio/video/imgwould do - Forgetting that iframes import another page’s security and performance costs
- Treating this overview as “enough forever” and skipping the specialized lessons when you actually publish media
Summary
- HTML media covers images, audio, video, and embeds
- Prefer the matching element for the job
- Give users controls and plan alternatives when media carries meaning
- Native tags for your own files; iframe when you truly nest another page or hosted player
- Next lessons specialize each type — this page is the map
🧠 Test Your Knowledge
Test Your Knowledge
Challenge yourself with this interactive quiz and see how well you understand the topic
📝 Instructions
- Read each question carefully
- Select the best answer for each question
- You can retake the quiz as many times as you want
- Your progress will be shown at the top