Inefficient UX of Markdown editor when there are multiple on a page (such as in a GitHub issue form)

[SaschaCowley]

Select Topic Area

Product Feedback

GitHub Feature Area

Issues

Body

Follow-up to https://github.com/orgs/community/discussions/61696

While we're very glad to see the accessibility improvements in GitHub Issue forms, I'd argue that the current user experience is, while technically accessible, not usable, when multiple markdown inputs are used in the one form. This is because each markdown editor occupies 4 tab stops:

1. View mode (switch between write and preview
2. Formatting toolbar
3. Composition area
4. Attachment picker

This makes navigating issue forms very tedious for keyboard users, including screen reader users, who typically navigate forms in focus/forms mode.

I propose modifying the markdown editor so that it occupies a single tab stop:

• The toolbar could be reached with a keyboard shortcut, such as Alt+F10.
• The view mode selector could get its own shortcut, or could be accessed from the toolbar.
• The file selection button would become part of the toolbar.
• A visual and screen-reader accessible indication of how to access the editor chrome would need to be added.

For an example of something like this, take a look at CKEditor

[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. ⭐