Create a responsive image example with truthful alternative text, explicit dimensions and a documented source-selection test.
A fictional tutorial card displays a diagram at up to 700 CSS pixels. The package provides raster candidates 350, 700 and 1,400 pixels wide with the same 7:4 aspect ratio. The browser selects a candidate using layout, pixel density and its own conditions; exact selection is not guaranteed by markup alone.
| Candidate width | Height | Aspect ratio |
|---|---|---|
| 350 | 200 | 7:4 |
| 700 | 400 | 7:4 |
| 1400 | 800 | 7:4 |
A precise diagram can remain vector-based, while raster variants are useful for testing responsive markup. Preserve the same content across variants so size selection does not change meaning. The case uses an original educational diagram rather than decorative stock photography. File dimensions and byte size answer different questions.
Inspect the SVG and the three raster candidates.
Asset inventory
Record your result and evidence here or in a separate file.
Each variant has the stated ratio and the same diagram content.
Compare dimensions rather than assuming a filename is accurate.
Use width descriptors in srcset and a sizes value that reflects the actual CSS layout. The browser uses those hints rather than a simple device-name rule. A misleading sizes value can cause an unnecessarily large download. Keep a normal src fallback and a meaningful alt description.
Build the responsive image element for a 700-pixel maximum layout.
Responsive markup
Record your result and evidence here or in a separate file.
Descriptors match actual raster widths and sizes agrees with the CSS.
Measure the rendered slot before editing the candidate list.
Explicit dimensions establish the intrinsic ratio so the page can reserve space before the image loads. Alternative text should convey the diagram’s relevant relationship, while nearby text can provide detail. Do not duplicate a long caption word for word if it makes the reading experience repetitive.
Add dimensions, alt text and a concise text equivalent.
Accessible image block
Record your result and evidence here or in a separate file.
The information remains understandable with the image unavailable.
Describe the relationship shown, not merely a colorful diagram.
The picture element can select different compositions when the visual information must be framed differently. That is distinct from offering the same image at multiple resolutions. This case uses resolution switching, so extra art-direction markup is unnecessary unless a meaningful small-screen composition is created.
Explain whether the case needs picture or a single img with srcset.
Markup rationale
Record your result and evidence here or in a separate file.
The rationale separates composition changes from resolution changes.
Use the simpler structure when every candidate has identical content.
Test at two viewports and inspect currentSrc, rendered width and image dimensions. Cache and device scale can affect selection, so record conditions and avoid asserting a universal candidate. The prepared files can be checked locally; production CDN behavior would need separate verification after deployment.
Record candidate selection and layout at desktop and mobile widths.
Image test log
Record your result and evidence here or in a separate file.
Actual currentSrc values are recorded, not guessed from viewport alone.
Clear or account for cache when comparing requests.
Deliver the source diagram, three raster candidates, responsive HTML and two-viewport inspection log. Show that removing the image still leaves a useful text equivalent.
Candidate descriptors match real file dimensions and browser source selection is observed rather than promised.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
All candidates share width/height = 1.75. A 700-CSS-pixel slot on a high-density screen may need more than 700 source pixels, but the browser ultimately chooses. The test report should record currentSrc instead of claiming that every mobile device downloads the 350-pixel file.
This is a local responsive-image exercise, not a verified production CDN configuration or a bandwidth guarantee.