Lumen/Guide: Course List Table Formatting (Headers)

How to properly utilize headers and sum totals in program curriculum.

Cascading headers in course lists

If using headers in tables, you must cascade for accessibility and proper ordering.

  1. first using Area Header
  2. second using Area Subheader

If you need more than two levels of headings, it's recommended to use headings on the page and use multiple course lists.

A screen shot of a sample table using Area Header, Area Subheader, and regular text to show the visual difference.

Area header

  • Area headers may only be set up on text (add comment entry).
  • Area headers can only be set up by checking the "Area Header" box.
  • An area header displays as bold text in both the edit course list feature and in the public facing table.
  • This reads "areaheader" when using a screen reader.

A screen shot of the edit course list table with the "Area Header" check box highlighted by a red box.

Area subheader

  • Area subheaders may only be set up on text (add comment entry).
  • Area headers can only be set up by checking the "Area Subheader" box.
  • An area subheader displays as italics in the public facing table. The only visual indicator of a subheader is the check box; the font/styling doesn't change in this space.
  • This reads "areasubheader" when using a screen reader.
  • It is not a requirement to use an area subheader if you use an area header.
  • If using area subheader, there should be more than one subheader used.

A screen shot of the edit course list table with the "Area Subheader" check box highlighted by a red box.

When to use headers

An area header should be utilized when distinguishing between sections of a curriculum. This could be:

  1. distinguishing the core courses from electives,
  2. parsing types of requirements (mathematics, statistics, chemistry),
  3. any other feature that distinguishes one segment/section of courses from another in a single program.

An area subheader should be utilized when identifying subgroups under an area header.

Headers let end-users know what part of the curriculum they're interacting with and the prominence of pieces of the courses related to the program. They are imperative for all users, particularly for individuals using screen readers, to comprehend the organization of the curriculum.

It is not required to use any headers within the course list table if headers are used outside of the course list, parsing the curriculum by section.

Proper use of headers

  • Only use headers for heading purposes (not for visual aesthetics)
  • Headers must not duplicate the tab name (ex. Requirements)
  • Headers cannot be used to mimic course list functionality (sum hours)
  • Area headers must not be the same text as a header on the requirements tab outside of the table (i.e. Required Courses on the page, Required Courses in the course list)
  • If using multiple area headers, they should be high-level sections that are equitable in the display.

Best practices

  1. If using headings in a table, the first item in the list must be an area header.
  2. Headers should reflect a topical area of study, semester/timing (if articulating curriculum in the order courses must be taken), or other distinguishable segment.
  3. Credits should be associated with text, not a header. Typically, this directly follows the header.

Examples of best practices

Examples of improper header use with how to fix

The following examples are modified course lists to display actual table set-ups without any specific identifying information (i.e. these are not real programs).



Keywords:
curriculum, courses, programs, integration point, headers, headers in tables, course list, requirement, requirements, requirement header
Doc ID:
138758
Owned by:
Melissa S. in Lumen and Guide
Created:
2024-07-26
Updated:
2024-08-20
Sites:
Lumen and Guide