Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using single H1 tag per page #383

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

Using single H1 tag per page #383

websanya opened this issue Jan 14, 2014 · 6 comments

Comments

@websanya
Copy link

@websanya websanya commented Jan 14, 2014

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
Copy link

@yakirgot yakirgot commented Jan 14, 2014

Definitely. +1000000

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

@pierrepavlov
Copy link

@pierrepavlov pierrepavlov commented Jan 14, 2014

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

@websanya
Copy link
Author

@websanya websanya commented Jan 14, 2014

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
Copy link
Contributor

@kovshenin kovshenin commented Jan 14, 2014

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
Copy link
Contributor

@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
Copy link
Contributor

@kovshenin kovshenin commented Jan 27, 2014

@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
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants