🎩 What? Why?

The comments section heading order is illogical.

Also, the comments main heading should be a <h3> in the Decidim default layout for it to be logical compared to most of the contexts where the comment section is displayed in the Decidim default layout.

Currently e.g. on this page:
https://meta.decidim.org/processes/RedesignDecidim/f/1662/posts/235

The current <h4> level indicates that the comments section is a subsection of the last text section titled "Methodology: Open design / participated design". The correct top-level context of the comments section should be the blog article's title which is <h2> and therefore <h3> makes more sense for the comments section.

Many screen reader users users glance the page quickly by going through its headings in which case this can be confusing.

WCAG 2.2 / 1.3.1 Info and Relationships (Level A)

https://www.w3.org/TR/WCAG22/#info-and-relationships
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html

📌 Related Issues

• Related to Fix illogical heading order for a single proposal #8877, Fundamental problem in the design with H1-level headings #8893

Testing

Give the linked blog page to a visually impaired user and ask them to read it.

📋 Checklist

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.