1. Heading — light section, GLOBAL color. The heading below uses "Use theme default" on a light section (variant 1). It should be dark and legible. This caption is a Rich text module on the same light section.
Light section heading (global color → dark)
2. Heading — DARK section, GLOBAL color (the bug scenario). The heading below uses "Use theme default" with section variant 4. It must render light/legible on this dark band. This caption is a Rich text module (also global) on the dark section — its body text and this link should also be legible.
Dark section heading (global color → light, legible)
3. Heading — CUSTOM color (#B30000) survives. The heading below sets Title color → Custom. The fix does not touch the custom branch, so the editor-chosen color still applies.
Custom color heading (dark red)
4. Rich text — GLOBAL, dark section. This paragraph's body color follows the dark section text color and should be legible. Here is a link and another link — both should use the dark-section link color and remain readable, with a visible hover state.
- List items inherit the same legible body color.
- Blockquote, code and table styling all track the section palette.
A blockquote on the dark band — text, background and accent come from the dark section's blockquote tokens.
5a. Buttons — light section. Two buttons using theme variants (primary + secondary). Colors come entirely from the theme button styles.
5b. Buttons — dark section. The same theme button variants on a dark band. They should remain legible and on-brand without any per-instance color fields.
6. Animation — heading slides up on scroll
Rich text — line by line. This paragraph reveals first.
This one follows with the theme stagger delay.
- List items reveal one after another.
- Using the shared reveal system — same as every standardized module.