I don't quite see how you come to your conclusions. Disclaimer: I am hardly an expert on this stuff.
At any rate, if your html is pasted into the w3c markup validation service the following warning is returned:
Warning: Consider using the h1 element as a top-level heading only (all h1 elements
are treated as top-level headings by many screen readers and other tools).
Following that link gives:
Usage notes
- Heading information can be used by user agents to construct a table of contents for a document automatically.
- Avoid using heading elements to resize text. Instead, use the CSS font-size property.
- Avoid skipping heading levels: always start from <h1>, followed by <h2> and so on.
- Use only one <h1> per page or view. It should concisely describe the overall purpose of the content.
- Using more than one <h1> will not result in an error, but is not considered a best practice. It is beneficial for screenreader users, and SEO.
- While HTML5 allows a <h1> per sectioning element, it is not considered best practice, and may subvert the expectations of how screen reader users navigate.
As a further note, html makes a distinction between structural markup and presentational markup. h1 tags are an example of structural markup. As is noted in
HTML - Wikipedia
There are several types of markup elements used in HTML:
Structural markup indicates the purpose of text. For example, <h2>Golf</h2> establishes "Golf" as a second-level
heading. Structural markup does not denote any specific rendering, but most web browsers have default styles for element formatting. Content may be further styled using
Cascading Style Sheets (CSS).
[72]
Presentational markup indicates the appearance of the text, regardless of its purposeFor example, <b>bold text</b> indicates that visual output devices should render "boldface" in bold text, but gives little indication what devices that are unable to do this (such as aural devices that read the text aloud) should do. In the case of both <b>bold text</b> and <i>italic text</i>, there are other elements that may have equivalent visual renderings but that are more semantic in nature, such as <strong>strong text</strong> and <em>emphasized text</em> respectively. It is easier to see how an aural user agent should interpret the latter two elements. However, they are not equivalent to their presentational counterparts: it would be undesirable for a screen-reader to emphasize the name of a book, for instance, but on a screen such a name would be italicized. Most presentational markup elements have become
deprecated under the HTML 4.0 specification in favor of using
CSS for styling.