• Media Type Web > Lists
  • State Active
  • Advisory No

The HTML list elements dl, ul, and ol should only be used to create lists, not for formatting effects such as indentation or presentation which does not communicate list items.

Compliant Example

<!-- example that uses the CSS margin property for indention -->
<style>
   p { margin-left: 1em;}
</style>
<p>
  Content to be indented.
</p>

<!-- a list with list items used for indention but the role of list and it's list
item children will not be exposed to the accessibility API because role of presentation is
set on the list element.  Role of presentation does not need to be set on the list items. 
This technique is not recommended as there should be no reason to use the list structure
and CSS should be used instead to indent content that is not part of a list.-->

<ol role="presentation">
  <li>Content to be indented.</li>
</ol>

Non-Compliant Example

An unordered list element used with no list items and just content inside to produce an
indented effect.
<ul>
  Content to be indented.
</ul>

Ensure that lists are not used for indentation purposes. List and list item elements should only be used to structure items that belong in a list. Developers should ensure that pages do not contain (l) elements without (li) elements within them. Additionally, developers should not have (dl) elements without (dt) and (dd) elements within them.

Organization Standards

  • Section 508 and 255 (Revised 2017)
    • Chapter 3: Functional Performance Criteria
      • 302.1 Without Vision
  • WCAG 2.0 Level A
    • 1.3.1 Information and relationships conveyed through presentation
  • WCAG 2.1 Level A
    • 1.3.1 Info and Relationships

Other Mapped Standards

  • § 508-1194.31 Functional performance criteria
    • (a) Ensure access for blind and visually impaired
  • 47 CFR 14. Advanced Communication Services
    • 47 CFR 14.21 Performance Objectives
      • (b) Accessible
        • (b)(2) All information necessary to operate and use the product
          • (b)(2)(i) Availability of visual information
  • BITV 2.0 (Priority I)
    • 1.3.1 Informationen und Beziehungen
  • EN 301 549 v3.2.1
    • Chapter 4: Functional Performance
      • 4.2 Functional Performance Statements (FPS)
        • 4.2.1 Usage without vision
    • Chapter 9: Web
      • 9.1 Perceivable
        • 9.1.3 Adaptable
          • 9.1.3.1 Info and relationships
  • JIS X 8341-3: 2004 - Technical Standards Subpart 5
    • 5.2 (a) Provide proper document structure
  • KWCAG
    • 3-2 - Ensure formats are understandable
      • 3-2-1 - Ensure to use proper HTML tag
  • Telecommunications Act Accessibility Guidelines
    • 1193.43 Output, display, and control functions.
      • (a) Availability of visual information. Provide visual information through at least one mode in auditory form.
  • WCAG 1.0 Priority 2
    • 03.6 Mark up lists and list items properly.
  • WCAG 2.2 Level A
    • 1.3.1 Info and Relationships

  • Severity

    4 (yellow)
    in range of 1 to 10

  • Noticeability

    6 ()
    in range of 1 to 10

  • Tractability

    4 ()
    in range of 1 to 10