Why this wireframe works | Before-you-visit access
Pre-visit worries answered item by item
Reservations, parking, the entrance, wheelchair access: the things people wonder about before coming are listed item by item. Fewer surprises on the day, and fewer phone calls to check.
The gist readable without opening
Each heading carries the gist, such as “By appointment only” or “No on-site parking”, and only the full explanation opens. Skimming the headings is enough to learn what matters.
Location basics gathered at the top
The map, address and nearest station are summarized small above the checklist, so the basics and the checks fit on one screen.
Labels make items easy to find
Each item starts with a label such as “Reservations” or “Parking”, so the item that concerns you is easy to spot.
Common mistakes | Before-you-visit access
A heading like “About parking” that hides the answer
When the heading is only the question, every item must be opened to learn the answer. Put the gist in the heading.
Not saying what is unavailable
No parking, steps at the entrance: what is unavailable is exactly what people want to know before coming. Say it plainly, not in roundabout terms.
Too many items
Listing everything that comes to mind buries the important items. Keep to the ones most asked about and most likely to cause trouble on the day.
Contradicting the FAQ page
When the same thing is also on the FAQ, editing one and not the other creates conflicts. Make one the source and link to it from the other.
FAQ | Before-you-visit access
In what order should the items go?
By how much trouble they would cause on the day. If reservations are required, put reservations first; if many visitors drive, put parking near the top.
Is this pattern needed when there is an FAQ page?
The FAQ answers a wide range of questions; this pattern is for checking just before a visit. Gather only the visit-related items here and link to the FAQ for the full explanations, so the roles stay separate.
Can everything be shown without accordions?
With three or four items and short explanations, showing everything reads fine. With many items or long explanations, put the gist in the heading and let the rest open.















