Test results
Pick a model to see how accessible its components are, with the accessibility skill off and on.
Grok 4.7
Skill version 2.3
| Measure | Skill off | Skill on |
|---|---|---|
| Failed acceptance criteria | 42 | 6 |
| of which WCAG | 29 | 5 |
| of which Best practice | 13 | 1 |
| Total cost (US dollars) | $7.93 | $51.79 |
Checkbox group
Results, totals across all generations
Failed acceptance criteria
Each acceptance criterion is counted once per component if it fails in any generation.
- Skill off
- 1 fail
- WCAG
- 1 fail
- 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
- 19,858 tokens
- Skill on
- 516,158 tokens
Output tokens
- Skill off
- 14,784 tokens
- Skill on
- 41,658 tokens
Turns
- Skill off
- 3 turns
- Skill on
- 13 turns
Time
- Skill off
- 168 seconds
- Skill on
- 582 seconds
Cost
- Skill off
- $0.12
- Skill on
- $0.75
Generated components
Prompt given to the model
Acceptance criteria
Showing 16 of 16 criteria
Labels and messaging2 criteria
- The checkbox has a visible label.WCAG 3.3.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 checkbox group has a visible label.WCAG 3.3.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 markup7 criteria
- The checkbox'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
- Each checkbox has an accessible name 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 checkboxes are grouped programmatically, and the group role is included in the accessibility tree.WCAG 1.3.1AutomatedSkill 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 checkbox group has an accessible name 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 checkbox's checked and not-checked 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
- The group's required state is included in the accessibility tree.WCAG 1.3.1AutomatedSkill off
3/3 failed
- Generation 1: Fail
- Generation 2: Fail
- Generation 3: Fail
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
- The error message is programmatically associated with the group and is included in the accessibility tree.WCAG 1.3.1AutomatedSkill 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 checkboxes are 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
- Each checkbox can be checked and unchecked 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 checkbox 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 design3 criteria
- The error state does not use colour as the only method to indicate an error.WCAG 1.4.1AutomatedSkill 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
- All text meets the minimum contrast ratio of 4.5:1 against the background colour, or 3:1 for large-scale text.WCAG 1.4.3AutomatedSkill 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 checkbox 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
1/3 passed
- Generation 1: Not applicable
- Generation 2: Pass
- Generation 3: Not applicable
Skill on3/3 passed
- Generation 1: Pass
- Generation 2: Pass
- Generation 3: Pass
Notes on this run
Skill off
- Generation 1, 2, and 3 also have
aria-required="true"applied to the<fieldset>.aria-required="true"is invalid on thegrouprole and screen readers handle it inconsistently. - Generation 1, 2 and 3 have
aria-invalidapplied to the<fieldset>.aria-invalidis invalid on thegrouprole and screen readers handle it inconsistently.
Skill on
- Generation 1, 2 and 3 have
aria-required="true"applied to the<fieldset>.aria-required="true"is invalid on thegrouprole and screen readers handle it inconsistently. - Generation 1 and 3 have
aria-invalidapplied to the<fieldset>.aria-invalidis invalid on thegrouprole and screen readers handle it inconsistently.
Feedback on this result
Spotted a result that looks wrong, or a problem our tests don’t catch? Let us know. We’ll check it, correct any errors and use your feedback to improve the tests.
