Navigation
the menu, the persistent call to action, and what the footer carries
Five items and a button.
The main menu
The Space Weddings Occasions ▾ Catering Rates [ Check availability ]- The Space is the room, the deck, the video tour and the floorplan. Everything factual links back to it.
- Weddings sits at the top level rather than inside a dropdown.
- Occasions holds Meetings & Events and Celebrations & Memorials. Named Occasions rather than Events, because a dropdown called Events containing "Meetings & Events" nests the word inside itself.
- Rates is a navigation item rather than a link on the inquiry page. See Rates & Availability.
Gallery is not in the navigation. It arrives in phase 3 and lives in the footer until it has real events in it.
Label the button "Check availability," not "Contact us."
One name per destination
The button says "Check availability," so the page is Check Availability and the URL is /availability.
"Check availability" is transactional, and the celebrations audience includes families arranging a memorial. Does the page heading soften while the button stays as it is, or does one label serve both?
The persistent action
The button sits in the header on every page, at every screen size, and stays visible when the page scrolls. On phones it becomes a bar fixed to the bottom of the screen with the phone number beside it.
Family celebrations and memorials are often booked by phone rather than by form.
Cross-links between pages
The three occasion pages each link to the same four places: capacity, rates, the video tour and the inquiry form. Every page ends with a single call to action rather than a list of options.
"Check availability for your date" at the end of the weddings page, going to the form with the event type already selected.
"Take a tour, download the floorplan, see rates, get in touch, follow us on Instagram": five links, none chosen.
The footer
| Group | Contents |
|---|---|
| Contact | Address, phone, email and a map link |
| The space | The main pages, repeated. Gallery joins in phase 3 |
| Practical | Directions and parking, accessibility, FAQ, privacy |
| Meals on Wheels People | What the rental funds, in one line, and a link to mowp.org |
| Social | Instagram first. It's where venue photography lives |
Every one of those Practical links needs a destination. Directions and parking point at the address section on Check Availability, FAQ at the same page's FAQ, privacy at its own page, and accessibility at a named section on The Space.
The address belongs in the footer as text on every page, not only on the inquiry page. Visitors copy it, and search engines read it as a location signal.
Accessibility
The navigation follows the same standards as the main website: keyboard operable, visible focus, a skip link and the dropdown usable without a mouse. The phone bar on mobile must not cover the page's last line of content.
The site also needs a venue accessibility section someone can link to: step-free route, elevator, restrooms and assistive listening if there is any.
Should any pages be available in languages other than English? The audience for family celebrations around 82nd Avenue is a specific case for it, and MOWP built the dining program with Karen, Somali, Burmese, Tongan and Chinese community leaders. A translation toolbar isn't the same answer as a translated page.