Keyboard-operable ARIA radiogroup with roving tabindex
One task across 30 published runs. Inspect the scores and outputs together, with each run's execution method shown.
- Task
- AYGAT-0006
- Domain
- UI components
- Difficulty
- hard
Leading published run: claude-opus-4-8 (max 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 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). Build a custom radio group following the WAI-ARIA radiogroup pattern (do NOT use native <input type="radio">). Requirements: - A role="radiogroup" containing exactly three role="radio" options with the ids radio-standard, radio-express, radio-overnight. Exactly one option is checked on load (aria-checked="true"); only the checked option has tabindex="0" and the others have tabindex="-1" (roving tabindex, so the whole group is a single Tab stop). - When a radio has focus, ArrowDown or ArrowRight moves selection to the next option and ArrowUp or ArrowLeft to the previous (wrapping at the ends). Moving selection updates aria-checked (the newly selected option becomes "true", the previous "false"), moves tabindex, and moves DOM focus to the newly selected option. The radio group must be fully operable with the keyboard alone. Use plain, accessible markup.