Description List
A Description List pairs each name with a value or explanation. It suits short, read-only facts.
Another example
An order summary lists status, customer, delivery time, tax number, and payment method as read-only facts.
Main parts
- 01Trigger or task context
- 02Primary control surface
- 03Feedback, focus, and dismissal
Use it when
Use it for a short fact set where every value needs a clear name.
Do not use it when
Do not use it for editable forms, sortable tables, or normal articles.
Name used in code
<dl><dt><dd> Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Description List to solve this user need without losing the current context. User context: An order summary lists status, customer, delivery time, tax number, and payment method as read-only facts. Recommended pattern: Description List. Why it fits: Use it for a short fact set where every value needs a clear name. Do not use it when: Do not use it for editable forms, sortable tables, or normal articles. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Description List. Definition: A Description List pairs each name with a value or explanation. It suits short, read-only facts. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.