Test results
Pick a model to see how accessible its components are, with the accessibility skill off and on.
Gemini 4 Argon
Skill version 2.3
| Measure | Skill off | Skill on |
|---|---|---|
| Failed acceptance criteria | 22 | 0 |
| of which WCAG | 15 | 0 |
| of which Best practice | 7 | 0 |
| Total cost (US dollars) | $4.84 | $10.85 |
Icon button
Results, totals across all generations
Failed acceptance criteria
Each acceptance criterion is counted once per component if it fails in any generation.
- Skill off
- 0 fails
- WCAG
- 0 fails
- Best practice
- 0 fails
- Skill on
- 0 fails
- WCAG
- 0 fails
- Best practice
- 0 fails
Efficiency, average per generation
Input tokens include cache reads.
Cost in USD
Input tokens
- Skill off
- 5,498 tokens
- Skill on
- 103,470 tokens
Output tokens
- Skill off
- 4,138 tokens
- Skill on
- 7,080 tokens
Turns
- Skill off
- 3 turns
- Skill on
- 8 turns
Time
- Skill off
- 47 seconds
- Skill on
- 127 seconds
Cost
- Skill off
- $0.05
- Skill on
- $0.14
Generated components
Prompt given to the model
Build an icon button in a single self-contained HTML file (inline CSS and JS, no build step, no external libraries). The button shows only an icon (for example a magnifying-glass search icon) with no visible text label. Include one enabled icon button and one disabled icon button. Output the complete code in one HTML code block.
Acceptance criteria
Show
Showing 9 of 9 criteria
Labels and messaging1 criterion
- The icon button has a programmatic accessible name (aria-label, aria-labelledby, or title) and no visible text label.WCAG 4.1.2AutomatedSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Semantic markup3 criteria
- The button's role is included in the accessibility tree.WCAG 4.1.2AutomatedSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
- The icon button's accessible name is included in the accessibility tree.WCAG 4.1.2AutomatedSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
- If the button is disabled, the button's disabled state is included in the accessibility tree.WCAG 4.1.2AutomatedSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Keyboard4 criteria
- The button is focusable using a keyboard.WCAG 2.1.1BrowserSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
- The button is activated by pressing the Space or Enter keys on the keyboard.Best practiceBrowserSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
- The button has a focus style when it receives focus using a keyboard.WCAG 2.4.7BrowserSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
- The keyboard focus style still renders in forced-colours mode (e.g. Windows High Contrast Mode).Best practiceBrowserSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Visual design1 criterion
- If the button uses a custom focus style, the focus indicator has a contrast ratio of at least 3:1 against its background colour.WCAG 1.4.11BrowserSkill off
3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass