Accessibility Checkpoint WCAG 1 3.5
Headings must be nested correctly. For example, H2 must appear after H1, H3 after H2 etc.
Renumber headings so that the top level heading is H1, sub-headings are H2 and so on. Use CSS style rules to change heading font styles if needed.
- 5.5 May 2014 Don’t trigger for non-W3C technologies.
- 4.7 Jun 2012 Don’t trigger for WCAG2 (which doesn’t require strict nesting of headings).
- 3.5 Dec 2009 Don’t require an H1 to come before H2 (there are examples of H2 before H1 in WCAG 2 success techniques, and this is done on WAI site).
- 3.0 Dec 2008 Now triggers WCAG2 issue.
- 1.0 Feb 2007 Added.
This page describes a web site issue detected by SortSite Desktop and OnDemand Suite.
Rule ID: AccWcag1-3.5.1