[wp-trac] [WordPress Trac] #17611: TwentyEleven Theme H1 Priority

WordPress Trac wp-trac at lists.automattic.com
Wed Jun 1 05:31:57 UTC 2011


#17611: TwentyEleven Theme H1 Priority
--------------------------+-----------------------
 Reporter:  emiluzelac    |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  3.2
Component:  Themes        |     Version:  3.2
 Severity:  normal        |  Resolution:
 Keywords:  close         |
--------------------------+-----------------------

Comment (by nacin):

 Money quote:

 > Sections may contain headings of any rank, but authors are strongly
 encouraged to either use only h1 elements, or to use elements of the
 appropriate rank for the section's nesting level.

 See: http://www.w3.org/TR/html5/sections.html#headings-and-sections

 So if we're nesting <sections>, then we *could* start at h2. The document
 goes on to suggest that with each nested <section>, increasing the heading
 # might result in the document being "more clearly expressed", but
 emphasizes according to the spec that "Both of the documents above are
 semantically identical and would produce the same outline in compliant
 user agents.".

 It finally states "This third example is also semantically identical, and
 might be easier to maintain (e.g. if sections are often moved around in
 editing)" and goes on to suggest straight h1's at the top of every section
 element.

 I support our current markup. But I'm inclined to go along with the third
 example, and thus any h1 inside a section becomes an h2. This is for
 purely practical and anti-pedantic reasons -- I'm not looking forward to
 the Trac tickets or support threads, and I agree that it will be more
 clear to someone deriving a theme from Twenty Eleven what's going on (who
 hasn't learned PHP and even HTML semantics from the default WordPress
 theme?). And who knows what'll happen when this post becomes flooded with
 proclaimed SEO experts.

 I'm just surprised there hasn't been a wp-hackers thread yet.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17611#comment:36>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list