Structure

Properly structured documents are essential to allow users who cannot see the layout to navigate documents. Assistive technology relies on the underlying structure to differentiate between (and indicate to users) content types which allows users to jump to specific places in the document, browse or skim information, and understand an overview before delving deeper. Consistently structured documents help all readers with context, organization of ideas, and clarity.

On this page:

• Headings
• Navigation
• Lists
• Tables

Headings

Headings are an important part of documents and web pages. Headings create organizational flow, build connections between key concepts, and break up large blocks of text to increase readability. Headings allow all learners to understand the logical structure of the page and navigate to different sections. Assistive technology can convey this structure to screen readers and speech-to-text software if the headings are properly formatted, not simply larger and bold text.

Use built-in tools to create headings in nested, sequential order. Accessible headings are both visual and semantic (i.e., they provide code for interpreting content). Simply making text larger and bold does not give headings essential meaning in code. Accessible headings have both style and meaning.

In addition to formatting headings correctly in code, headings must clearly describe the topic or purpose of their section in the content. Consider clickbait headlines, which are generally misleading and deceptive, but are designed to entice the reader to follow a link. Users dislike this practice because it is frustrating to expect specific information when following a link and not be able to find relevant information. Make sure headings accurately describe the information they present.

Headings:

Navigation

• Ensure documents have a title.
• Add a table of contents to documents longer than 5 pages.
• Provide skip links and multiple ways to navigate (previous and next buttons, menus, breadcrumb navigation, site map, etc.) in HTML.

Lists

Use the list tools to create lists. Creating lists using asterisks or dashes will not inform assistive technology that the content is part of a list. Lists are useful for steps in a process or grouping items. It is important that lists are coded so that assistive technology can make users aware of the presence of a list.

Correctly formatted lists organize information and make your documents accessible.

• Bullet lists are coded as unordered lists.
• They are appropriate for lists where the sequence is not important.
• Use bullet lists to group items or show hierarchy.

1. Numbered lists are coded as ordered lists.
2. They are appropriate for lists where the sequence is important, such as steps in a process.
3. Use numbered lists to give step-by-step instructions or for outlining a sequence.

Tables

Table Best Practices

• Tables must have a header row and/or column.
• A concise, descriptive table title or caption helps with context and organization.
• Do not use nested, merged, split, or unnecessary blank cells.
• Use cell borders to keep data visually distinct. There are exceptions in which cell borders can be removed.
• Ensure cells have adequate padding and margins.
• Do not use color alone to indicate meaning.
• Verify table reading order by placing the text cursor in cell A1 and pressing the Tab key to move from cell to cell. Ensure reading order matches the visual order.
• The Accessibility Checkers in Brightspace and Canvas offer significant checks and resolutions to improve table accessibility. The Office (Word and PowerPoint) checker does not offer as robust checks, only flagging a missing header row.

Later chapters will expand on using built-in tools to create headings, lists, and tables in different software suites and document types.