Jan 17 2019 09:03 AM
Noticed that when using the modern text web part, if you select text and format it as an H1 heading, it actually creates an H2 heading.
Oct 11 2019 07:49 AM
@Jaymz Yates, have you received any feedback, answers, or clarifications?
I'm getting the same result - even using the Markdown webpart, my H1 tags are rendered as H2. I'm trying to get the auto-anchors to work, but since nothing is rendered as H1, I suppose that is why the auto-anchors aren't working either.
I've also tried deploying pages using the PnP PowerShell (Apply-PnPProvisioningTemplate) and forcing H1 tags onto the page, but so far no luck.
Jul 28 2021 01:59 AM
Nov 01 2022 10:02 AM
Nov 02 2022 02:23 AM
@Jaymz Yates @smblair72 @Darren70s @Daniel TSHIN
This is known behavior in SharePoint online. As per Microsoft:
Many Web Parts introduce a level 2 heading to pages without providing a means for users to change that heading level.
For headings added to pages using the Text Web Part, the heading level the page author specifies is downgraded by one when presented to the end user (e.g., a heading a page author sets to level 1 will be presented as a heading level 2 in the final HTML). The purpose of this is to ensure that the page title is always the only heading level 1 on the page and to avoid conflicts with heading levels when users copy and paste from other sources.
Tables added with the Text Web Part do not have column or row headers defined.
Find more details at: Accessibility Question about Heading Levels and Heading Styles
I will suggest you to:
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
Nov 02 2022 07:31 AM
Nov 03 2022 01:46 AM
@smblair72 Voted on the feedback/idea.
Please consider giving a Like if my post helped you in any way.