[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 joedolson):

 I don't see anywhere in WCAG 2.0 that specifies that the H1 can't cater to
 the best accessibility case. 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)"; the important thing is whether
 items of an equivalent structural level are presented with equivalent
 logical levels.

 Now, I would say that the way many themes have historically handled this
 is wrong, using an H1 for the page title, and when the blog title is an
 H1, I would say that this function should return an H2, because the
 navigation structure should be at a level below the main blog title.
 However, I also believe that the main blog title should not be a heading.
 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 that we can debate around the question forever -- the fact is that
 the "ideal" heading hierarchy is not something that can be accomplished in
 a theme, because content and plug-ins will change it anyway. An "ideal"
 heading hierarchy is also subjective, and many different opinions can
 influence it.

 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.

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