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 Wrap definition items in a definition list. 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-11 | ✓→✗ | ▼ Worse | -20% | 0% |
| case-01 | ✓→✓ | = Same ✓ | 0% | 0% |
| case-02 | ✓→✓ | = Same ✓ | 18% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 25% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 36% | 0% |
Standalone <dt> or <dd> elements lose their semantic meaning and fail to provide the context needed for assistive technologies to link terms with definitions.
Locate any <dt> or <dd> elements that are not children of a <dl> element.
Wrap orphaned <dt> and <dd> elements in a parent <dl> container.
Explain why <dt> and <dd> must be contained within a <dl> for correct semantic association.
Review the rendered markup and interactive states that affect Wrap definition items in a definition list. 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/dlitem
Other measured skills in the registry, with their headline benchmark lift.