FAQ list

• faq-ledger groups its questions under repeated topic labels that hang in the margin, and divides the band with rules of two different lengths. It is the one to take when the questions fall into groups.
• faq-measure refuses the split: one column at the full 1240, questions at display size, answers stepped in. It is the one to take when the FAQ is the whole page.
• faq-list is the one to take when the FAQ sits on a sales page and the point of it is the sentence at the top and the button under it.

• core/details is core, and it is safe at the 6.6 floor. The block landed in WordPress 6.3, and its block.json and its save() output are byte for byte identical in 6.5.5 and 6.7.1, which brackets the 6.6.7 matrix entry. The name attribute that powers exclusive accordions arrived later and is not used here, so nothing in this payload depends on anything above the floor.
• The question line box is a 45px band, on purpose. <summary> is not a block, so no block attribute can put padding on it; the only property that reaches it is what the <details> passes down by inheritance. Its height is therefore its line box and nothing else, and at 17px an ordinary 1.2 line height gives a 20px row, which is half of a usable touch target. line-height: max(45px, 1.15em) makes every single-line question a 45px band at every size, which clears the 44px target and gives the ruled list its even rhythm. It applies PER LINE, so a question that wraps on a phone opens a 45px gap inside itself and every automated gate passes it: the questions here are all under 26 characters, and the fix for a long one is shorter copy, never a looser line box.
• The answer measure is bounded by the content, not the viewport. The answer's padding-right: max(0rem, 100% - 32rem) resolves its percentage against the row's own width, so the answer is exactly 32rem wide wherever the row is wider than that and exactly full width wherever it is not. A first draft used a vw expression instead and read at 95 to 101 characters per line in themes whose content width was not the one it had been tuned against: a measure has to be derived from the thing it is measuring.
• The answer is set a step under the question, at 15 to 16px against the question's 17 to 19px, with the question at weight 600. With both at the same size and weight an opened row loses its hierarchy, which at this scale is the only hierarchy the row has.
• The closing action is a button, not a link in a sentence. The 45px trick above does not transfer: an inline <a> takes its height from the font's em box, so line-height opens space around it without making the box itself tappable. Anything clickable that is not a <summary> is a core/buttons block with its own padding.
• The header column stacks first on a phone. Core stacks columns below 782px, so at 390 the headline, the lead line and the button arrive above the questions, which is the reading order this pattern wants anyway. If you would rather the action closed the section, move the buttons block to the end of the list column.
• The first row ships open (showContent: true). A section whose every row is shut shows a visitor nothing about what is inside it, and it shows you nothing in a preview either.
• The disclosure marker is the browser's, not ours. It cannot be restyled from block attributes, and CSS a block attribute cannot express lives in the companion plugin rather than in a payload, so the triangle stays. It is also the only affordance telling a visitor the row can be opened, which is a good reason not to want it gone. The variation that has no triangle is not this design with the marker removed; see Open index below.
• Typography cascades down the row. Size, weight, tracking and line height are set once on the <details> and the question inherits them; the answer paragraph then resets all four to its own values. Change the question scale in one place per row, not two.

Each is a complete file you copy instead of the base, and each changes one idea.

• Night list. The colour axis, using the only move the contract can promise everywhere: the section inverts to your contrast with your base on it, the hairlines follow the type because they are currentColor, and the button inverts back so it stays the loudest element rather than a hole in the band. Both slugs exist in every stock block theme, which a tint would not.
• Open index. No disclosure at all, and composed so that is obviously the point: numbered entries, the question in the left column and its answer in the right, everything visible at once. It is the right choice for a short list, for a page that has to read straight through, and for anything printed. It exists because the triangle cannot be removed from a core/details row, so the way to a list without markers is a different composition rather than a subtraction. It is also the one payload here that keeps its own header, a small tracked label across the top, because an index has no header column beside it.
• Paper and ember. The colour axis again, the other way: it declares "colour": "stated" and carries its own palette, ink #1d2733 on paper #f5f2ec with the headline in an ember #8c3b1b. Identical in every theme and matching none, which is right for a buyer who wants exactly this palette and wrong for one who wants their site's.

The six answers are real answers, not filler, and two of them make claims about the product rather than about this section. The plugin answer in particular is written to be true under the three axes: the default promise is no plugin at all, a section that needs the free companion plugin says so on its own page before you buy, and it stays legible with the plugin switched off. If you keep our copy rather than writing your own, keep it true of what you sell.

Every pair in the base and in Night list is your contrast on your base, or the reverse, which is the pair your theme already ships body copy on; the button reverses it again. The headline is large display text and is claimed at 3:1. Everything else is body text at 4.5:1, the questions included: at 17 to 19px they are no longer large text by the WCAG definition, which is a consequence of the rework worth stating rather than assuming. Paper and ember is measured on the values it actually paints: ink on paper 13.5:1, the ember headline on paper 6.8:1, and paper on ink for the button 13.5:1. The hairlines are structural marks in currentColor and carry no text.