enabling spell checking for editing a md file

[bvarwig]

Select Topic Area

Product Feedback

GitHub Feature Area

UI/UX

Body

I would like to use the spell checking capability's of my Browser when editing an markdown file. Many other input fields support the spell checking.

here a screenshot where i would like to have the spell checking:

My browser has spell checking enabled as you can see in the screenshot below, which is showing the edit mode of this discussion body:

I have checked this with:

• Chrome: Version 129.0.6668.101 (Official Build) (64-bit)
• Microsoft Edge for Business Version 132.0.2957.115 (Official build) (64-bit)

It would be nice if spell checking for all md like the README.md and others could be enabled.
Of cause for Source code it might not be the best to have spell checking enabled.
For those who like Grammarly, Grammarly should work when spell checking is enabled.

Having this feature would help all Dyslexic People and others as well.

Regards Britta

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

[cehfisher]

Thank you @bvarwig for taking the time to submit your feedback! We have filed an internal issue with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates. Thanks again!

[Myndex]

More than just accessibility: This applies to all, and I've also brought these issues up. The editor in repos for editing files, is as I understand it Ruby based, with the editor used for message posts in issues or discussions JS based. The JS based editors do not block browser features like spell check, but the Ruby based editors do, and also, the Ruby based editors can crash causing loss of work.