Accessibility improvements for files changed view

[ReginaReusser]

Select Topic Area

General

GitHub Feature Area

Pull Requests

Body

Hello
In the “Files changed” view, additions and deletions are currently only visually marked by color (green/red) and a plus/minus sign.
For screen reader and Braille display users, it would be much more accessible if these changes were also semantically marked up, for example using the "ins"-element for insertions and the "del" element for deleted text.

I have tested and locally and confirmed that sccreen readers announce “inserted” or “deleted” text, giving clear, non-visual context.
Visually, browsers display inserted text underlined and deleted text with a strikethrough, so sighted users benefit as well without relying solely on color.

This semantic markup would improve accessibility for users who cannot perceive colors and would support compliance with WCAG 1.4.1 (Use of Color).

Thank you for considering this improvement.

[48vineet]

Using semantic HTML elements like:

for inserted text

for deleted text

would allow:

Screen readers to announce changes as “inserted” or “deleted”

Sighted users to benefit from underlines and strikethroughs, improving clarity

Better compliance with WCAG 1.4.1 – Use of Color, which requires that color not be the only means of conveying information

Practical Impact
You've already tested this locally and confirmed that screen readers respond correctly—this is a strong case for GitHub to consider implementing it. It would make code reviews more inclusive and accessible for developers with visual impairments.

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

[jmuheim]

I highly second this improvement. I think that GitHub does a pretty good job already regarding accessibility, but using simple semantic HTML elements is the lowest hanging fruit imaginable.

Honestly, I'm a bit shocked that <ins> and <del> isn't used by GitHub yet - as diff-views are THE use case (and probably the ONE AND ONLY use case) for these two little HTML tags. And while other inline tags like <em> or <strong> don't have a clear meaning, <ins> and <del> definitely do.

[cehfisher]

Hi @ReginaReusser - thanks so much for sharing your product feedback! To help us figure out which version of the PR view you’re using, could you share a few screenshots of the issue? We’re trying to confirm whether you’re using the old or new PR experience. Do you see a “Try the new experience” option on your page? Thanks!