Behavioral tasks
- Primary action works with a pointer on desktop0/5 passedactivation produced no observable response
- Primary action works from the keyboard0/5 passedactivation produced no observable response
Promotion guardrails
- PassAccessibilityNo blocking issues
- PassRuntime correctnessNo blocking issues
- PassArtifact boundaryNo blocking issues
SUS diagnostic feedback
**Usability**: This is a genuinely well-executed single-purpose landing page. The primary 'Book a Walk' CTA is immediately visible, high-contrast, and clearly labelled; information density is appropriate and nothing competes for attention. Semantic HTML, skip-link, and zero axe violations reflect deliberate accessibility work. The only meaningful friction is that the booking dialog is hidden until triggered, so price and date availability aren't visible at a glance before the user commits to opening it. **Visual design**: This is a genuinely polished, well-considered landing page that executes its narrow brief with confidence. The typographic hierarchy is clear—pill tag, large H1, supporting body copy, bold CTA—and the forest-green accent is used consistently and sparingly against a clean white ground. The only noticeable composition wobble is the four-item detail strip wrapping into a 3+1 layout, which breaks visual rhythm; a 2×2 grid would read better. Axe-core reports zero violations, and semantic structure is solid throughout. **Content & clarity**: This is a well-executed, single-purpose landing page that communicates its value proposition clearly within seconds: guided walking tours, every weekend, £18/person. The headline, subhead, and CTA form a tight, coherent hierarchy with no extraneous noise. Copy is concise and benefit-led. The details strip (duration, group size, price, location) answers the key visitor questions immediately. Accessibility implementation appears solid with skip links, ARIA roles, and semantic HTML throughout.
Suggestions
- Make the page's primary call to action obvious, enabled, and behaviorally functional: activating it must navigate, scroll, open a dialog/window, or change visible content without runtime errors.
- Surface the next available date(s) directly in the hero or details strip so users know walks are actually bookable before hitting the CTA.
- Make the £18 price more prominent — currently it sits in a lower detail card that some users may miss before clicking Book.
- Add a visible schedule or calendar preview (even just 'Next walk: Saturday 12 Sep') to reduce uncertainty and increase booking confidence.
- Ensure the booking dialog traps focus correctly and that the close button is the first focusable element in the dialog for keyboard users — this cannot be confirmed from the static screenshot alone.
- The Highlights and About nav links appear to be in-page anchors; label them clearly (e.g., 'Highlights ↓') or ensure smooth-scroll and visible section IDs exist so users who click them get clear feedback.
- Consider a short testimonial or trust signal (e.g., '4.9 ★ from 200+ walkers') near the CTA to reduce hesitation for first-time visitors.
- Rework the details strip to a 2×2 grid so all four items share equal visual weight and the odd-one-out wrap is eliminated.
- Increase the body copy contrast slightly — #444 on white passes AA but teeters; nudging to #333 improves readability and passes AAA with no design cost.
- Add a subtle hover/focus state to the tag pill or make it visually distinct from an interactive element to avoid affordance confusion.
- The logo icon silhouette reads as a generic person glyph — consider a more distinctive mark (e.g., a walking figure mid-stride) to reinforce the brand concept.