Guidelines for heading semantics in the Admin Guidelines for heading semantics in the Admin
- Guideline 2.4: Provide ways to help users navigate, find content, and determine where they are.
- Guideline 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA).
The objective is to make section headings within web content descriptive. Descriptive headings and titles work together to give users an overview of the content and its organization. Descriptive headings identify sections of the content in relation both to the web page as a whole and to other sections of the same web page.
This means: One H1 per screen, describing what the screen is about, the main title.
The rest of the sections and content is identified by meaningful sequential headings.
- WCAG 2 Technique: Providing descriptive headings
- WCAG 2 Technique: Using h1-h6 to identify headings
- WCAG 2 Technique: Organizing a page using headings
- The Headings Hierarchy Challenge by Joe Dolson
- HTML5 Headings in WordPress: A11y versus SEO? by Rian Rietveld
Open tickets Open tickets
Open tickets addressing the heading semantics Admin are labeled #a11y-headings.
In WordPress 4.3 the main heading was changed from an H2 into an H1 for admin screens.
Changing all headings will be the accessibility focus for milestone 4.4.
- Make a list of admin screens we need to change.
- Create tickets (label them in the description with #a11y-headings).
- Create patches, as smal as possible.
- Investigate how plugins will be affected.