In one paragraph
DL elements must only directly contain properly ordered DT and DD groups means the tested description list failed a structural check. Use valid term-description grouping, preserve the actual information relationship, and move unrelated headings or layout content outside it. The checker does not validate every group's completeness or meaning. A single accepted pair is not proof that the whole description list is well organised.
Why it matters
Description lists suit terms with descriptions or appropriate name-value associations. HTML permits groups with more than one term or description; a simplistic mandatory one-to-one model would reject legitimate content.
Their exposure differs across assistive technology. Do not promise the same count or navigation as a bullet list in every browser. The important task is to communicate the intended association and a useful reading order.
Component wrappers and CMS imports can introduce stray content, reversed groups, or terms without corresponding explanations. A visually tidy two-column grid does not prove valid semantics, and a valid set of tags does not prove the terms and descriptions are paired correctly.
How WebAuditOS evaluates this finding
The supplied definition-list rule inspects applicable visible dl elements without a role override. It checks documented allowed-child and limited ordering conditions, with supported div grouping and script-supporting or hidden-content exceptions.
Serious impact maps to high severity. The source explicitly describes looser order checks than the rule label implies: grouped entries or later invalid ordering can escape a pass once its particular conditions are met. Separate orphaned dt/dd checks cover parent relationships. Treat the result as partial structural evidence.
How to fix it
- Identify each actual term group and its descriptions. Keep adjacent explanatory prose and section headings distinct from the list unless they belong meaningfully inside an entry.
- Build an appropriate native structure. For example:
<dl>
<div><dt>Delivery method</dt><dd>Courier</dd></div>
<div><dt>Estimated transit</dt><dd>Two working days</dd></div>
</dl>The values are illustrative. Review the actual content and required grouping rather than copying the sample into an unrelated specification.
- Keep div wrappers in a valid content model. Avoid unnecessary additional structural levels inside a group and do not mix unrelated layout containers with native terms merely because a checker ignores some nodes.
- Move headings, notices, and independent paragraphs to appropriate surrounding positions. Do not delete necessary information simply to make the list's child set smaller.
- Verify every group manually, including multiple terms sharing a description or multiple descriptions attached to a term. A checker finding at least one valid sequence is not a complete semantic validation.
- Prefer a table when the information requires meaningful row and column comparisons rather than forcing all datasets into dl for styling convenience.
- Test generated empty, partial, loaded, and error states. A template may leave terms without descriptions while data loads or accidentally place an error banner directly inside the list.
- Rescan this rule and the dt/dd parent rule, then inspect reading order, visual pairing, and responsive layout. Keep useful semantics even when adding a role would remove the element from this specific selector.
What the fix can break
Changing wrappers can alter grid or flex selectors, margins, and scripts that walk children. Test both presentation and data binding after the repair.
An empty list passing the engine is not a reason to remove content or leave a failed request unexplained. Present actual status in a suitable accessible location.
Do not convert a comparison table to a description list if doing so loses meaningful headers. Structural simplicity should preserve the information model.
Questions
Are div wrappers always invalid inside dl?
No. HTML supports suitable grouping. Follow the complete content model and the tested implementation rather than prohibiting every wrapper.
Does a pass prove all terms have meaningful descriptions?
No. The documented ordering logic is limited; review each relationship manually.
Can a dl group contain multiple terms?
Yes, where the information supports that relationship. Do not impose a false universal one-to-one restriction.
Which related checks help?
Review dt/dd parents, ordinary list structure, and the automation limits guide.
What severity does this get in the report?
High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. axe declares this rule serious, so a failure arrives as high. The panel above shows a conformance level because for axe rules severity comes from the scan.