design-gan Autoresearch dual-agent loop

Run #7 exhausted Scrub ▸

best iter 2
best task score 100
iterations 2
holdout pass

A simple, accessible landing page for a weekend walking tour. Use concise text, high-contrast dark text on white, semantic HTML, and one clearly labeled primary Book a walk button that opens an accessible booking dialog with a working close button. Keep the standalone page compact and fully offline.

Frozen browser tasks

domain landing-page · 5 trial(s)/task · promotion α=0.05 · product live-auth-smoke-20260907

artifact standalone-html · max 524288 bytes · network blocked

  • development · Primary action works with a pointer on desktop: Find the page's primary call to action, activate it, and observe a meaningful response such as navigation, scrolling, a dialog, a new window, or changed visible content.
  • development · Primary action works from the keyboard: Reach the primary call to action with keyboard focus, activate it with Enter, and observe a meaningful response without runtime errors.
  • holdout · Primary action remains usable on mobile: At a compact mobile viewport, find and activate the primary call to action and observe a meaningful response without runtime errors.
  • holdout · Primary action remains keyboard-usable on mobile: At a compact mobile viewport, focus and activate the primary call to action from the keyboard and observe a meaningful response.

Final untouched holdout: PASS · score 100

Cross-run challenge: established · incumbent 1 · product live-auth-smoke-20260907

#1 0
Iter 1
Task score0% Trials0/10 SUS diagnostic90 GuardrailsEligible DecisionPromoted

Behavioral tasks

  • Primary action works with a pointer on desktop0/5 passed
    activation produced no observable response
  • Primary action works from the keyboard0/5 passed
    activation produced no observable response

Promotion guardrails

  • PassAccessibilityNo blocking issues
  • PassRuntime correctnessNo blocking issues
  • PassArtifact boundaryNo blocking issues
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.
#2 100
Iter 2
Task score100% Trials10/10 SUS diagnostic92 GuardrailsEligible DecisionPromoted

Behavioral tasks

  • Primary action works with a pointer on desktop5/5 passed
  • Primary action works from the keyboard5/5 passed

Promotion guardrails

  • PassAccessibilityNo blocking issues
  • PassRuntime correctnessNo blocking issues
  • PassArtifact boundaryNo blocking issues
Suggestions
  • Add a secondary contact option (email or phone) for users who are reluctant to fill in an online form — this reduces abandonment for less digitally-confident visitors.
  • Show a mini calendar or list of upcoming walk dates before the modal opens, so users can verify availability without committing to the booking flow.
  • The 'About' section is only reachable via scroll or nav link; consider surfacing a guide photo or one trust-building sentence (e.g., guide credentials) directly in the hero to reduce hesitation.
  • The star rating ('4.9 · 200+ happy walkers') lacks a source link; linking to a review platform or testimonials section would increase credibility.
  • Ensure the booking modal implements a focus trap and returns focus to the trigger button on close — this is critical for keyboard and screen-reader users and cannot be confirmed from static inspection.
  • Consider adding a 'What to bring' or FAQ accordion below the details strip to preemptively answer common questions and reduce pre-booking support queries.
  • Replace the ↓ text arrows in the nav links with a proper SVG chevron icon to maintain consistent iconographic language throughout the page.
  • Remove or swap the map-emoji from the tag-pill for a matching SVG icon used elsewhere, resolving the emoji-vs-SVG inconsistency.
  • Add a subtle hover/focus indicator (e.g. background highlight) to the sticky header nav links to reinforce interactivity affordance at smaller font sizes.
  • The price badge and next-walk date sit in close proximity with similar visual weight; increase contrast between them by making the date text slightly larger or bolder so scanning order is unambiguous.