[wp-meta] [Making WordPress.org] #4117: Proposal to change the headings hierarchy in the Support section

Making WordPress.org noreply at wordpress.org
Tue Jan 29 14:19:17 UTC 2019

#4117: Proposal to change the headings hierarchy in the Support section
 Reporter:  afercia  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:  headings-hierarchy
 Splitting this out from #4110.

 The headings hierarchy in the Support section has room for improvements
 for better SEO and accessibility:


 As mentioned in #4112 the logo shouldn't be a `h1`. The main topic in this
 page is "WordPress Support" and that should be the only `h1` in the page.

 The headings hierarchy is incorrect: all the other heading should be
 bumped up from `h3` to `h2`.

 **Categories main pages:**
 they look OK with the exception the logo shouldn't be a `h1` see for
 example https://wordpress.org/support/category/basic-administration/

 **Article pages:**
 In the article pages, for example


 - the logo shouldn't be a `h1`
 - in the left sidebar, the "Categories" `h2` comes before the main topic
 `h1`, which is unexpected
 - the hierarchy of the headings in the content is correct but there's a
 problem: the "hash link" to get the in-page link repeats the visible text.
 This way, all the headings have duplicated content.

 In the example page, any software including search engines crawlers and
 assistive technologies perceive the following headings content:

 - Introduction Introduction
 - Plugin Repositories Plugin Repositories
 - Default Plugins Default Plugins
 - Plugin Development Plugin Development

 - the headings shouldn't contain extraneous content: the "hash link"
 should be moved out from the headings
 - ideally, it should have a meaningful link text, e.g.: "link to the
 section Introduction", "link to the section Plugin Repositories", etc.

 Please consider the Support section has a huge amount of sub-section,
 pages, and content. Going through all of them is out of the scope of this
 ticket. However, these are general guidelines that should be applied

Ticket URL: <https://meta.trac.wordpress.org/ticket/4117>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list