Image alt text isn't included in pull request emails

[backwardok]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Pull Requests

Body

Issue

When an email goes out related to a pull request (PR), even if the images have alt text set, the email will include a link to the image with the label <filename> (view on web) and not include the image alt text. This is true for both images that are included as part of the PR description and images that are included in comments on PRs. This means that anyone who's using a screen reader would need to go to the PR in order to hear the alt text.

Example

I recently had a pull request where I included before and after screenshots in a table.

How it looks in the pull request on the web:

How it was coded in markdown:

| Before | After |
|--------|--------|
| <img width="511" height="183" alt="Fieldset highlighted from Chrome DevTools showing additional space below the last checkbox" src="https://github.com/user-attachments/assets/072fdf27-7d47-451a-9b9d-61e2360013a3" /> | <img width="504" height="175" alt="Same fieldset with the highlight of the fieldset tight to the end of the checkbox" src="https://github.com/user-attachments/assets/45dd7b08-a4cf-4a53-be52-a6e1119831e1" /> | 

How it looks in the email:

Possible solutions

When alt text is present, it's more accessible to include the alt text in the link text so it's clearer what the link goes to and also clarifies what the image is for anyone who can't see the image.

For example, the link text could be Image: <alt> (view on web). For my example, that would look something like Image: Fieldset highlighted from Chrome DevTools showing additional space below the last checkbox (view on web).

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