Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use correct definition list structure. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 30% | 0% |
| case-05 | ✓→✓ | = Same ✓ | 18% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -12% | 0% |
| case-07 | ✓→✓ | = Same ✓ | 13% | 0% |
| case-08 | ✓→✓ | = Same ✓ | -8% | 0% |
Broken list structures confuse assistive technologies, preventing users from understanding the relationship between terms and their definitions.
Verify that all <dl> elements contain only valid child elements (dt, dd, or allowed wrappers).
Remove any invalid elements from within the <dl> or wrap them appropriately to maintain semantic integrity.
Explain how proper definition list structure helps screen readers navigate and group related information.
Review the rendered markup and interactive states that affect Use correct definition list structure. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/definition-list
Other measured skills in the registry, with their headline benchmark lift.