Answer each phase's questions before reading its answer key. If an answer is difficult, return to the matching lesson and change its example until you can explain the result.
- What is the difference between View Source and the live Elements panel?
- Where does the browser look for a relative URL such as images/photo.svg?
- What belongs in head, and what belongs in body?
- Why should heading levels follow the content outline rather than font size?
- When should you use a link instead of a button?
- When should an image have empty alt text?
- Which list type represents steps whose order matters?
- When is article more appropriate than a plain div?
- View Source shows the original HTML response; Elements shows the current parsed document, which can change.
- It resolves relative to the current document URL unless another base URL is defined.
- Head holds metadata and resource links; body holds rendered document content.
- Headings communicate hierarchy to readers and assistive technology; CSS controls their size.
- Use a link to navigate to a URL or fragment; use a button to perform an action.
- Use empty alt for a purely decorative image that adds no information.
- An ordered list, ol.
- Use article for content that could stand on its own, such as a post or independent card.
- What connects a data cell to a straightforward row or column header?
- What do id and name each do for a form input?
- Why must radio buttons in one choice group share a name?
- Why is browser validation insufficient for a real server?
- What text alternatives might a spoken video need?
- Which native HTML pair creates a no-script disclosure?
- Why should page titles be unique?
- Why is zero validator errors not proof of a usable page?
- A th cell with an appropriate scope value, plus clear table structure.
- id connects labels and references to the control; name is the submitted key.
- A shared name makes them one mutually exclusive group.
- Requests can bypass browser checks; the server must validate what it receives.
- Captions for speech and important sound, and a transcript or equivalent text where needed.
- details and summary.
- They identify each page in tabs, history, search results, and link sharing.
- Validation checks syntax and some structure, not every semantic or usability decision.
- What happens when a browser does not understand one CSS declaration?
- Which selector is reusable across many elements: class or ID?
- Where can you see which of two competing declarations wins?
- How do rem and em differ?
- Why check contrast after adding transparency?
- Why avoid a fixed height for a text card?
- What is included in width under border-box sizing?
- How does display:none differ from visibility:hidden?
- It ignores that declaration and continues parsing other valid CSS.
- A class.
- In developer tools, inspect Styles and Computed values.
- rem refers to the root font size; em uses the element's font size for most properties, but the parent's font size when setting font-size itself.
- The underlying surface changes the final visible colors and contrast.
- Longer, translated, or zoomed text may overflow or be clipped.
- Content, padding, and border fit within the declared width.
- display:none removes layout space; visibility:hidden hides the element while retaining its space.
- What usually establishes the containing block for an absolutely positioned badge?
- Which Flexbox property puts items on additional lines?
- When is Grid a better starting point than Flexbox?
- How should you choose a responsive breakpoint?
- What does a container query measure?
- What does clamp do?
- What is the difference between srcset and object-fit?
- Why should the narrow-screen content order be designed early?
- A positioned ancestor, commonly the card with position:relative.
- flex-wrap.
- When rows and columns need coordinated alignment.
- At a width where the content or layout begins to fail.
- A defined ancestor query container, rather than the viewport.
- It bounds a preferred value between a minimum and maximum.
- srcset offers resource candidates; object-fit controls how an already chosen image fills its box.
- Source order and readability should work before wider visual arrangements are added.
- Why does automated accessibility testing need manual checks?
- Which CSS state is useful for a keyboard-specific focus indicator?
- What names a group of related form controls?
- Why should a placeholder not replace a label?
- What should happen if a web font fails to load?
- Why can opacity on a whole card be a problem?
- What should reduced-motion preferences change?
- What is one useful change for a print stylesheet?
- Tools cannot judge every task, reading order, wording, or interaction experience.
- :focus-visible.
- fieldset with legend.
- The placeholder can disappear and may not provide a persistent accessible name.
- A readable fallback font should render the content.
- It also fades the text, which can reduce readability.
- Remove or simplify nonessential animation while keeping state changes understandable.
- Remove navigation, expose useful link URLs, or prevent poor page breaks.
- Where can a theme override a shared custom property?
- Why use cascade layers in a large stylesheet?
- What does :has() let a selector express?
- What problem does subgrid solve for repeated cards?
- What does inline-start mean in a right-to-left writing direction?
- What makes a component selector fragile?
- Why keep a base declaration before an @supports enhancement?
- What must work before a progressive enhancement activates?
- On a theme wrapper or another appropriate ancestor in the cascade.
- They give explicit priority groups and reduce specificity conflicts.
- A match based on a descendant or related element's presence or state.
- It aligns nested rows or columns to tracks shared with the parent grid.
- The start of the inline direction, typically the right side for right-to-left horizontal text.
- Depending on deep page structure or unrelated ancestor classes.
- The base remains usable where the enhancement is not applied.
- The core content, order, and basic interaction.
- Which developer-tools views explain a too-wide card?
- Why test in more than one browser engine?
- Why include image width and height in HTML?
- Can metadata replace clear visible content?
- Does styling an iframe change whether its content is trusted?
- What should a component document besides its default appearance?
- What makes a code-review comment useful?
- What should you check after a successful push and deployment?
- Computed styles and the box model, followed by the relevant style rules.
- Defaults, feature behavior, and rendering can differ between engines.
- They reserve space and help prevent layout movement while loading.
- No; visible content and structure remain the main source of meaning.
- No; trust and capabilities need separate controls and review.
- Purpose, variants, interaction states, markup, and accessibility behavior.
- A specific issue, its effect, and a testable proposed fix.
- Public links, assets, forms, keyboard behavior, and responsive layout.
- Why is absolute positioning a weak method for reproducing an entire design?
- Which content states should be used to stress-test a card?
- Does a button's visual style decide whether it should be an a or button element?
- What should an accessibility finding record?
- What makes a performance comparison meaningful?
- How do you reduce risk during a CSS refactor?
- What pages and evidence should the capstone include?
- What should a case study say about limitations?
- It often breaks when content length, viewport size, or zoom changes.
- Long titles, missing images, extra text, translated-like wording, and narrow widths.
- No. Navigation uses a link; an action uses a button.
- Location, user impact, reproduction steps, fix, and retest result.
- Comparable conditions, a relevant metric, and a clear before-and-after change.
- Refactor in small steps and compare appearance and behavior after each step.
- Home, listing, article/detail, and contact pages; code, public URL, audits, measurements, and a case study.
- State known limits honestly and identify the next useful iteration.