[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
-------------------------------------+-------------------------------------
Changes (by GaryJ):

 * focuses:  template => accessibility, template


Comment:

 Replying to [comment:28 obenland]:
 > Discussed this with arush, GrahamArmfield, joedolson, and
 acessibilityjoe during the contributor team meetup.
 >
 > [https://wordpress.slack.com/archives/accessibility/p1414610844000262 We
 agreed] to remove the arrows and meta-nav items from all three functions

 Excellent, thank you.

 > but leave the `h1` tag.

 I find it hard to believe that all of those involved would have readily
 agreed to keeping the `h1`, but as no discussion was documented, I can't
 follow-up on the reasonings.

 > While there is currently spotty support for HTML5 sectioning elements in
 screen readers

 The sectioning elements aren't the problem per se. The support of the
 outline algorithm is what's missing in all screen readers and graphical
 UAs. The HTML5 spec clearly
 [http://www.w3.org/TR/html5/sections.html#outlines recommends the use of
 heading hierarchy to convey document structure].

 The fact you've highlighted the area is spotty, is surely sign that it's
 not ready for prime time Core usage?

 > keeping it would foster the adoption of modern web standards.

 This is not the place to fight that battle. Not when the spec itself
 recognises that not a single implementation of this part of the spec
 currently exists and recommends not to follow it.

 > The most important part is that there is a screen reader text in the
 first place.

 Agreed, but not if it's marked up in a way that is detrimental to screen
 reader users from understanding the document structure. This issue is now
 absolutely no different than r30072 / #30065, and to allow the `h1` to
 stay would permit inconsistencies in the document structure.

 Please, remove it, or at least filter it, so that if Twenty Fifteen and a
 different theme want to follow the completely-unsupported document outline
 for headings, they can do so when they want, without having to avoid using
 the functions as they stand.

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