🎩 What? Why?

This changes the <h2> element in the participatory space subtitles to a <p> element as discussed at:
#8893 (comment)

This makes it easier to control the heading orders below <h1> and also makes it possible to fix some inconsistencies currently with the heading ordering, e.g. that the debate titles are <h2> but proposal titles are <h3>.

The change is related to the rest of the accessibility fixes.

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 Fundamental problem in the design with H1-level headings #8893, Fix illogical heading order for a single proposal #8877, Fix the component index views heading order for the subtitle change #8902, Fix heading order in the process steps page #8906, Fix illogical heading order for a single proposal #8877

Testing

Take a look at the subtitle element with the inspector in different participatory spaces and see that it is now a <p>.

📋 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.

📷 Screenshots

The design is not affected by this change so the before and after looks the same: