The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: benazeer-ben <benazeer@git.wordpress.org>
Co-authored-by: carolinan <poena@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: Marc-pi <mdxfr@git.wordpress.org>
Co-authored-by: afercia <afercia@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: alexstine <alexstine@git.wordpress.org>
Co-authored-by: 00travelgirl00 <travel_girl@git.wordpress.org>
Co-authored-by: huubl <huubl@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Could someone review this PR when available? @Mamaduka @ajitbohra @fabiankaegy

Let me know if you'd like any further refinements!

Thanks in advance!

Hi Team,

Whenever you have some time, could you please review this PR? I’d really appreciate your feedback.

Thanks in advance!

cc: @t-hamano @carolinan

Hi, the table of content block is still experimental, personally I am not able to prioritise it.

Thanks for the PR!

From reading the issue, it seems like the current TOC block needs some improvement from an accessibility perspective, so simply adding an h2 heading option might not be the best solution.

Before proceeding with implementation, it is a good idea to consider what specification would be the ideal approach.

well, that's a strong need, instead of having to encapsulate it into a group block just to add a free paragraph in it on top of ToC.

• this text should not have by default any heading level
• personally i never add such a Hn on top ToC list, only a simple paragraph (ex: "Summary")

Let's close this PR and consider a more ideal approach. Looking at #52378, I think we need to discuss the more fundamental issues below first:

• The block outputs a nav element, but there is no way to label it.
• On the other hand, tables of contents with navigation landmark can sometimes be noisy.

@benazeer-ben Thank you for your efforts!