Estate Agent Viewing Request Profile Block for Ark UI

Edit LISTINGS at the top: each has a title, a place, a price, beds, baths, area, a type (house or condo), three words about the neighbourhood and the kind of drawing. In your app replace the drawing with the listing's photograph: it is one Scene component, so you swap it for an img with object-cover. DAYS and TIMES are the viewing slots.

No. The drawn grid sits over an unseen copy of all six listings, so choosing houses or flats never moves the end cell or the foot. If the chosen listing is filtered out, the first one that is shown takes its place.

Nothing leaves the page. It says Drafted in this demo, nothing sent, in the status line, and the sentence above the foot reads back the listing, the day and the time. To make it real, send the listing, the day and the time to your own API from the form's submit handler and show its answer in the same line.

From two typed numbers, the last twelve months and the twelve before. The change is worked out and rounded to a whole percent with a sign, never typed, so it cannot disagree with the volumes. The agent and the figures are invented.

The listings are a group of native radio buttons, so the arrow keys move between them and the chosen one is both ringed and announced. The selects have visible labels, the rooms are a description list, and the status line is a polite live region present from the start. The drawings are hidden from assistive technology because every fact in them is in the text.

The listings come first, two across, and the chosen listing's details and the request stack under them with a rule and plus marks between, then the foot pinned to the bottom of the screen. From the medium breakpoint the details sit in a cell at the end. Prices keep their order in a right-to-left layout.