Reservation FAQ Block for React

No. This block has no server: the button only answers with a polite note ("Request noted for 4 at 7:30 pm. We'll confirm by text.") and never says a table is booked. To make it real, replace the body of submit with a call to your booking system and show its answer in the same live line.

From SLOTS at the top of the file: each slot lists how many tables are free for a party of one or two, three or four, and five to eight. The live line, the disabled chips and the button all read the same numbers through one helper, so they never disagree. A slot with no table for the chosen party is disabled, struck through and read as "full" by a screen reader.

It's a Number Input from 1 to 8 with plus and minus buttons; you can also type, and anything out of range counts as the nearest allowed size. Changing it re-checks every slot at once, and clears a note that a request was sent. Larger groups are a question further down: they write to the team.

The widget is a form named "Reserve a table". The time chips are toggle buttons in a fieldset named "Time", and Tab moves between the party size, the chips and the button. The line under the chips is a polite live region, so each change and the final note are announced, and focus stays where you left it.

Yes. Closed answers stay in the markup as hidden="until-found", so search engines see them and the browser's find in page opens a match.

The header stacks above the widget, and the opening-hours line shows from lg up. The chips stay three to a row and the widget's padding tightens, so the first question starts within the first screen. Nothing scrolls sideways at 320 pixels.