For lists, what is required to ensure semantic output is accessible?

• A. All visually apparent lists are programmatically identified according to their type (<ol>, <ul>, and <dl>).
• B. Lists may be represented with any container element.
• C. Lists are unnecessary for accessible content.
• D. List semantics can be omitted if the page looks good.

Answer: (A)

Using proper list markup is essential so assistive technologies can understand the structure and navigate the content effectively. To ensure accessible output, every visually apparent list should be marked up with the correct HTML list element: ordered lists for items where sequence matters use

, unordered lists for bulleted items use
, and description lists for terms and definitions use

(with

and

). This native semantics lets screen readers announce the start and end of the list, indicate how many items there are, and convey the relationship between terms and their descriptions, improving keyboard navigation and comprehension for users relying on assistive tech. If you replace these with a generic container like a div or span, the semantic information is lost, and accessibility suffers—even if it looks right visually. While ARIA can add some semantics, it’s not a substitute for using the correct native elements.