#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 needs-testing | Focuses: accessibility
-------------------------------------+----------------------------
Comment (by davidakennedy):
Replying to [comment:4 rianrietveld]:
> Furthermore, and this may be a bridge to far to change for this theme:
There still is always a double H1. One for the site title, and one actual
H1 that represents the content.
>
> To my opinion, the best solution would be:
> Don't put headings on the site title and the site description.
> And put the (real) H1 directly above the content, in this theme:
> In <header> of <main>.
> If home is "Your latest posts", use the site title as H1 and hide it by
adding a screen-reader-text class, because in this case home is in fact an
archive without a visual title.
I wanted to reply to Rian and leave my thoughts. This also relates to
#30057.
Previously, the heading structure was very future-leaning, a fantastic
thing. I think the solution we have currently in the patch is an
improvement. It takes a bunch of `<h1>`s and a flat document structure and
creates a nice middle ground with less `<h1>`s and more structure, which
is also future leaning but mindful of current support in browsers and
assistive technology. I always favor better than before and released code
over aiming for perfection in unreleased patches.
About potentially moving to one `<h1>` per page: I think it's a good goal.
I also think that if we have two `<h1>`s, the site title and the main
content heading, it's not the end of the world. That's me though, someone
who tests for accessibility with assistive technology but doesn't use it
each and every day, all day.
There isn't any hard advice in the WCAG 2.0 guidelines about specifically
using one `<h1>` per page:
http://www.w3.org/TR/WCAG20-TECHS/H42.html
But the code examples provided only use one `<h1>`. :)
The W3C recently changed its advice on headings because of the outline
issue:
* http://lists.w3.org/Archives/Public/public-html/2014Jan/0004.html
* http://www.w3.org/html/wg/drafts/html/master/sections.html#outlines
All of the well-known accessibility consultant agencies use one `<h1>` per
page:
The Paciello Group: http://www.paciellogroup.com/blog/
WebAIM: http://webaim.org/blog/
Deque: http://www.deque.com/blog/
Nomensa : http://www.nomensa.com/insights
Simply Accessible uses two `<h1>`s on the index page, one for site title
and one for main content heading. The single view page has one `<h1>`:
http://simplyaccessible.com/
Knowing all this: What's the best decision for this default theme,
WordPress and the many sites and situations it will power?
Maybe a good middle ground is two `<h1>`s for the index/home page and one
everywhere else?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/30065#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform