[wp-trac] [WordPress Trac] #30065: Twenty Fifteen: Heading Structure

WordPress Trac noreply at wordpress.org
Tue Oct 28 05:16:31 UTC 2014


#30065: Twenty Fifteen: Heading Structure
---------------------------+----------------------------
 Reporter:  bramd          |       Owner:
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  4.1
Component:  Bundled Theme  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  accessibility
---------------------------+----------------------------

Comment (by davidakennedy):

 Replying to [comment:13 joedolson]:
 > It's my opinion that the site title should never be a heading -- it
 doesn't serve structurally as a heading within the page; and any 'heading'
 characteristics it should have semantically are easily fulfilled by using
 the <header> structural container.
 >
 > If you consider the value of headings from a structural and navigational
 perspective, having a top-level heading for the site title is almost never
 valuable -- all it does is affirm that yes, you're still on this site.
 This is information that you've already received from the <title> element,
 so it's hardly new information.
 >

 Thanks for weighing in Joe. That's a good point about the `<title>`
 element. I think it makes sense to move to one `<h1>` per page here. It
 would give us an even cleaner outline and structure, good for semantics,
 assistive technology and search engines.

 If

 * home page is blog index and front page: site title is `<h1>`
 * home page is page and blog index is page: site tile is  `<p>` on home
 page and hidden  `<h1>` in  `<header>`  above post listing on blo index
 page is the title for the blog index page: `get_the_title( get_option(
 'page_for_posts' ) );`. Similar to `.page-title` markup.

 This should give us a unique `<h1>` on every page.

 Am I missing any use cases with the combination of `is_home()` and
 `is_front_page()`?

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


More information about the wp-trac mailing list