Module 5: Applied Design & Code Review: Reading Guide
Use resources selectively. The guide teaches the path; books and videos repair specific gaps.
How To Read For This Module
For Cluster 6, read the curriculum concept first, use the W3C WCAG 2.2 criterion only when preparing or checking a concrete test, and return immediately to observation. Accessibility guidance is not completed by reading: preserve keyboard, semantic, focus, error, contrast, reflow, and assistive-technology evidence. Use local design books for maintainable component contracts and official W3C material for normative accessibility requirements.
| Mode | Use when | Action |
|---|---|---|
| Close read | The concept is central and still unclear | Reconstruct the argument from memory after reading. |
| Skim | You need vocabulary or context | Capture only terms, diagrams, and examples. |
| Skip for now | The section is advanced or unrelated to current outputs | Add it to optional deep dive, not the main path. |
| Exercise read | You need practice volume | Read only enough to solve the next problem. |
| Reference lookup | You forgot a detail | Open the smallest relevant section, then return to the task. |
Stop-Reading Rules
Stop reading and start producing evidence when you can:
- explain the concept without the page open
- solve one small variant
- name one failure mode
- connect the idea to the module project or portfolio artifact
Active Reading Notes
For every substantial source, write four lines:
- Main claim:
- Example worth preserving:
- What I can now do:
- What I still cannot do:
Resource Triage
If two resources explain the same idea, keep the one that gives better examples, exercises, or implementation detail. Do not collect redundant links for comfort.