Issue Forms: Ability to change heading levels

[LekoArts]

Hi!

When using the different form schemas like textarea or checkboxes the main information is inside the label and this will also be output in the resulting markdown.

Currently all labels will be a <h3> while we personally would like them to be a <h2>. Generally speaking the heading levels could become an accessibility concern as people might use h1, h2, etc. in their freeform textarea field, e.g. like here: https://github.com/LekoArts/stale-bot-test/issues/27

There could be wrong heading orders or even multiple h1 on a page then. Maybe the heading levels inside any textarea should be modified/adapated in order to fit into the whole page flow.

[elsiehupp]

I personally go back and edit my Issues to use <h2/> (i.e. ##) instead of <h3/> (i.e. ###). I mean, it just looks better and increases legibility, in addition to the hierarchy issues you mention that could break accessibility.

I found my way here because, as you say, there doesn't seem to be a way to change the default heading level for label headers, and IMHO they should default to or just in general be <h2/> (i.e. ##) instead of <h3/> (i.e. ###), <h1/> (i.e. #) being already in use for the Issue title.

Weird that this forum for Issue Forms is a "Discussions" rather than an "Issues"? idk.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐