question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Multiple h1s in Changelog - there should only be one

See original GitHub issue

The HTML output in the change logs produced by this tool include too many h1 elements. There should be one at the top for “Change Log”, and the individual releases should be h2’s so the content hierarchy makes sense and follows best practices for accessible headings.

Here’s what it outputs now:

# Change Log

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

<a name="3.0.0-alpha.2"></a>
# [3.0.0-alpha.2](https://github.com/dequelabs/axe-core/compare/v3.0.0-alpha.1...v3.0.0-alpha.2) (2017-09-01)

### Bug Fixes

Here’s what it should be:

# Change Log

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

<a name="3.0.0-alpha.2"></a>
## [3.0.0-alpha.2](https://github.com/dequelabs/axe-core/compare/v3.0.0-alpha.1...v3.0.0-alpha.2) (2017-09-01)

### Bug Fixes

I couldn’t figure out where those come from after a quick look through the source, perhaps it’s from one of the dependent modules? I’m happy to submit a PR if someone can point me in the right direction (including to another repo, if needed).

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:5
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
bcoecommented, May 5, 2019

This should now be fixed as of standard-version@6.x.x thanks for reporting the issue @marcysutton 👍

1reaction
aaronjameslangcommented, Jun 7, 2018

So we need to bump the version of conventional-changelog standard-version depends on. Should we update all the deps while we’re at it? Looks like it might require a major version bump, would there be resistance to this?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Multiple H1 Tags on Page is Perfectly Fine in SEO - Blog
The one question that has been bugging On-Page Optimization specialists is whether Multiple H1 tags on a page can cause a bad reputation...
Read more >
How to Use Multiple H1 Tags - Greenlane Search Marketing
An H1 should always be in the first section of the page's content (usually the logo or the level heading area). H1 tags...
Read more >
Multiple H1s not frowned upon after all, Google says
It has long been considered best practice to use only one top-level heading (H1) on a web page. However, during a recent episode...
Read more >
Multiple H1 Tags - Are They OK? - PageTraffic
Is It Bad To Have Multiple H1 Tags On A Page ... Google search listings may require a single H1 tag as the...
Read more >
Multiple H1 Tags on Page | SEO Forum - Moz
The biggest problem with multiple H1's is that using different keywords can confuse Google and Users about what a page is attempting to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found