[wp-trac] [WordPress Trac] #29808: Post/paging navigation template tags

[WordPress Trac]

#29808: Post/paging navigation template tags
-------------------------------------+-------------------------------------
 Reporter:  obenland                 |       Owner:  johnbillion
     Type:  enhancement              |      Status:  reopened
 Priority:  normal                   |   Milestone:  4.1
Component:  Themes                   |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  twenty-fifteen has-      |     Focuses:  accessibility,
  patch                              |  template
-------------------------------------+-------------------------------------

Comment (by GaryJ):

 Replying to [comment:36 joedolson]:
 > If you read [http://www.w3.org/TR/WCAG20-TECHS/H42.html], it
 specifically states that "the layout could be presented with the first
 heading in each column at the same logical level (such as an h1)";

 if you care to finish that sentence, it carries on to say "or as found in
 the example, where the '''logical level reflects its importance in
 relation to the main content'''". It also says for the same example:
 "'''The content''' in the first and third columns '''is less important,
 and marked with h2'''". So, even putting any accessibility, document
 outline and SEO weightings aside, are you saying that the "Post
 Navigation" or similarly named sections are as important as the post
 content to which they are paginating through?

 > If the blog title is not a heading, then the posts navigation is, in my
 opinion, a top-level structural piece of the page; along with the main
 content area and any other navigation or sidebars.

 I think our opinions are going to forever differ here then. The three-
 column example you referred to in WCAG 2 also differs with your opinion -
 the main column is `h1`, and the columns that contain Site Navigation and
 Related Links headings are each `h2`.
 [http://webaim.org/techniques/semanticstructure/ WebAIM] also disagrees
 with your opinion.

 > An "ideal" heading hierarchy is also subjective, and many different
 opinions can influence it.

 I'm not trying to get "ideal" here. I'm trying to get the solution that I
 believe is the best combination of accessible, SEO beneficial, reflecting
 of importance related to other content on the page, and one that a greater
 proportion of developers will be happy to use as is, without wanting to
 filter it. I believe `h2` is the best element for that.
 >
 > To me, the important things here are only that 1) there is a heading and
 2) that heading can be changed to suit the needs and requirements of the
 site using it.

 On that we're agreed - I'd rather there were fewer people who felt the
 need to use that filter, than not, and that means catering for all
 reasonings of wanting a certain element, not just one.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29808#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform