Photo Access Repair Contact Block for React

No. They stay in the visitor's browser tab and the thumbnails are previews of the visitor's own files; nothing is sent. The block ships no photographs. To make it real, send files where submit waits, and check the type and size again on your server, because the drop zone's limits are only a courtesy.

It is not added, and a polite line under the slots says which file and why ("notes.pdf is not an image", "photo.png is over 8 MB", "would be a fourth photo"). A drop that mixes good and refused files keeps the good ones: the block listens to the drop zone's accept and reject events, not its change event, which would report an empty list after a mixed drop. Change MAX_PHOTOS, MAX_MB and ACCEPT at the top of the file.

It is a plain ordered list of four steps. Three lines change with the form: how many photos you added, the window you picked, and whether the engineer may enter when you are out and knows about pets. All the wordings share one grid cell, so a change never moves the page. The hours in it are example wording: write your own association's.

Yes. The drop zone opens the file chooser with Enter or Space, each remove button is a tab stop named after its file, and removing a photo returns focus to the drop zone. The switches and the three-way window toggle use arrow keys and Space as their libraries do, and the status line reads what was added, removed or refused.

Nowhere yet. The submit waits 800 milliseconds, as a stand-in for a request, then shows the confirmation, which echoes the flat, the window, the access choices and the photo names. Replace the timer in submit with your call: details, files, enter, pets and visit hold everything.

The cells stack with the form first, then the panel. The three photo slots stay in one row and truncate long file names, the switch rows keep their switch at the end, the window toggle fills the width, and the button goes full width.