Review Notes component reference
Purpose: static editorial review pages. This is a filled documentation example, not a published organizational release.
Usage rule and working specimen
RN-01 is required content. RN-02 holds optional source context. Keep those roles distinct.
Read the review scope before commenting.
Reference notes
Compare the draft against the supplied source notes.
Implementation notes
Keep the required instruction outside the optional references.
RN-02 · component contract
- Use when
- The reader may need optional source context.
- Do not use when
- The hidden content is an instruction most readers need.
- Required structure
- Native details, descriptive summary, supplied reference body.
- Initial and changed states
- Both instances closed initially. Open and close independently; the other instance and required instruction stay unchanged.
<details class="reference"> <summary>Reference notes</summary> <p>Compare the draft against the supplied source notes.</p> </details>
Shared values actually used here
- --rn-ink
- #20394d · text
- --rn-gap
- 16px · spacing in the specimen
- --rn-focus
- #7c2d12 · focus outline,3px solid with3px offset
Expected checks and observation scope
Inspect initial state, both independent open/close paths, retained text, visible required instruction, focus indication and narrow-width reading.
Actual browser results live in the execution receipts. Keyboard activation, assistive technology, other browsers and print remain observation pending; no accessibility certification claimed.
Change note and maintained source
Version0.1 is this authored teaching specimen. Actual owner, repository release and approval reference: not supplied.
Changed rule/value · reason · affected consumers · checks and actual resultsActual release reference
A changed reference page does not update earlier copied consumers. Keep prior specifications and identify the pages to check.