Skip to content

Using single H1 tag per page #383

Closed
websanya opened this Issue Jan 14, 2014 · 6 comments

5 participants

@websanya

According to comments in this article http://webdesign.tutsplus.com/tutorials/htmlcss-tutorials/the-truth-about-multiple-h1-tags-in-the-html5-era/ one doesn't simply use multiple H1 tags on one page. Underscores uses H1 for all the stuff: articles, nave and sidebar widgets.

Maybe we should make it more seo-friendly, according to comments in the above article search engines doesn't use HTML5 Document Outline, neither screen readers do =(.

@yakirgot

Definitely. +1000000

article title in archive should be h2
widget title should be h3

@pierrepavlov

This has been discussed on multiple occasions, for example here: #232

@websanya

cool, but the commenters over here http://webdesign.tutsplus.com/tutorials/htmlcss-tutorials/the-truth-about-multiple-h1-tags-in-the-html5-era/ suggest the other way, this HTML5 semantic stuff isn't supported in any User Agent or Search Engine or Screenreader.

Over here: http://blog.paciellogroup.com/2013/10/html5-document-outline/

@kovshenin

This is the 16th "h1 issue" on _s. Closing as wontfix. Feel free to change h1 to another tag after generating a theme with _s, if you think that will help.

@kovshenin kovshenin closed this Jan 14, 2014
@mrwweb
mrwweb commented Jan 24, 2014

@kovshenin has the accessibility side of this debate ever actually been discussed on the h1 issue? I'm not finding much in the issues on Github, but the more I read the more I think some changes (probably not all) may be in order. If I open a new, carefully researched ticket, will it get heard out?

@kovshenin

@mrwweb I don't think the accessibility side of this issue has been discussed before, so sure :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.