How to Fix Page Structure and Headings

Screen reader users pull up a list of a page's headings and jump straight to the section they want, the way a sighted reader scans down the page. Text that only looks like a heading never appears in that list. This is also the biggest subject in the library, more than a fifth of it, because 1.3.1 Info and Relationships reaches into tables, lists, forms and landmarks as well as headings. The techniques here cover marking up headings, lists and regions properly, and keeping reading order meaningful when CSS moves things around. They also cover giving every page a descriptive title, and the failures that come from formatting text instead of structuring it. One thing to settle before you start, because it saves an argument later. WCAG sets no number of h1 elements and does not require heading levels to run without a skip, so a tidy outline is good work here rather than a Level AA obligation.