Frontory

Open code, practice, and notes →

Download source with English comments · for reading

HTML · 27 Checking Image Failure and Zoom

Series contents · Technology map

Stage: Accessibility Review and Card Integration · Editable example · Storage ID: html-step-27

Goals and learning outcomes

Prerequisites

The work and experiment records from Unit 26, “HTML Errors and Browser Recovery”.

Key concepts and explanations

Alternatives

Essential information and the meaning of controls must remain when resources are missing. alt and body descriptions work together in failure cases.

Zoomed Environments

Zoom reduces the area visible at once. Check clipped content and focus navigation problems through actual operation.

Practice setup

First check the execution scope guidance on the example screen. The following environment is for extending the assignment in a separate project. Implement it yourself in a separate local project and check it with browser developer tools. Prepare HTML and any necessary image/media files in a separate folder and open them through a local HTTP server. Check with the Elements and accessibility panels and actual keyboard operation.

The linked example is a starting point. It does not implement every task below. Complete work beyond its supported scope in a separate project.

Practice tasks

  1. In audit.html, prepare 6 cards, image failure, and two zoom levels.
  2. Break the image paths on the card page and navigate with the keyboard at 200%·400% zoom.
  3. Run with 6 cards, image failure, and two zoom levels. Results to check: Card titles and action purposes remain with 6 failed images. There is a record of reaching every control at both zoom levels. Record expected and actual results separately.

Variables to observe

VariableBaselineChangeExpected change / hypothesis
Zoom100%400%Pre-run hypothesis: More line wrapping and scrolling will be needed. Keep other conditions fixed and record the actual result separately after running.

Predictions in this table are not measured results. Change one condition at a time and record why the actual result differs.

Completion criteria

Self-check

  1. Do alternative text and body content repeat unnecessarily?
  2. Should clipped controls be fixed in HTML or CSS?

Official references

Linked example and execution scope

Example source · Runtime environments and limits

Reduce preview width to check reflow, and separately test actual browser zoom at 200%·400%. Scope document body/html selectors within Shadow DOM. @media responds to the outer preview viewport, while the width slider changes only the container. Network access, form navigation, and iframe execution are restricted.

Source code and records are not overwritten automatically. Resetting an existing example also preserves your notes.

Next learning

Previous: HTML Errors and Browser Recovery · Next: Accessible Learning Cards

Open code, practice, and notes →