Landing page with a working mobile nav toggle
One task across 30 published runs. Inspect the scores and outputs together, with each run's execution method shown.
- Task
- WEB-0001
- Domain
- Websites
- Difficulty
- medium
Leading published run: claude-opus-4-8 (high reasoning) at 100.0% composite. Lowest: claude-haiku-4-5 at 0.0%. 30 published runs shown on this task.
How this task was evaluated
Results are ordered by this task's published score. API runs use one prompt and one completion; agent runs use a coding harness with tools and iteration. Inspect the execution method when comparing results.
Objective scores use the benchmark's execution checks. Judge scores use a vision panel's fixed rubric; the published score leaves out a model's own family. Missing values are labelled rather than treated as zero.
Read the brief
Build a single self-contained landing page as one HTML file (`index.html`) that renders with no build step and no network calls (inline all CSS and JS, no external fonts or scripts). Requirements: - three sections: a hero with a single main heading, a features grid with at least three feature items, and a footer, - a navigation menu that is collapsed by default and a hamburger toggle button (give the button id="nav-toggle" and the nav id="site-nav"), and - clicking the hamburger must open the menu (make it visible), and clicking it again must close the menu (hide it). Keep the button's accessible state in sync (aria-expanded) and update its label. Use plain, readable, accessible markup.
