Data Practices Table FAQ Block for React

Edit PRACTICES at the top of the file: each row has an id and the three columns, collect, why and kept. Keep each cell to a short phrase, and state retention as a period, not a date, so the table never goes stale. QUESTIONS holds the rows on the left. Have the table checked against what your service really does before you publish it.

It's our Table, in a framed card whose scroll container is a named region: below about 28 rem of width the table scrolls sideways inside it, and you can focus it and scroll with the arrow keys. The first column names each row and the cells wrap, so nothing is cut off.

Yes. The Accordion takes hiddenUntilFound, so every closed answer stays in the markup as hidden="until-found", and the browser's find in page opens the answer that holds a match. The table is plain content and is always in the markup.

The table is read by row and column headers, and each question is a button inside its own h3 under the section's h2. Tab moves through the questions, then into the table and on to the link. Tab moves from question to question.

It's a link (href="#"): point it at the page that starts an export, behind sign-in. It's an outline Button, because this block has no primary action. It renders the link it's given with render, with nativeButton={false}.