No.350 · FAQ
Footnote FAQ
An FAQ written as two honest paragraphs: the phrases a reader would want to check carry footnote numbers, and opening one sets its answer as a note right under the line.
The prompt
Written for the variant you picked above: Paper
Replace a stack of FAQ accordions with prose. Write what the product does in a couple of paragraphs set in a serif at reading size; the claims a reader would want to check ('its own preview address', 'per seat, monthly or yearly', 'you can leave whenever you like') are inline role=button spans (so they can wrap across lines, which <button> can't) with a dotted accent underline and a small mono superscript number, numbered in reading order. Pressing one inserts its note under that paragraph: a panel with a 2px accent rule on its left, the number, the question in bold and the answer, opening with a grid-template-rows reveal (520ms expo-out) while the answer fades and drops into place. Several notes can be open at once; the phrase stays washed in the accent while its note is open, and each note has a close button that returns focus to its phrase. Below the prose, an 'All questions' index lists every question with its number, for people who scan; choosing one opens the note and moves focus to its phrase. Each note has a deep link (#faq-3) that opens it on load. Phrases are role=button spans (Enter and Space work) with aria-expanded and aria-controls, and their accessible name includes the question; closed notes are inert. Selected variant — Paper (paper): Palette for this theme (Paper): --fn-body #3b3832; --fn-ink #1d1b17; --fn-line rgb(29 27 23 / 0.12); --fn-mark #2f5fd0; --fn-muted #77716a; --fn-note #f6f3ec; --fn-wash rgb(47 95 208 / 0.08). Treat these as the root colour tokens, one value per role, and name them to suit your code. Select it with the theme option set to "paper". Keep every dimension, spacing value, state and motion from the brief unchanged, and keep text at 4.5:1 contrast or better on these surfaces. This selection takes precedence over references to other themes or options in the general brief. Implement this selected appearance; do not add a variant picker or alternative appearances unless requested. Implementation requirements: Use React and TypeScript. Keep the component self-contained, with uniquely scoped CSS and no animation libraries. Include required imports, styles and font setup in the result. Interaction: Press an underlined phrase (or a question in the index) to open its note under the paragraph; press it again or the × to close. Motion: Notes open with a grid-rows reveal (520ms) and the answer fades in 120ms later; underline and wash fade 200ms. Accessibility: Phrases are role=button spans (Enter and Space work) with aria-expanded/aria-controls whose names include the question, so a screen reader hears 'per seat, monthly or yearly, note 4: What counts as a seat?'. Notes are labelled regions and inert while closed. The index is a nav of real links with hash deep links. Reduced motion opens notes instantly. Responsive behavior: Prose reflows like any paragraph; notes take the full measure. Works from 320px up. Preserve keyboard access, visible focus and reduced-motion behavior. Keep fictional demo data and simulated service calls in a separate usage example; expose callbacks for real actions and recover from rejected requests. Keep usage-example links inside the demo: use local buttons or prevent navigation. Demonstration links must not navigate to Vitrine routes or open other pages; preserve real URL support in the reusable component itself. Verify the result at narrow and wide viewport sizes, with keyboard input and reduced motion enabled.
Notes
- Interaction
- Press an underlined phrase (or a question in the index) to open its note under the paragraph; press it again or the × to close.
- Motion
- Notes open with a grid-rows reveal (520ms) and the answer fades in 120ms later; underline and wash fade 200ms.
- Accessibility
- Phrases are role=button spans (Enter and Space work) with aria-expanded/aria-controls whose names include the question, so a screen reader hears 'per seat, monthly or yearly, note 4: What counts as a seat?'. Notes are labelled regions and inert while closed. The index is a nav of real links with hash deep links. Reduced motion opens notes instantly.
- Responsive
- Prose reflows like any paragraph; notes take the full measure. Works from 320px up.