Github Issues allow highlighting text and code

[danirui]

Select Topic Area

Product Feedback

GitHub Feature Area

Markdown

Body

I think adding the ability and flexibility of highlighting plaintext and inside code-blocks would be very helpful for many people using Github Docs.

Currently, we have the rudimentary methods of <mark>plaintext</mark> which looks like plaintext (an extremely subdued yellow color), and

def function():
+ green code highlight
- red code highlight

which I learned from https://github.com/orgs/community/discussions/42489#discussion-4689594. Sadly this latter option is not available in conjunction with syntax highlighting.

The capability for Github Markdown to highlight text clearly exists; just a little more flexibility (some choice of color), and/or conjunction with syntax highlighting would be a major boost.

I put this in the Accessibility category because personally, I find that highlighting text judiciously improves my ability to skim, read, and understand it.
Research (Keyword Highlighting Improves Comprehension for People with Dyslexia --- Rello, Saggion, Baeza-Yates 2014) indicates that indeed highlighting improves readability and comprehensibility for people with dyslexia. See also Constrained Highlighting in a Document Reader can Improve Reading Comprehension --- Joshi, Vogel 2024, or this SkepticsSE post.

For these reasons, I think it is important that Github allow users the ability/flexibility to highlight some plaintext and code, preferably with some choice of (bright) colors.

[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]

Hello @danirui - thank you for providing this feedback! This is a really great feature request. We have filed this with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates. Thanks again!

[danirui]

Hi, sorry to bother, but have there been any updates? Thank you!

[cehfisher]

Hi @danirui — I can share that there’s quite a bit of internal work happening right now to improve the markdown experience. That said, I don’t yet know which features or updates will make the final cut or when they’ll be released. We’ll be sure to share updates as soon as we have them. Thank you for your continued patience!