Terms Consent Login Block for React

Nothing. Continue waits under a spinner for less than a second, then shows which versions were accepted, the fixed day the demo uses and whether product updates were chosen, and a polite status message says nothing was recorded. Start over clears every box. For real, post the ticked agreements from the submit handler where the code says so: the user, each agreement's id and version, the time and where it was accepted, stored where you can show it later, and only then open the app. Keep the busy state until the server answers and show its error under the group if it refuses.

A disabled button can't say why, and keyboard users can't reach it to find out. Here it stays enabled: pressed with the Terms or the Privacy notice unticked, it marks those cells, writes one sentence under the group that names them and moves focus to the first, so a screen reader hears what to do. Ticking a box clears its mark as you go, and the line under the group always has its space, so nothing moves.

It reads the two required boxes: clear when neither is ticked, mixed when one is, ticked when both are, and pressing it ticks or clears both. Product updates stay outside it because one box should not buy consent to two different things, and an optional agreement should be a choice made on its own: it is never pre-ticked and never required. The mixed state is the indeterminate prop beside checked.

Because what a person accepted is a particular text. The version and its effective day are typed in AGREEMENTS, so when you publish version 8 you change two values and everyone who accepted version 7 is asked again. Keep the number you show in the same record you store, so you can prove which words were accepted.

Yes. Tab runs through select-all, each agreement's box, the Read links, Continue and the quiet link. A press on any part of a cell ticks its box, and Space does the same from the keyboard. Each box is named by its title and described by what it covers and its version, and a marked one is also described by the group's problem line. After Continue, focus moves to the result's heading and a polite status message says what was accepted, so the outcome is heard.

The band keeps its rails and the group fills the width of the screen, so every box has a large target. Continue ends on the first screen, the cells' text wraps, and the result replaces the group without the page changing height.