API Error Codes FAQ Block for React

Edit CODES at the top of the file: each entry has the code, the question, the cause, the fix, the header as it appears on the wire and retry, whether sending the same request again can succeed. The "Retry rules" card reads retry, so a new code lands in the right list on its own. OPEN_CODE names the row that's open on load.

The question already says the code ("What does 429 mean?"), so a second "429" before it would be read twice. The chip is decoration for sighted readers: it lets you scan the column for a number. In the card the chips are a real list, because there they are the content.

As a badge at the foot of the answer, in words and an icon, never by colour alone: "Safe to retry" is an outline badge with a circular arrow and "Don't retry" a secondary badge with a barred circle. Both use the theme's foreground tones, so the block stays calm in any preset.

Yes. The Accordion takes hiddenUntilFound, so closed answers stay in the markup as hidden="until-found" and the browser's find in page opens the one that holds a match.

Each question is a button inside its own h3 under the section's h2. Tab moves from question to question, Enter or Space opens one, and the button says whether it's expanded. Each answer is a description list of cause, fix and header, so a screen reader announces the terms with their values.

Below the lg breakpoint the title and sentence stack above the rows, the rows run from rail to rail, and the retry-rules card follows the last one. The chip stays at the start of its question, a long question wraps beside it, and a long header line scrolls sideways inside its own box instead of the page.