Headings, Lists and Landmarks: The Structure Screen Reader Users Navigate By

Sighted readers skim a page. They catch a bold line, a bullet, a block of white space, and they know where they are. A screen reader user needs the same map, but it only exists if the file contains it.

Looks like a heading is not a heading

The most common structural fault is simple. A line is bold, larger and centred, so it looks like a heading. In the file it is an ordinary paragraph. Assistive technology cannot tell it from body text, so it never appears in the heading list that screen reader users jump through to find a chapter or a section.

The fix is to use real heading elements, in order. A chapter title is a level one, a section is level two, and a subsection is level three. Do not skip from two to four because the font looked better. Style belongs in the stylesheet, and rank belongs in the markup. WCAG 2.x covers this under success criterion 1.3.1, Info and Relationships.

Lists that are only typed

A column of lines starting with a bullet character, or numbered by hand, reads as a run of unrelated paragraphs. A real list element tells the reader "list, five items" before reading the first one, and lets them skip it. Reference lists, steps in a method, learning objectives and glossary entries all benefit. Hand-numbered lists have a second problem: reflow breaks them, and the numbers detach from the text.

Landmarks and navigation in an EPUB

EPUB adds its own layer. A working table of contents is a navigation document, and every entry must lead somewhere. Front matter, chapters, appendices and the index can carry DPUB-ARIA roles such as doc-chapter and doc-index, so a reader can jump straight to them. If the book has print page numbers, a page list that maps to the print edition matters for students whose class uses the printed version. Without it, "turn to page 112" has no answer.

Reading order

The order in the file must match the order a reader would follow. Sidebars, pull quotes and boxed features often fail here. They sit in the visual margin but come out in the middle of a sentence, or at the end of the chapter, depending on how the file was built. WCAG 1.3.2, Meaningful Sequence, covers it. The same rule applies to tagged PDFs, where the tag tree sets the order and a visually perfect page can still read badly.

A three-step check

First, open the book with a screen reader and pull up the list of headings. Does it read like a clean outline of the book? Second, skip through the lists. Are the real ones announced as lists? Third, read one chapter with a sidebar and listen for where it lands.

An automated checker will flag a missing heading. It will not tell you that the heading levels make no sense, or that a sidebar interrupts a paragraph. Those take a person listening.

Where S4Carlisle fits

Structure is cheapest to get right at tagging and conversion, before the files are final. S4Carlisle builds semantic headings, lists, landmarks and page lists into EPUB and PDF production, then tests the result by ear as well as by tool, so the outline holds up under a screen reader and not only under a validator. To talk about your next title, write to sales@s4carlisle.com.